Blog post #142
Blog post #142
Conversation
TomNicholas
commented
Oct 20, 2021
TomNicholas
commented
- Closes Blog post to show off pint-xarray integration? #114
Co-authored-by: keewis <[email protected]>
Co-authored-by: keewis <[email protected]>
Co-authored-by: keewis <[email protected]>
Co-authored-by: keewis <[email protected]>
Co-authored-by: keewis <[email protected]>
|
I think the doctest failure is a upstream issue: it may have been introduced when I changed the formatting code of |
that's wrong, it is the same issue as above: assigning to the application registry modifies the wrapper and not the unit registry. In this case, instead of |
|
as decided in the meeting this evening, we'll skip the We still need to wait on the |
blogpost.md
Outdated
| @expects("newton * seconds") | ||
| def jpl_trajectory_code(impulse): | ||
| print(f"Received impulse in units of [{impulse.pint.units}]") |
There was a problem hiding this comment.
Change this to a simple if raise statement for now, and add a note that we will improve this API in future
There was a problem hiding this comment.
Done now, though I should probably print the actual error message that would be raised
| ## Dequantifying | ||
|
|
||
| To convert our pint arrays back into numpy arrays, we can use `.dequantify`. | ||
| This will strip the units from the arrays and replace them into the `.attrs['units']` of each variable. | ||
| This is useful when we want to save our data back to a file, as it means that the current units will be preserved in the attributes of a netcdf file (or zarr store etc.), as long as we just do `ds.pint.dequantify().to_netcdf()`. |
There was a problem hiding this comment.
Put a note in about option of dequantifying to different formats
There was a problem hiding this comment.
@keewis should we bother with this?
for more information, see https://pre-commit.ci
|
@keewis we should ideally add this content as a new page of examples in the docs |
