Current workflow
This will be updated as pieces are developed and modified.
%%{init: { 'theme':'neutral' } }%%
flowchart TB
sources[(fasta files)]
sources --> combine --> MSA
click combine href "https://github.com/smutch/mccoy/blob/main/mccoy/workflow/rules/combine.smk"
MSA[multiple sequence alignment<br/>-- MAFFT] --> QC
click MSA href "https://github.com/smutch/mccoy/blob/main/mccoy/workflow/rules/align.smk"
subgraph QC["Quality control"]
tree[L_max tree<br/>-- iqtree2] --> RTR[root-tip regression]
click tree href "https://github.com/smutch/mccoy/blob/main/mccoy/workflow/rules/tree.smk"
otherQC[other checks]
end
QC --> XML[Beast XML generation<br/>-- Wytamma's scripts + templates + FEAST] --> OnlineBEAST[run, pause & update BEAST analysis<br/>-- Online BEAST] .-> Beastiary[monitor running BEAST jobs<br/>-- Beastiary]
click XML href "https://github.com/smutch/mccoy/blob/main/mccoy/workflow/rules/beast.smk"
click OnlineBEAST href "https://github.com/Wytamma/online-beast"
click Beastiary href "https://github.com/Wytamma/beastiary"
classDef complete fill:#48b884;
class gisaid,GISAIDR,sources,combine,MSA,tree,RTR,XML complete;
classDef inProg fill:#cc8400;
class otherQC,OnlineBEAST inProg;
Instructions
Ensure you have mamba (conda will work too, but mamba is strongly preferred), and poetry installed.
Step 1 - install the workflow
poetry install
To start using McCoy, you can either spawn a new shell with the McCoy Poetry environment enabled:
poetry shell
or you can replace every instance of mccoy in the commands below with poetry run mccoy.
The workflow is being developed such that all required software will be automatically installed for each step of the pipeline in self-contained conda environments. These environments will be cached and reused whenever possible (all handled internally by snakemake), but if you want to remove them then they can be found in .snakemake.
Step 2 - Create a McCoy project
First begin by creating a new McCoy project (called test in this example):
mccoy create test --reference resources/reference.fasta --template resources/templates/CoV_CE_fixed_clock_template.xml
The reference and template options are required. At the moment we are distributing these reference and template files, however, once we reach v1.0, these will be removed and the useer will have to ensure they have appropriate reference and template files available.
The config for this project can be altered by editing the newly created file test/config.yaml.
Step 3 - Run the project!
To run the newly created project:
mccoy run test --data resources/omicron_test-original.fasta
Again, the data option here is required. This command will create a new directory in test/runs with the workflow results and output.
Step 4 - Add new data
Subsequent calls to mccoy run will result in a whole new run of the pipeline from start-to-finsh unless the --inherit or --inherit-last flags are used. See mccoy run --help for more information. Inheriting from a previous run will use the data and MCMC state as a starting point for the new data.
mccoy run test --data resources/omicron_test-extra.fasta --inherit-last
As well as directly altering a project's config.yaml, config variables can be overridden on the command line. e.g.:
mccoy run --data resources/omicron_test-original.fasta --config align='{mafft: ["--6merpair", "--addfragments"]}'
Any options passed to mccoy run that are not listed in mccoy run --help will be directly forwarded on to Snakemake. See mccoy run --help-snakemake for a list of all available options.
Metadata
Release files for mccoy 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| mccoy-0.1.2.tar.gz | 98.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mccoy-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 207.8 kB
Release files / mccoy-0.1.2.tar.gz
| Download URL | mccoy-0.1.2.tar.gz |
|---|---|
| Size | 98.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
340f0de330fe86fb308ec8a7a50cc4830796c84d9891bafecfca4245d3787765
|
|
BLAKE2b-256 checksum How to use checksums |
a0743ee2db1f2dcce53ef8e150c173d66cdc44cf18d642be983980758780a72c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.2.1 CPython/3.8.10 Linux/5.15.0-1019-azure
|
Release files / mccoy-0.1.2-py3-none-any.whl
| Download URL | mccoy-0.1.2-py3-none-any.whl |
|---|---|
| Size | 109.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4ac392edd0c409c53ea1c40f8fb4f57034219e58ad96b5420f078977d03728a5
|
|
BLAKE2b-256 checksum How to use checksums |
d0b2d6da92aae492e070599be7407bc4d4c01521aeb6a166fa715b1c256b5fdf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.2.1 CPython/3.8.10 Linux/5.15.0-1019-azure
|
Security for mccoy 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.