Figure out how to deal with a variable base_path
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Nextflow
- Stars
- 23
- Forks
- 6
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 6
Description
Description of feature
option 1
we keep the s3 path, and replace whatever path (ie s3://nf-core/references) with the provided path
option 2
we have a placeholder <REFERENCES_BASE> that we replace with the provided path
Contributor guide
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 reviewing the two proposed approaches in the issue: replacing the existing S3 path or introducing a <REFERENCES_BASE> placeholder. Identify where the pipeline currently defines and consumes its reference base path. Done means agreeing on and implementing a complete approach for variable base_path handling, but the issue does not name files or tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- bioinformatics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100