simonsobs / simonsobs/SOOPERCOOL
Find and implement elegant naming convention to not have long filenames
Open
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 6
- Forks
- 5
- Avg merge
- 5d 22h
- Merged PRs (30d)
- 2
Description
Regarding all comments related to the naming convention length.
- A quick grep looking for occurrences of
ftaggives a lot of results: it feel unsafe to propagate all changes there. - This naming convention length issue will also occur for spectra (if map_sets are quite long and descriptive), covariances (pairs of
map_setpairs) and other products such as coupling matrices. - I'd rather open an issue on this, to see if we find any elegant way of compressing these labels to make pipeline output more human-readable and apply it to all outputs all at once.
Originally posted by @adrien-laposta in https://github.com/simonsobs/SOOPERCOOL/issues/70#issuecomment-4449413374
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 or tests are named. Start by tracing the ftag occurrences and inspecting how spectra, covariances, coupling matrices, and other pipeline products build output labels. Done means one agreed naming convention compresses long labels, remains human-readable, and can be applied consistently across all outputs.
Written by the indexing model from the issue text.
Assessment
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100