Skip to content

Wrangler#107

Closed
KasperThystrup wants to merge 9 commits intodevfrom
wrangler
Closed

Wrangler#107
KasperThystrup wants to merge 9 commits intodevfrom
wrangler

Conversation

@KasperThystrup
Copy link
Copy Markdown
Collaborator

Adding a wrangler requires a lot of restructuring. Thus this PR wil drastically change the software architecture. I suggest to merge everything prior to this branch, and then to re-clone repo once this has been merged.

A lot of restructuring and cleanup has been made, to facilitate a meaningful wrapper. This commit includes:
* A conceptual wrapper script
* Removal of unused variables
* A deployment_dir which are used to store databases and conda environments, as created by snakemake.
* Reorganisation of files.
  * Metadata renamed to target_screening for now
  * Analysis relevant files are moved into config/analysis (e.g. species_configs)
  * reads/ and assemblies/ folder now located in data folder
  * samplesheet now located in data folder
  * examples/ folder removed
  * Added Test and Deploy to .gitignore, I suggest to use Test/Results for output_folder, and Deploy for deployment_dir
* MLST-db-update rule removed completely, as MLST has removed the update script
* Illumina and Assembly paths removed from config and snakefile, now it must be specified directly in the samplesheet
* Samplesheet changes:
  * Adeded Illumina_mate1 and _mate2
  * Removed Nanopore path
  * Renamed Assembly path variable
* Removed sample_to_illumina, _to_nanopore, & _assembly vars and replaced with samplesheet
* Samples can be accessed as samplesheet.index
* Updated rules to acces samplesheet directory
Replaced lambda wildcards with lambda wc, to avoid confusion with snakemake.wildcards object
@SimoneScrima
Copy link
Copy Markdown
Collaborator

SimoneScrima commented Feb 9, 2026

Maybe the config.yaml can be further streamlined of the illumina and nanopore reads path since they are specified in the samplesheet, the path is taken from there and not from the config.yaml, same as the assembly path and configuration file for the species. It is a bit redundant.

Launcher has been added. Now config files are automatically created and executed FROM the launcher. A bit of polishing has been provided for all downstream files for supporting new launcher. Symbolic links of assembly files has NOT YET been added!
* If assemblies specified in samplesheet exists, it will be symlinked (unless allready exists as file and not link in results)
* Tool versioning removed from assemblies, as this would disrupt the circumvension of assembly linking - Think about alternatives see #112
* Migrated contents of config/analysis into config/ for simplicity
@KasperThystrup KasperThystrup added Ready Ready for merge upon confirmation from non-author and removed Ready Ready for merge upon confirmation from non-author labels Feb 11, 2026
@KasperThystrup KasperThystrup added the Ready Ready for merge upon confirmation from non-author label Feb 11, 2026
@KasperThystrup
Copy link
Copy Markdown
Collaborator Author

Should be working now

@KasperThystrup
Copy link
Copy Markdown
Collaborator Author

Closed for now, since it's already been merged into pkging branch (#110)

@KasperThystrup KasperThystrup removed the Ready Ready for merge upon confirmation from non-author label Feb 12, 2026
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.

2 participants