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

FIX: Fix for new xarray check for dtype. #804

Merged
merged 1 commit into from
Feb 26, 2024

Conversation

zssherman
Copy link
Collaborator

Trying to understand the encoding was a learning experience to say the least. The input encoding is 'float64' so I set it to that. 'datetime64[ns]' does not work.

@AdamTheisen
Copy link
Collaborator

@kenkehoe can we always assume that time bounds are always going to be floats?

@zssherman
Copy link
Collaborator Author

Yeah if it does change, I can try to find a way to automate it.

@kenkehoe
Copy link
Contributor

I believe time_bouds by ARM standards will always be a float (type float or double). It should be the number of seconds to add and subtract to define the bound. It should match the same type as the written time coordinate variable. Since Xarray converts time upon reading to datetime64 but not time_bounds it should stay a float.

@zssherman
Copy link
Collaborator Author

@AdamTheisen Good to merge?

@AdamTheisen AdamTheisen merged commit 90fc449 into ARM-DOE:main Feb 26, 2024
19 checks passed
@zssherman zssherman deleted the xarray_time branch May 2, 2024 14:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants