Mavis

Latest version: v3.1.2

Safety actively analyzes 630305 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 9

2.1.4

BugFix
- Warn only on missing aligner instead of throwing error so that mavis can be used as a package dependency

2.1.3

BugFixes

* 151 Allow summary to collapse all events by distance if they are called the same way, not just events called by split reads

2.1.2

BugFixes

- support scheduler job time formats >1 day
- support ext hgvs variants
- breakpoint ordering for duplications within repeats

2.1.1

BugFixes
- Fixed minor drawing bug for very small genes with a single exon

Documentation
- Added citation information to README

2.1.0

Improvements
* Allow strelka indels to be a valid input to convert/config

bugfix
* 136 Fix issue where the path to the blat binary could not be found.

2.0.0

MAVIS 2.0.0 has similar underlying mechanics to its predecessors in how it validates and processes structural variants. However, significant improvements to how MAVIS interacts with the scheduler have been made. This should improve the user experience.

**New Features**
- MAVIS now uses pythons built-in logging module so that different levels of logging can be selected to help debugging if uses encounter issues.
- MAVIS can be run locally without a scheduler, instead setting up its own multiprocessing using pythons concurrent.futures library
- Increased integration with schedulers to automate submitting, resubmitting, and monitoring jobs
- Support for buildout. This allows the user to create a mavis binary rather than having to install MAVIS into an existing python. This will improve the process of setting up and integrating MAVIS into existing bioinformatic pipelines
- A second tutorial which uses a smaller dataset and can be run locally on the average personal computer has also been added. This will make it easier for users to evaluate their MAVIS install

**Improvements**
- Ignores and logs problem (invalidly formatted) reads, instead of throwing an error. This will allow users to proceed even when their BAM file may contain 'dirty' reads.

Page 4 of 9

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.