NASA-AMMOS / NASA-AMMOS/AIT-Core
Simplify seq encode / decode utilities
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 56
- Forks
- 35
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 3
Description
There's not really a great reason for our encode / decode utilities to require specific input file naming conventions. Our example implementations should error on the side of simple and useful for the majority of users. Seems like these are failing there.
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
Locate the seq encode/decode utilities and their example implementations, then inspect where they enforce input file naming conventions. Done means the examples work with ordinary filenames rather than requiring a specific naming pattern; no test file or entry point is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100