You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an enhancement request which would aid in being able to run GenomeChronicler for any reference genome.
It also helps avoid GATK conflicts with sarek resources, especially for the non-canonical chromosomes.
The idea would be that all the current files (listed below) are kept as defaults, but also exposed to the user as hyperparameters. This will allow me to expose them as parameters in the GenomeChronicler Nextflow process and keep them in sync with the former processes resource files.
Even further, we could separate each process within the main perl script and have it as N processes in a fully nextflow-ified version. As a grooming first step, we could update below in what step of GenomeChronicler uses the reference files/resources and continue from there.
Moving forward I think the different scripts need to be linked by a configuration file for each run, that will include all the parameters instead of being passed through the command line, that way an arbitrary number of parameters can be set and only passed once... once the manuscript is out of the door I'll look into doing that.
Sounds good to me! Since you already have familiarity with Sarek we can work together on this to implement it the pure nextflow way, so we will have a nextflow.config with defaults but also allow the user to custom-specify, either completely free, or with sensible options (eg. curated by us reference and resource bundles).
This is an enhancement request which would aid in being able to run
GenomeChronicler
for any reference genome.It also helps avoid GATK conflicts with sarek resources, especially for the non-canonical chromosomes.
The idea would be that all the current files (listed below) are kept as defaults, but also exposed to the user as hyperparameters. This will allow me to expose them as parameters in the GenomeChronicler Nextflow process and keep them in sync with the former processes resource files.
Even further, we could separate each process within the main perl script and have it as N processes in a fully nextflow-ified version. As a grooming first step, we could update below in what step of GenomeChronicler uses the reference files/resources and continue from there.
@afonsoguerra feel free to add
enhancement
label, since this is not a bug, but a nice-to-have addition.The text was updated successfully, but these errors were encountered: