-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Examples in documentation not run #431
Comments
This is not a bug, but they were never actually run. Not sure if this is intentional, as some atlite examples just take too long? @euronion? |
I believe we set it up like this because running them would take a long time / consume too many resources. However the outputs have in the past been included in the examples and upload. |
Makes sense. Thank you! |
Ah, great. So just a different setup than in PyPSA (where .ipynb are run in the build stage of the docs). |
Could be a low prio improvement to have the examples run during the build stage of the docs? |
Yeah, as done in PyPSA/PyPSA for example. But I barley looked at it and I think with resources needed right now this is a very low prio improvement. The bigger cutouts would need to be cached |
Version Checks (indicate both or one)
I have confirmed this bug exists on the lastest release of atlite.
I have confirmed this bug exists on the current
master
branch of atlite.Issue Description
See https://atlite.readthedocs.io/en/latest/examples/landuse-availability.html
Reproducible Example
Expected Behavior
The outputs of the code cells should be shown. They should be run on Readthedocs when building the documentation.
Installed Versions
N/A
The text was updated successfully, but these errors were encountered: