Running gfzrnx should not modify the input file
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 23
- Forks
- 9
- Avg merge
- 5d 12h
- Merged PRs (30d)
- 4
Description
What if we copy the observation file in a new folder and add everything associated to the processing job: nav files, intermediate files, generated prx file, log files. For the folder name (job id) hash the file provided by the user.
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
Start by tracing how gfzrnx is invoked and how the observation file, navigation files, intermediate files, generated prx files, and logs are currently handled. Done means processing leaves the user-provided observation file unchanged and places the copied input and associated job artifacts in a folder named from its hash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100