Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow relative file paths #257

Open
wants to merge 2 commits into
base: dev
Choose a base branch
from
Open

Allow relative file paths #257

wants to merge 2 commits into from

Conversation

RamiyapriyaS
Copy link
Collaborator

Description

Changes allow for command line parameters to be provided as relative paths.

Checklist

Go Through Checklist Below and Place A ✔️ (X Inside the Box) if Completed

General Checks

  • Have you run appropriate tests (unit/integration/end-to-end) to check logic across run environments (Conda/Docker/Singularity on Scicomp/AWS/NF Tower/Local)?

    For each relevant configuration:

    • Can the program run completely through without erroring out? Yes
    • Does it produce the expected outputs, given the inputs provided? Yes

@RamiyapriyaS
Copy link
Collaborator Author

PR Testing:

Run the pipeline with relative paths for the following parameters: meta_path, submission_config, ref_fasta_path, ref_gff_path, and bakta_db_path.

Example command:

nextflow run main.nf -profile test,singularity --species virus --annotation --submission --output_dir rjd0_rel_path --submission_config conf/submission_config.yaml --ref_fasta_path assets/ref/ref.MPXV.NC063383.v7.fasta

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Internal] [Bug] 'Not a valid path value:' for relative paths on command line
1 participant