Please check if your PR fulfills the following requirements:
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been reviewed and added / updated if needed (for bug fixes / features)
Some docs updates need to be made in the COAsT-site repo, in a separate PR. See contributing to documentation for details.
[x] Build (./build.sh) was run locally and no errors reported. NB not sure about this requirement: GitActions test this
[x] Lint (pylint .) has passed locally and any fixes were made for failures. NB not sure about this requirement: GitActions test this with black
Pull request type
Please check the type of change your PR introduces:
- [ ] Bugfix
- [x] Feature
- [x] Code style update (formatting, renaming)
- [ ] Refactoring (no functional changes, no api changes)
- [ ] Build related changes
- [ ] Documentation content changes
- [ ] Other (please describe):
## What is the new behavior?
- Incorporate the ability to open zarr files.
- Include a sample notebook for reference.
- Address and rectify any lint issues.
### Checklist
- [x] Code compiles correctly
- [ ] Created tests which fail without the change (if possible)
- [x] All tests passing (`pip install . && pytest unit_testing/unit_test.py -s`)
- [x] Extended the README / documentation, if necessary
- [x] Added myself / the copyright holder to the AUTHORS file
## Does this introduce a breaking change?
- [ ] Yes
- [x] No
Pull request checklist
Please check if your PR fulfills the following requirements:
COAsT-siterepo, in a separate PR. See contributing to documentation for details../build.sh) was run locally and no errors reported. NB not sure about this requirement: GitActions test thispylint .) has passed locally and any fixes were made for failures. NB not sure about this requirement: GitActions test this withblackPull request type
Please check the type of change your PR introduces: - [ ] Bugfix - [x] Feature - [x] Code style update (formatting, renaming) - [ ] Refactoring (no functional changes, no api changes) - [ ] Build related changes - [ ] Documentation content changes - [ ] Other (please describe): ## What is the new behavior? - Incorporate the ability to open zarr files. - Include a sample notebook for reference. - Address and rectify any lint issues. ### Checklist - [x] Code compiles correctly - [ ] Created tests which fail without the change (if possible) - [x] All tests passing (`pip install . && pytest unit_testing/unit_test.py -s`) - [x] Extended the README / documentation, if necessary - [x] Added myself / the copyright holder to the AUTHORS file ## Does this introduce a breaking change? - [ ] Yes - [x] No