-
Notifications
You must be signed in to change notification settings - Fork 39
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
Update mov run #994
Update mov run #994
Conversation
@acordonez would you be able to help verifying this PR won't break the MoV demo? |
@lee1043 I'm getting a segmentation fault when I run the first example. This looks like the issue I saw with my changes in the variability_across_timescales driver, where importing shapely after importing cdat libraries causes a segmentation fault. I can get the driver to run normally if I put an "import shapely" statement at the top of variability_modes_driver.py, but the pre-commit hooks don't like that. If you have a better fix I can also use that in variability_across_timescales. Here's the full text:
|
@acordonez it is interesting to know this would prevent the error. What about if "import shapely" is added at the top of lib/plot_map.py? Could you please check if this would work? I am studying pre-commit settings to see if there is any way to make it an exception. |
@acordonez I guess this might be related to the version of shapely, which we couldn't update to the latest because of the limit in the Python version that is tied with the CDAT... |
@lee1043 When I saw this problem before, shapely has to be called before any cdat packages in the entire run. So if the driver script imports cdat before shapely, even if shapely is called in another script, it causes the segmentation fault. |
@lee1043 I tried a few different versions of shapely, even old ones, with variability_across_timescales and couldn't find one that would work. It might be something to do with underlying C packages that get called by both shapely and cdat, but I didn't investigate the underlying cause that deeply. |
…t can consider it as an exception
@acordonez thank you for the comments, very helpful! I revised the driver script to import shapely at the top and added |
@lee1043 The segmentation fault is gone! I'm getting another error in section 3.2.1 (and seeing a similar error in 3.3.1):
|
@acordonez thank you for checking this. I think the error was caused by combinations of multiple factors -- cdms variable with cartopy, 1e20 being used for fill value that was not appreciated by xarray. I add workarounds and confirmed that demo notebook is working without any issue. Could you please double check if this is true on your end as well? |
@lee1043 The notebook ran perfectly this time |
@lee1043 Should I merge this? |
@acordonez Excellent, thank you for double checking! |
@acordonez let me clean up a few more things and will merge it. |
No description provided.