Open rpetit3 opened 1 year ago
@rpetit3, In my mind the output of this would just tell you if your samples passed QC. So you would get a file back that said PASS/FAIL and the reason why for each sample. Why does it then run further analysis? Our team is developing an entry (-entry scaffolds) that would take in assemblies and check some QC and then run everything post SPAdes. It seems like there might be some over lap with what you had in mind?
There are some steps in PHOENIX
that require custom databases (e.g. kraken and gamma). I thought it best to have PHOENIX
handle that for the user, instead of alternate pipelines integrating it into their own.
Duplicate of https://github.com/CDCgov/phoenix/pull/83
This PR adds a new entry point for PHoeNIx, called
PHOENIX_QC
. What this does is allow users to run their samples through other pipelines, then determining if their samples pass PHoeNIx QC metrics.PHOENIX_QC
requires a different type of CSV file with the following columns:The remained steps in
PHOENIX_QC
match the rest of thePHOENIX
pipeline. I thought it best to let analyses (e.g. kraken, gamma) with PHoeNIx-specific databases still be handled by PHoeNIx.Right now I've pointed this at the
v1.2.0-dev
branch.Happy to take any suggestions and feedback.