Error cannot convert float nan to int

[davide-f]

Error cannot convert float nan to int

[euronion]

Can't reproduce, sorry. Closing for now. If you encounter it again feel free to re-open the issue.

[davide-f]

Hello!
Actually it appeared again using pypsa-meets-earth/pypsa-earth#701 on NZ...
I may have to create again the cutout

[euronion]

Is it the same cutout with which you encounter the problem in the first place? Or already a new one?

[davide-f]

Again many thanks for the quick reply! :)

Indeed it is the same cutout. I would do other checks and let you know.
In particular, the tests may be:

1. Recreate the cutout for the whole earth again
2. Create a NZ-specific cutout
   All of them using the latest version of the repository.

@euronion could you confirm that some compression is already included in the new version?

Ah, as a little comment: in conda/pip the version .11 is available bit no .11 tag is available in github

[euronion]

Compression is included in the 0.2.11 version, yes. But don't expect significant gains unless you stitched together the world cutout by hand before. ERA5 data is already nicely compressed.

@FabianHofmann did the last release; I can see a tag, but no GitHub release. @FabianHofmann could you check?

[FabianHofmann]

@euronion @davide-f I made a new GH release for 2.1. Most likely not related but note @davide-f that #242 (fixing nan's in hydro calculation) did not make into this release. On the other hand, #289 should fix this mentioned issue. Did you make sure version 0.2.11 is installed?

[davide-f]

@FabianHofmann yeah, I confirm that 0.2.11 is installed.
I also recently re-created the whole cutout with the new version and the error persists unfortunately

[euronion]

Can you reproduce the issue with an MWE? Or only inside the workflow?

[davide-f]

This problem with a custom environment is not appearing.
It may be related to xarray: with the v2023 some errors in the workflow have disappeared, not sure why. Now NZ is working.
This problems may be related for some reason with xarray or another package

[euronion]

Alright, let's keep an eye out for it. If we can track it down again it would be nice to have an test in the CI.