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 path for sunbeam_config.yml #397

Open
scottdaniel opened this issue Apr 28, 2023 · 2 comments
Open

allow relative path for sunbeam_config.yml #397

scottdaniel opened this issue Apr 28, 2023 · 2 comments
Assignees

Comments

@scottdaniel
Copy link
Contributor

scottdaniel commented Apr 28, 2023

What's the feature?
In the config.yaml you have to put the absolute path of the sunbeam_config.yml
This would allow it to simply look in the directory where the config.yaml already resides

e.g.
configfile: "sunbeam4_config.yml" # would be nice if you could do it like this
instead of...
configfile: "/mnt/isilon/microbiome/analysis/danielsg/redding_run_4/Scripts/HPC_cluster/sunbeam4_config.yml"

@Ulthran
Copy link
Contributor

Ulthran commented May 1, 2023

Hi Scott,

Just tested this out and it seems like it probably won't work. The path has to relative to a sunbeamlib script it's read into instead of config.yaml.

sunbeam init should fill this in automatically for you though. I think we talked at some point about making a template file for the team so that you could use sunbeam init instead of copy/pasting.

e.g. this is an old pmacs template:

qc:
  human_genome_fp: "/project/bushmanlab/indexes/GCA_000001405.15_GRCh38_genomic.fna"
  phix_genome_fp: "/project/bushmanlab/indexes/phix174.fasta"

classify:
  kraken_db_fp: "/project/bushmanlab/kraken/standard"

blastdbs:
  root_fp: "/project/bushmanlab/genomeIndexes/blast"
  nucleotide:
    nt: nt/nt

Make a file like this with all the default values you want specified or overridden and then use sunbeam init --defaults /path/to/defaults/file.yml ....

@scottdaniel
Copy link
Contributor Author

scottdaniel commented May 1, 2023 via email

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

No branches or pull requests

2 participants