You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is probably because the job building the documentation simply takes too long and/or runs out of memory. My proposal is to add the same USE_FULL_DETECTOR hack to .readthedocs.yaml as is used for the github test runner for now (however, I don't know how to do that):
sed -i "s/USE_FULL_DETECTOR = True/USE_FULL_DETECTOR = False/g" MICADO/docs/example_notebooks/*.ipynb
Then later we can remove that hack once we made ScopeSim fast again.
Difficulty is that we don't have access to our readthedocs account. A workaround is to manually import the IRDB as a personal project on rtd. In that project it will be possible to see what the problem is, and if those are fixed, then the official documentation is also fixed.
The text was updated successfully, but these errors were encountered:
The read the docs documentations for the IRDB currently fails to build.
This is probably because the job building the documentation simply takes too long and/or runs out of memory. My proposal is to add the same
USE_FULL_DETECTOR
hack to.readthedocs.yaml
as is used for the github test runner for now (however, I don't know how to do that):irdb/.github/workflows/tests.yml
Line 100 in 27ec035
Then later we can remove that hack once we made ScopeSim fast again.
Difficulty is that we don't have access to our readthedocs account. A workaround is to manually import the IRDB as a personal project on rtd. In that project it will be possible to see what the problem is, and if those are fixed, then the official documentation is also fixed.
The text was updated successfully, but these errors were encountered: