Skip to content

Commit

Permalink
Update Changelogs (#364)
Browse files Browse the repository at this point in the history
* Update long-read-mngs readme

* Update short-read-mngs changelog
  • Loading branch information
lvreynoso authored May 21, 2024
1 parent eb1e2b6 commit 29224db
Show file tree
Hide file tree
Showing 2 changed files with 19 additions and 0 deletions.
7 changes: 7 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,13 @@ In addition, if a modification is made that may affect the results of a pipeline

### Unreleased

### short-read-mngs-v8.3.2
- Parameterize WDL version for Diamond workflow
- Remove SRST2 task
- Additional code to prioritize hits that are more specific in taxon-level
- Fixed an issue where certain network requests failed due to an interaction between Docker and the Python requests module.
### short-read-mngs-v8.3.1
- Add more logging output for SPAdes
### short-read-mngs-v8.3.0
- Convert Kallisto gene count to transcript count
### short-read-mngs-v8.2.7
Expand Down
12 changes: 12 additions & 0 deletions workflows/long-read-mngs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,18 @@ Further documentation on how to use the CZ ID long-read-mngs workflow can be fou
### Changelog

**v0.7.8** -- May 21, 2024 -- Adjust Diamond sensitivity
- Parameterizes the WDL version for the Diamond workflow. It is now a top-level input to the long-read-mngs WDL workflow.
- Added the `--sensitive` flag to Diamond invocations.
- Fixed an issue where certain network requests failed due to an interaction between Docker and the Python requests module.

**v0.7.7** -- April 29, 2024 -- Prioritize more specific taxon-level hits
- Changed some of the code that calls hits for read and contig queries to prioritize more specific hits over more general ones, i.e. species-level hits will be prioritized over genus-level, and genus-level over family-level. The most specific hit available will be chosen.

**v0.7.6** -- March 8, 2024 -- Bugfix for coverage viz output
- Fixed a bug that caused coverage viz output files to output the wrong contig file byteranges for contigs. Previously, the byteranges being output were for an intermediate file (one that filtered out contigs that did not have a corresponding read). GenerateCoverageViz now uses the full contigs file, which is a workflow output, as input and generates contig byteranges for this file.
Expand Down

0 comments on commit 29224db

Please sign in to comment.