Skip to content
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

upgrade cartopy 0.20 -> 0.21 #693

Closed
emanuel-schmid opened this issue Apr 13, 2023 · 4 comments
Closed

upgrade cartopy 0.20 -> 0.21 #693

emanuel-schmid opened this issue Apr 13, 2023 · 4 comments
Assignees

Comments

@emanuel-schmid
Copy link
Collaborator

emanuel-schmid commented Apr 13, 2023

Since the update to cartopy 0.21, the unit test climada.test.test_plot.TestPlotter.test_exposures_value_pass fails gracelessly on Jenkins because it runs out of memory:

======================================================================
ERROR [31.423s]: test_exposures_value_pass (climada.test.test_plot.TestPlotter)
Plot exposures values.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/var/lib/jenkins/jobs/climada_branches/branches/develop/workspace/climada/test/test_plot.py", line 123, in test_exposures_value_pass

  ...

  File "/home/IEDAdmin/miniconda3/envs/climada_env/lib/python3.9/site-packages/pyproj/utils.py", line 129, in _copytobuffer
    return xxx.astype("d", order="C", copy=not inplace), DataType.ARRAY
numpy.core._exceptions._ArrayMemoryError: Unable to allocate 981. MiB for an array with shape (128544732,) and data type float64

(On Windows, the test consumes, unrestricted, about 10G.)

@emanuel-schmid
Copy link
Collaborator Author

we need a more considerate test - or a smarter plot. 🤷

@emanuel-schmid
Copy link
Collaborator Author

first encountered after dependency upgrade (#682)

@NicolasColombi
Copy link
Collaborator

NicolasColombi commented Apr 18, 2023

Hi @emanuel-schmid, the problem should be fixed, the issue was with plot.raster() I simply applied a coarser resolution and now it takes around 400Mb of RAM to execute the test. See PR #697

@peanutfun
Copy link
Member

Upgraded with #682

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants