Store results on macdatafile
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 21
- Forks
- 11
- Avg merge
- 12h 5m
- Merged PRs (30d)
- 24
Description
People have trouble finding the results files on the RAW_DATA folder, so maybe it would be better to store them on macdatafile. Also link to the consensus and amino frequencies files for the latest version right from the run folder.
- Look to see how much room they take up, and if there are some large files that we don't need to store. (unmapped FASTQ?)
- Change monitor script to write results to macdatafile.
- Link to latest conseqs and amino frequencies file right in run folder.
- Write version number to a latest_version.txt file in run folder.
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 reading the monitor script and inspecting the results currently stored under RAW_DATA versus macdatafile, including unmapped FASTQ files. Determine the storage impact, then verify that results are written to macdatafile, the run folder links to the latest consensus and amino frequencies files, and latest_version.txt contains the version number.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- bioinformatics
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100