Ability to read ASTE grids
Ability to read seaice and thsice native output
Reading of optional grid files
Moved test data to figshare
Writing of binary files
Xarray 0.12 compatibility
Ability to read 2D slice diagnostics of 3D fields
Extend capabilities of read_raw_data (GH84)
Fix the problem with testing type of prefix (GH83)
Cast prefix to list if it isn’t already one (GH79)
Generalizes _get_all_iternums in order to handle compressed data (GH77)
Extract version number from git tag (GH72)
Adding .stickler.yml (GH70)
Added functionality to read PTRtave files (GH63)
Update examples.rst (GH65)
fix time encoding (GH61)
Fix llc chunking (GH60)
Test refactor (GH54)
Kpp added properly (GH55)
Tests for ref_date issue (GH53)
Add python 3.6 testing (GH52)
Added layers axis attribute (GH47)
Fix to ensure that grid indices are always interger dtype.
Fix to keep proper Comodo metadata when swapping dimensions.
- This release contains the following feature enhancements:
Files are not read until the data are accessed. This helps overcome a common “too many open files issue” (GH11).
A workaround for missing
Option for a separate
grid_dirin case it is different from
Refactor of the way LLC data is read which allows for more efficient chunking and lower memory usage (GH20)
Support for cartesian curvilinear grids. By Andrea Cimatoribus.
Expanded and improved documentation.
Unless otherwise noted, all updates are by Ryan Abernathey.
Anyone interested in helping to develop xmitgcm needs to create their own fork of our git repository. (Follow the github forking instructions. You will need a github account.)
Clone your fork on your local machine.
$ git clone email@example.com:USERNAME/xmitgcm
(In the above, replace USERNAME with your github user name.)
Then set your fork to track the upstream xmitgcm repo.
$ cd xmitgcm $ git remote add upstream git://github.com/MITgcm/xmitgcm.git
You will want to periodically sync your master branch with the upstream master.
$ git fetch upstream $ git rebase upstream/master
Never make any commits on your local master branch. Instead open a feature branch for every new development task.
$ git checkout -b cool_new_feature
(Replace cool_new_feature with an appropriate description of your feature.) At this point you work on your new feature, using git add to add your changes. When your feature is complete and well tested, commit your changes
$ git commit -m 'did a bunch of great work'
and push your branch to github.
$ git push origin cool_new_feature
At this point, you go find your fork on github.com and create a pull request. Clearly describe what you have done in the comments. If your pull request fixes an issue or adds a useful new feature, the team will gladly merge it.
After your pull request is merged, you can switch back to the master branch, rebase, and delete your feature branch. You will find your new feature incorporated into xmitgcm.
$ git checkout master $ git fetch upstream $ git rebase upstream/master $ git branch -d cool_new_feature
This is how to create a virtual environment into which to test-install xmitgcm, install it, check the version, and tear down the virtual environment.
$ conda create --yes -n test_env python=3.5 xarray dask numpy pytest future $ source activate test_env $ pip install xmitgcm $ python -c 'import xmitgcm; print(xmitgcm.__version__);' $ source deactivate $ conda env remove --yes -n test_env