imicroseq / imicroseq/singularity
Allow passing TSV columns through environment variables
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
As described here https://wiki.oicr.on.ca/pages/viewpage.action?pageId=191465562, TSVs are generated programatically through a lot of hardcoded values that should be dynamic.
This change is necessary so that Singularity can be reused in other projects.
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 linked wiki page and locating where TSVs are generated in the repository. Identify the hardcoded columns and the expected environment-variable interface; done means the TSV columns can be configured for reuse in other projects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100