Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Storing history of xarray operations
See original GitHub issueIt may be useful to keep track of operations applied to DataArrays and Datasets in order to enhance provenance of output netcdf datasets, particularly for scientific applications to enhance reproducibility. However, this essentially would require keeping track of all the operations that were used to produce a given DataArray or Dataset.
Ideally, we would want this to eventually result in appending data to the ‘history’ attribute for calls to *.to_netcdf(...). This would keep track of data manipulation similar to nco/ncks/etc operations.
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This package addresses this issue: https://github.com/recipy/recipy
They are working on xarray support: https://github.com/recipy/recipy/issues/176
Thanks @shoyer! I think after this discussion that this is something we should handle within our own wrapper. There does not seem to be a clean one size fits all solution warranting inclusion in xarray, unless I’m mistaken. If so, I hope someone chimes in to correct me.