Msstitch

Latest version: v3.15

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

Scan your dependencies

Page 3 of 5

3.3

Added
- Added `--dinosaur` to store results from MS1 quant using dinosaur, include FWHM data
- Added median-intensity (i.e. not ratio) summarization to `isosummarize` and `proteins` etc

Changed
- Choose between MS1 apex and MS1 sum for quantification
- Choose between median and average when summarizing isobaric PSM data

Fixed
- Bug in MS1 feat to PSM scan aligment, `ORDER BY` had been removed in `9717325837853de159ede5e77191b0c7de032820`

3.2

Changed
- `msstitch merge --no-group-annotation` does output a protein(s) column for whatever accession is in the DB

Fixed
- Corrected typo in column to index on for ensg_proteins table (gene_id), which made merging ENSG very slow

3.1

Fixed
- Quant lookup on consensusXML stored channels in wrong order when >10 channels eg in TMT16
- --spectracol argument in msstitch psmtable did not work

3.0

Breaking
- Completely new interface, one command (msstitch), some subcommands, merged several
functionalities (e.g. SQLite creation/output) into fewer steps.

Added
- Possible to add ion mobility value of scans to PSM table

Changed
- Updated README
- Output column name changes (esp Gene ID/ Gene name from symbols)
- peptide sequence in first column of peptide table output
- trypsinize adds peptide index to fasta output as to not create duplicate entries
- PSM table creator does not longer take a mapfn from biomart, all info comes from fasta header
- Consequently, picked FDR can now work on ENSG ID and gene names
- SQLite creation for spectra has possiblity to specify output file
- Percolator output splitprotein different behaviour: can specify "known" prot headers which excludes all scans with those annotations,
when not specified it keeps any scan for a header (also if other headers are specified)

Fixed
- msslookup quant no longer stores duplicates if >500.000 scans, those first 500.000 were stored twice

Removed
- percolator split/merge/filter/qvality scoring, only kept protein identity splitting
- Protein error probability output

2.19

Fixed
- Protein FDR calculation for ENSG entries was correct but only if the fasta file contained a decoy_ prefix on the ENSG entries, which they did not
in the case of makedecoy generated.

2.18

Changed
- makedecoy shuffles x times and then does no longer throw out the peptide but keeps the original decoy. Otherwise the decoy database gets smaller

Fixed
- makedecoy with target checking works also on long proteins, which exceed the max parameter setting for SQLite

Page 3 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.