-
Notifications
You must be signed in to change notification settings - Fork 52
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
Switch simulationStartTime to xarray #705
Conversation
15ad1ac
to
ae83d4d
Compare
@darincomeau, I haven't had a chance to fully test this but I think it will fix #704 |
This should hopefully improve problems with string decoding Remove terminating null characters from date strings
ae83d4d
to
1dbc0cf
Compare
@darincomeau, could you re-test with this branch? I think it's finally fixed. I'm running the analysis you pointed me to last week right now but it's at least getting through the initialization phase where it was going wrong before. |
@xylar I'm now getting errors in all of the SOSE/WOCE transect tasks, e.g.:
|
@darincomeau, I didn't have any trouble with those. I'm running with a pretty new
|
@darincomeau, I'm seeing a similar error when I run code that used to work fine (ISMIP6 stuff) in an environment that used to work fine on files that have nothing to do with PIO2 and aren't new. I'm not sure if this could be something specific to Cori, maybe a recent update or something? I'm kind of baffled at the moment. |
I see, in my case, it's just a very confusing "file not found" error. Maybe the same for you and it will work if you purge and re-run? |
Thanks @xylar - I had created a new environment last week before submitting this issue. I also tried clearing out the |
@darincomeau, short of that, you are going to have to debug which file is missing and why. The error message you posted doesn't give the offending file name so I would need that info to help you debug. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should hopefully improve problems with string decoding
closes #704