We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
I believe the syntax is wrong in the examples here:
https://satpy.readthedocs.io/en/latest/overview.html#data-chunks
To Reproduce
# Your code here
Expected behavior A clear and concise description of what you expected to happen.
Think it should be dask.config.set({"array.chunk-size": "32MiB"}) for example.
dask.config.set({"array.chunk-size": "32MiB"})
(Curly braces are missing)
Actual results Text output of actual results or error messages including full tracebacks if applicable.
Screenshots If applicable, add screenshots to help explain your problem.
Environment Info:
from satpy.utils import check_satpy; check_satpy()
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
I thought I had already fixed this issue, but seemingly not! Anyway, I agree that the curly braces should be there.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Describe the bug
I believe the syntax is wrong in the examples here:
https://satpy.readthedocs.io/en/latest/overview.html#data-chunks
To Reproduce
# Your code here
Expected behavior
A clear and concise description of what you expected to happen.
Think it should be
dask.config.set({"array.chunk-size": "32MiB"})
for example.(Curly braces are missing)
Actual results
Text output of actual results or error messages including full tracebacks if applicable.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment Info:
from satpy.utils import check_satpy; check_satpy()
]Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: