Releases: nasa/GeneLab_Data_Processing
Releases · nasa/GeneLab_Data_Processing
NF_RCP-F_1.0.2
34b583f3ab427df64ab1856fb0faa482 NF_RCP-F_1.0.2.zip
NF_RCP-F_1.0.1
1ef161fefab400f8e686b1673dac4710 NF_RCP-F_1.0.1.zip
NF_RCP-F_1.0.0
LIMITATION NOTICE:
This workflow version was prior to the deployment of the OSDR. As such, usage with GLDS datasets will not work due to changes in OSDR/GeneLab api endpoints.
3ef3371316b02e43d3fb496d95e876bf NF_RCP-F_1.0.0.zip
SW_AmpIllumina-A_1.0.0
- Release holding asset for the first amplicon Illumina workflow version
SW_Amp454IonTor_1.0.0
- Release holding asset for the first amplicon 454 / ion torrent workflow version
GL_RefAnnotTable_1.0.0
- Release holding asset for the first generating reference annotation tables workflow version
SW_MGRemoveHumanReads-A_1.0.0
- Release holding asset for the first metagenomics human-read removal workflow version
SW_MGIllumina_2.0.2
- Release holding asset for Illumina metagenomics workflow version 2.0.2
- increasing bit package version in MG Illumina workflow
- some users were having trouble with conda installing an appropriate goatools on some systems with the bit version that was previously specified (goatools is a dependency of bit, but not something that is used by this workflow anyway), bumping to a later version of bit seems to resolve the issue
- increasing bit package version in MG Illumina workflow
SW_MGIllumina_2.0.1
- Release holding assets for Illumina metagenomis workflow version 2.0.1
- updated humann version from 3.5 to 3.6 in accordance with critical bug described here: https://forum.biobakery.org/t/announcing-humann-3-6-critical-update/4155
SW_MGIllumina_2.0.0
- Release holding asset for Illumina metagenomics workflow version 2.0.0
- the humann environment installs a specific version of humann, and humann grabs metaphlan as a dependency, but it didn't grab a specific version of metaphlan. So when metaphlan had later versions, even though we were installing the same version of humann, things were breaking.
- this included a (good) change in one metaphlan option from
--unknown_estimationto--unclassified_estimation, and changes to versions of reference databases being used
- this included a (good) change in one metaphlan option from
- now the env/humann3.yaml specifies humann=3.5 and metaphlan=4.0.1
- this is being released as a major version increase (1 to 2) because these changes were incompatible with the previous one
- the humann environment installs a specific version of humann, and humann grabs metaphlan as a dependency, but it didn't grab a specific version of metaphlan. So when metaphlan had later versions, even though we were installing the same version of humann, things were breaking.