simonsobs / simonsobs/SOOPERCOOL
Change file format of release-relevant products
Open
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 6
- Forks
- 5
- Avg merge
- 5d 22h
- Merged PRs (30d)
- 2
Description
For data releases, we aim to avoid npz format as it is an usafe format, and replace it by e.g. fits or HDF5. We should identify those products (e.g. TF, beams, etc.) and refactor the code accordingly.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating where data-release products such as TF and beams are written in npz format, then document which products require a replacement and compare the proposed fits or HDF5 options. Done means all identified release-relevant products use the selected safe format and their release paths remain usable.
Written by the indexing model from the issue text.
Assessment
- Domain
- data, release
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100