msInspect Commandline Functions Manual

Introduction

This manual describes all of the commandline functionality available in msInspect. To access any of these commands, type the java command that you use to start msInspect (e.g., 'java -Xmx1G -jar viewerApp.jar'), followed by ' --<command>' (the name of the command), followed by any arguments. Argument names are not case-sensitive.

To access a graphical interface for entering arguments for any command (with graphical help for choosing files, etc.), use the command '--interactive', followed by the name of the command you wish to execute.

All commandline functions may also be accessed through the msInspect graphical user interface using the 'Run Command' menu item under the 'File' menu.

For more information about msInspect, as well as help with the graphical user interface, go to the official msInspect webpage at http://proteomics.fhcrc.org/CPL/msinspect.html

Required arguments for each command are indicated in bold text in the arguments table. In some cases, additional arguments may be required if certain arguments are specified. Some commands have 'advanced' arguments, which are never required; it is not recommended to specify values for those arguments unless you know exactly what you're doing.

In addition to the arguments discussed below for each particular command, msInspect accepts two special arguments for all commands:

  1. --log : Turn on logging of all output messages to a log file (log file location can be specified with --log=<filepath>)
  2. --debug : Turn on full debug logging of all Java classes (individual class names can also be specified with --debug=<full_class_name>,<full_class_name>...

This document automatically generated on August 12, 2009 by msInspect revision 382. If you are running a newer version of msInspect, you may generate the current version of this document with the 'usermanual' command.

Table of Contents

The available commands are divided into sections: General, Quantitation, Alignment, MS/MS, AMT, MRM, Quality Assurance

General

General msInspect tools

CommandSummary
analyzehydroalgTemplate command for analyzing a hydrophobicity algorithm
calibratefeaturemassesPerform mass calibration on a set of high-mass-accuracy peptide features
calibratemzxmlmassesPerform mass calibration on mzXML spectra
consensusfeaturefile(no description)
convertfeaturefileConvert between formats of feature files
createindex(no description)
deconvoluteDeconvolute
detectadductsDisplay a chart showing MS1 feature masses at different intervals above MS2 feature masses
dumpwindow2dCreate a feature file that contains a 2D window of spectra around each feature
filterFilter feature sets based on various critera
findpeptidesFind features in an mzXML file based on various critera
massaccuracyDetermine MS1 mass accuracy by matching to MS2
matchfeaturesperform simple feature-matching
modelpeptide(no description)
plotfeatureattributesHistograms attributes of featuresets
plotmasscalibrationVisualizes the mass calibration of a feature file as a scatterplot
plotms1ms2scancountsPlots scan counts
runcommandfileRun the commands specified in a command file
saveimageCreate an image file containing a visualization of a run
savemzxmlwindowSave a partial window from an mzXml file, limited by scan and MZ
spreadsheetmergemerge spreadsheets
usermanualCreate a user manual for commandline functions
viewspectrumPeptideSpectrumChart

Quantitation

Tools related to labeled and unlabeled quantitation

CommandSummary
icatICAT Quantitation
peptideratiovariationpeptideratiovariation
proteinquantchartsproteinquantcharts
q3newRun Q3 quantitation on a pepXml file
quantQuantitate
quantchartsCreate charts showing the MS1 spectra near quantitative events for specified peptides or proteins
qurateReview quantitation charts

Alignment

Tools for aligning multiple runs, including Peptide Arrays

CommandSummary
alignAlign feature sets
analyzepeparrayTools for analyzing peptide arrays.
peptidearrayCreate a peptide array from two or more feature files

MS/MS

Tools related to tandem mass spectrometry and the file formats used for tandem MS

CommandSummary
calcfdrUse reverse database hits to calculate False Discovery Rate and filter.
combinepepxmlfilescombinepepxmlfiles
comparefastascompare fastas
correctprecursormzPerform mass correction on mzXML precursor masses
extractrunsfrompepxmlExtract individual runs from a multi-fraction PepXML file
filterpeptideregexp(no description)
filterpepxml(no description)
filterreversedbhits(no description)
findindistinguishableproteinsfindindistinguishableproteins
flippepxmlratiosFlip peptide ratios and light/heavy areas
guessproteinsfromfastaPopulate (guess at) the protein for each identified peptide, by looking at the specified FASTA and using the first protein that contains the peptide
ms2scanviewerms2scanviewer
peptidecompareCompare peptide IDs between multiple runs
picktargetedms2candidatespicktargetedms2candidates
plotdeltamassesPlot deltaMass values against feature masses
populatems2timesPopulate clock time information for a set of MS2 features
postprocesspepxmlPost-process PepXML. This provides tools for stripping out peptides and median-centering log ratios.
proteinfractionsspreadsheetCreate a spreadsheet assigning proteins to fractions
protxmlcompareCompare two protXML files
reversefasta(no description)
searchscorecutoffUse reverse database hits to determine the performance of a search score
spectralcountCreate a spreadsheet with spectral count information
summarizeprotxmlSummarize the contents of one or more protXML files

AMT

Accurate Mass and Time analysis tools

CommandSummary
amtdiagnosticGet various kinds of information about an AMT database.
amtlabeledquantPerforms labeled quantitation by mining AMT results for isotopic pairs.
combineamtms2Combine MS/MS results (pepxml or feature files) with AMT results (pepxml or feature files)
createamtCreate an AMT database.
createamtfeaturesetA tool for creating feature sets from amt databases
manageamtTools for managing an AMT database
matchamtMatch between AMT databases and MS1 feature files
proteinrollupTools for rolling up peptide information to the protein level.

MRM

The MRMer tools for Multiple Reaction Monitoring

CommandSummary
mrmMRMer is used to display, quantify, and edit MRM scans

Quality Assurance

Quality Assurance tools

CommandSummary
qaexperimentPerform QA analysis on a single experiment
qaprotxmlPerform QA analysis on a single protXML file



General

General msInspect tools


analyzehydroalg

This command analyzes the Krokhin peptide hydrophobicity prediction algorithm (v3). It runs the algorithm on all tryptic peptides from a given FASTA file, and returns the mean and standard deviation. It also serves as a template for analyzing other algorithms.

Usage:

--analyzehydroalg --fasta=<filepath>

Arguments:

ArgumentUsageDefaultDescription
fasta<filepath>nullfasta file containing database to digest


calibratefeaturemasses

This tool is used to correct high-accuracy features for mass miscalibration, based on theoretical properties of the distribution of peptide masses. Based on work by Wolski et al., 2006

Usage:

--calibratefeaturemasses [--initialfilterppm=<integer>] [--maxpairs=<integer>] [--out=<filepath>] [--outdir=<filepath>] [--partitions=<integer>] [--showcharts=<true | false>] [--theoreticalwavelength=<decimal>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullInput feature file(s)
initialfilterppm<integer>0Initial ppm value used as a pre-calibration cutoff. Features deviating from theoretical clusters (BEFORE calibration) will be filtered out during calibration. However, those features WILL appear in the recalibrated featureset, with corrected masses. Default = no filter
maxpairs<integer>500000Maximum number of mass pairs to be considered (higher numbers may increase accuracy, but will take much longer)
out<filepath>nullOutput file (for single input files)
outdir<filepath>nullOutput directory (for multiple input files)
partitions<integer>1Number of partitions to break the file into (higher numbers are more expensive)
showcharts<true | false>falseShow charts
theoreticalwavelength<decimal>1.000476Theoretical mass cluster wavelength


calibratemzxmlmasses

Calibrates the masses in mzXML spectra, based on supplied parameters, or on the calibration properties of a specified feature file This should work well when mass miscalibration is a function of M/Z (e.g., in some TOF data). If it's a function of mass that behaves differently for different charge states (e.g., some LTQFT data), this will not give good results.

Usage:

--calibratemzxmlmasses [--features=<filepath>] [--featuresdir=<filepath>] [--initialfilterppm=<integer>] [--offset=<decimal>] [--onlyms2precursormasses=<true | false>] [--out=<filepath>] [--outdir=<filepath>] [--outfeatures=<filepath>] [--partitions=<integer>] [--scanchargefeatures=<filepath>] [--scanchargefeaturesdir=<filepath>] [--wavelength=<decimal>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullInput mzXML file(s)
features<filepath>nullFeature file to use in recalibration
featuresdir<filepath>nullDirectory of feature files to use in recalibration
initialfilterppm<integer>0Initial ppm value used as a pre-calibration cutoff. Features deviating from theoretical clusters (BEFORE calibration) will be filtered out during calibration. However, those features WILL appear in the recalibrated featureset, with corrected masses. Default = no filter
offset<decimal>nullOffset
onlyms2precursormasses<true | false>falseOnly recalibrate MS2 precursor masses
out<filepath>nullOutput File
outdir<filepath>nullOutput Directory (for multiple inputs)
outfeatures<filepath>nullOutput recalibrated feature file
partitions<integer>1Number of partitions by scan
scanchargefeatures<filepath>nullFeature file to use to assign charges to MS/MS scans
scanchargefeaturesdir<filepath>nullDirectory of feature files to use for determining charge states
wavelength<decimal>nullWavelength


consensusfeaturefile

Usage:

--consensusfeaturefile [--minfeatureruns=<integer>] [--out=<filepath>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullinput feature files
minfeatureruns<integer>2minimun number of runs a feature must appear in
out<filepath>nulloutput file


convertfeaturefile

This command converts between different formats of feature files. Allowed formats: msinspect: msInspect tab-separated values pepxml: PepXML specarraytsv: SpecArray tab-separated values apml: APML v2.0 (XML) hardklor: Hardklor text format multimsinspect: Multiple msInspect feature sets in a single file, with a column indicating run

Usage:

--convertfeaturefile --outformat=<msinspect | pepxml | specarraytsv | apml | hardklor | multimsinspect> [--dumpwindow=<true | false>] [--fasta=<filepath>] [--forcepeptideprophetvalue=<decimal>] [--informat=<msinspect | pepxml | specarraytsv | apml | hardklor | multimsinspect>] [--mzxml=<filepath>] [--out=<filepath>] [--outdir=<filepath>] [--specarrayversion=<1.0 | 1.2>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullInput feature file(s)
outformat<msinspect | pepxml | specarraytsv | apml | hardklor | multimsinspect>nulloutput file format
dumpwindow<true | false>null(no details provided)
fasta<filepath>nullFASTA filepath to include in pepXML file (for outformat=pepxml only)
forcepeptideprophetvalue<decimal>nullSet the PeptideProphet probability of all features to this (for pepxml output)
informat<msinspect | pepxml | specarraytsv | apml | hardklor | multimsinspect>msinspectinput file format. To force loading of an ambiguous file as a specific file type
mzxml<filepath>null(no details provided)
out<filepath>nulloutput file
outdir<filepath>nulloutput directory (for multiple inputs)
specarrayversion<1.0 | 1.2>nullspecArray version, for specArray conversions (default 1.2)


createindex

Usage:

--createindex <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullA series of feature files to index


deconvolute

Deconvolute

Usage:

--deconvolute [--deltamass=<mass value>da|ppm] [--deltatime=<decimal>] [--heavytagweight=<decimal>] [--intensitytype=<total | max | recalculated>] [--labeledresidue=<value>] [--lighttagweight=<decimal>] [--masswindow=<decimal>] [--maxlabelcount=<integer>] [--msfile=<filepath>] [--out=<filepath>] [--outdir=<filepath>] [--quant=<true | false>] [--scanwindow=<integer>] [--showcharts=<true | false>] [--sumintensities=<true | false>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullInput File(s)
deltamass<mass value>da|ppm0.2daMass Tolerance
deltatime<decimal>10.0Time Tolerance
heavytagweight<decimal>-1.0Heavy tag weight
intensitytype<total | max | recalculated>nullIntensity type
labeledresidue<value>nullLabeled Residue
lighttagweight<decimal>-1.0Light tag weight
masswindow<decimal>0.4Mass Window
maxlabelcount<integer>3Maximum Label Count
msfile<filepath>nullmzXml File
out<filepath>nullOutput File
outdir<filepath>nullOutput Directory (for multiple files)
quant<true | false>falseQuantitate
scanwindow<integer>6Scan Window
showcharts<true | false>falseShow Charts
sumintensities<true | false>trueIf true, deconvoluted feature intensities reflect the sum of all component feature intensities. If false, intensity of most-intense feature is kept.


detectadducts

Display a chart showing MS1 feature masses at different intervals above MS2 feature masses. Highly experimental

Usage:

--detectadducts [--deltamass=<mass value>da|ppm] [--masswavelength=<decimal>] [--maxrelativedaltons=<integer>] [--maxrelativeseconds=<integer>] [--minrelativedaltons=<integer>] [--minrelativeseconds=<integer>] [--scanwindowsize=<integer>] [--secondsincrement=<integer>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullFeature File of features to interrogate
deltamass<mass value>da|ppm10.0ppmMass tolerance around each Dalton increment
masswavelength<decimal>1.000476Mass wavelength
maxrelativedaltons<integer>100Maximum Daltons, relative to original mass
maxrelativeseconds<integer>60(no details provided)
minrelativedaltons<integer>0Minimum Daltons, relative to original mass
minrelativeseconds<integer>-60(no details provided)
scanwindowsize<integer>1Size of the scan window (including identity scan)
secondsincrement<integer>1(no details provided)


dumpwindow2d

The dumpwindow2d command creates a feature file that contains a 2D window of spectra around each feature

Usage:

--dumpwindow2d --features=<filepath> [--leadingpeaks=<integer>] [--leadingscans=<integer>] [--out=<filepath>] [--trailingpeaks=<integer>] [--trailingscans=<integer>] <filepath>

Arguments:

ArgumentUsageDefaultDescription
(unnamed)<filepath>nullmzXML File
features<filepath>nullFeature file
leadingpeaks<integer>1Leading Peaks
leadingscans<integer>4Leading Scans
out<filepath>nulloutput file
trailingpeaks<integer>1Leading Peaks
trailingscans<integer>4Trailing Scans


filter

The filter command allows you to one or more feature files based on various criteria. The out parameter specifies a feature file for output. You may filter features based on ma, mass, peaks, charge, kl, intensity, time, or scans. If you wish to filter more than one file at once, you will need to specify the outdir parameter, to indicate the output directory. The output filenames will be based on the input filenames, ending in '.filtered.tsv'

Usage:

----filter [--out=filename] [--outdir=directory] [--minMz=float] [--maxMz=float] [--minMass=float] [--maxMass=float] [--minPeaks=int] [--maxPeaks=int] [--minCharge=int] [--maxCharge=int] [--maxKL=float] [--minIntensity=float] [--minTotalIntensity=float] [--minTime=float] [--maxTime=float] [--scanFirst=int] [scanLast=int] [--minScans=int] [--minpprophet=float] [--maxmassdeviationppm] [--outputpepxml] [--maxsumsquaresdist=float] [--minsearchscore=float] [--maxsearchscore=float] [--searchscorename=string] [--accmz=true|false] [--outformat=msinspect|pepxml] featurefile [featurefile] [featurefile] ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullInput feature file(s)
accmz<true | false>nullAccurate m/z only?
maxcharge<integer>nullMaximum charge
maxkl<decimal>nullMaximum K/L score
maxmass<decimal>nullMaximum mass
maxmassdeviationppm<integer>nullMaximum deviation from nearest theoretical mass cluster, in PPM
maxmz<decimal>nullMaximum M/Z value
maxpeaks<integer>nullMaximum number of peaks
maxsearchscore<decimal>3.4028234663852886E38Maximum search score
maxsumsquaresdist<decimal>nullMaximum sum-squares distance score
maxtime<decimal>nullMaximum time
mincharge<integer>nullMinimum charge
minintensity<decimal>nullMinimum intensity
minmass<decimal>nullMinimum mass
minmz<decimal>nullMinimum M/Z value
minpeaks<integer>nullMinimum number of peaks
minpprophet<decimal>nullMinimum PeptideProphet score
minscans<integer>nullMinimum number of scans covered
minsearchscore<decimal>1.401298464324817E-45Minimum search score
mintime<decimal>nullMinimum time
mintotalintensity<decimal>nullMinimum total intensity
out<filepath>nullOutput File
outdir<filepath>nullOutput Directory (for filtering multiple files)
outformat<msinspect | pepxml>null msinspect: msInspect .tsv format pepxml: pepXML format
scanfirst<integer>nullMinimum scan number
scanlast<integer>nullMaximum scan number
searchscorename<value>nullSearch score name (for minsearchscore or maxsearchscore)


findpeptides

The findpeptides command finds peptide features in an mzXML file, based on the criteria supplied. By default, only features with at least 2 peaks and a K/L score less than 3.0 are kept.

Usage:

----findPeptides [--dumpWindow=windowSize] [--out=outfilename] [--outdir=outdirpath] [--start=startScan] [--count=scanCount] [--minMz=minMzVal] [--maxMz=maxMzVal] [--strategy=className] [--noAccurateMass] [--accurateMassScans=<int>] [--walkSmoothed] mzxmlfile

Basic Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullInput mzXML file(s)
count<integer>2147483647Number of scans to search
maxmz<decimal>nullMaximum M/Z Value (default: the maximum m/z value in the file)
minmz<decimal>nullMinimum M/Z Value (default: the minimum m/z value in the file)
out<filepath>nullOutput File
outdir<filepath>nullOutput Directory (for finding features in multiple files)
start<integer>1Minimum scan number
strategy<value>nullClass name of a feature-finding strategy implementation

Advanced Arguments:

ArgumentUsageDefaultDescription
accuratemassscans<integer>3When attempting to improve mass-accuracy, consider a neighborhood of <int> scans
dumpwindow<integer>0Number of scans around each feature to dump to the file
maxkl<decimal>3.0Maximum K/L quality score
minpeaks<integer>2Maximum K/L quality score
noaccuratemass<true | false>falseDo NOT attempt mass-accuracy adjustment after default peak finding strategy (by default, adjustment is done)
nofilter<true | false>falsePerform no filtering on identified features. By default, only features with at least 2 peaks and a K/L score less than 3.0 are kept. (overrides maxkl and minpeaks)
plotstats<true | false>falsePlot statistics related to feature-finding
walksmoothed<true | false>falseWhen calculating feature extents, use smoothed rather than wavelet-transformed spectra)


massaccuracy

calculate the mass accuracy of ms2 features

Usage:

--massaccuracy --ms1features=<filepath> --ms2features=<filepath> --mzxml=<filepath> [--deltamass=<mass value>da|ppm] [--deltatime=<decimal>] [--minpprophet=<decimal>]

Arguments:

ArgumentUsageDefaultDescription
ms1features<filepath>nullMS1 features
ms2features<filepath>nullMS2 features
mzxml<filepath>nullmzXML file
deltamass<mass value>da|ppm5.0ppmMaximum mass difference between matched features (in units of da [Daltons] or ppm [parts per million]
deltatime<decimal>nullMaximum time between matched features
minpprophet<decimal>nullMinimum PeptideProphet score


matchfeatures

perform feature-matching between different sets of features

Usage:

--matchfeatures --ms1features=<filepath> [--align=<true | false>] [--amtdbtoexclude=<filepath>] [--deltamass=<mass value>da|ppm] [--deltascan=<integer>] [--deltatime=<decimal>] [--fasta=<filepath>] [--matchonhydro=<true | false>] [--minpprophet=<decimal>] [--mode=<ms1ms2 | ms1ms2dir>] [--modifications=<residue><massdiff>[V][,...]] [--ms2dir=<filepath>] [--ms2features=<filepath>] [--mzxml=<filepath>] [--out=<filepath>] [--outallms2marked=<filepath>] [--outunmatchedms2=<filepath>] [--showcharts=<true | false>] [--stripmultiplems2=<true | false>] [--writeunmatched=<true | false>]

Arguments:

ArgumentUsageDefaultDescription
ms1features<filepath>nullMS1 feature file
align<true | false>falsealign all MS2 runs to the MS1 run being matched
amtdbtoexclude<filepath>nullan AMT database whose peptides should be excluded from protein matching
deltamass<mass value>da|ppm5.0ppmMaximum mass difference between matched features (in units of da [Daltons] or ppm [parts per million]
deltascan<integer>3Maximum number of scans between matched features
deltatime<decimal>20.0Maximum time between matched features
fasta<filepath>nullFasta database for matching
matchonhydro<true | false>falseunder the hood, perform matching based on hydrophobicity
minpprophet<decimal>0.0Minimum PeptideProphet score
mode<ms1ms2 | ms1ms2dir>ms1ms2Mode of operation, default ms1ms2
modifications<residue><massdiff>[V][,...]nulla list of modifications to use when creating features to represent peptide sequences
ms2dir<filepath>nullMS2 feature file directory
ms2features<filepath>nullMS2 feature file (usually pepXml)
mzxml<filepath>nullmzXML file
out<filepath>nullOutput File
outallms2marked<filepath>nullOutput File for all MS2, with unmatched having 'unmatched' in description
outunmatchedms2<filepath>nullOutput File for unmatched MS2
showcharts<true | false>falseshow useful charts created when matching
stripmultiplems2<true | false>trueStrip subsequent MS2 identifications for the same peptide out of the file when matching
writeunmatched<true | false>trueWrite out unmatched features


modelpeptide

Usage:

--modelpeptide --daltons=<decimal>

Arguments:

ArgumentUsageDefaultDescription
daltons<decimal>nullpeptide mass


plotfeatureattributes

asdfasdf

Usage:

--plotfeatureattributes --attribute=<pprophet | fracdeltamass | intensity | time | ratio | lightarea | charge | sumsquaresdist | kl | peaks | searchscore | fval | mass | mz> [--attribute2=<pprophet | fracdeltamass | intensity | time | ratio | lightarea | charge | sumsquaresdist | kl | peaks | searchscore | fval | mass | mz>] [--breaks=<integer>] [--logmode=<true | false>] [--out=<filepath>] [--outdir=<filepath>] [--plottype=<histogram | scatter | boxplot>] [--searchscore=<value>] [--showcharts=<true | false>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullFeature file(s)
attribute<pprophet | fracdeltamass | intensity | time | ratio | lightarea | charge | sumsquaresdist | kl | peaks | searchscore | fval | mass | mz>null pprophet: PeptideProphet probabilities fracdeltamass: Fractional Delta Mass intensity: (Maximum) Intensity time: Retention Time ratio: Ratio lightarea: Light Area (quantitated peptides) charge: Charge sumsquaresdist: Sum-of-squares distance kl: K/L Score peaks: Number of peaks searchscore: Search score (must provide score name) fval: fval mass: mass mz: mz
attribute2<pprophet | fracdeltamass | intensity | time | ratio | lightarea | charge | sumsquaresdist | kl | peaks | searchscore | fval | mass | mz>null pprophet: PeptideProphet probabilities fracdeltamass: Fractional Delta Mass intensity: (Maximum) Intensity time: Retention Time ratio: Ratio lightarea: Light Area (quantitated peptides) charge: Charge sumsquaresdist: Sum-of-squares distance kl: K/L Score peaks: Number of peaks searchscore: Search score (must provide score name) fval: fval mass: mass mz: mz
breaks<integer>100Number of breaks
logmode<true | false>falseLog mode
out<filepath>null(no details provided)
outdir<filepath>null(no details provided)
plottype<histogram | scatter | boxplot>null histogram: Histogram scatter: Scatterplot boxplot: Box and whiskers plot
searchscore<value>nullSearch score name (for searchscore mode)
showcharts<true | false>trueShow charts?


plotmasscalibration

Visualizes the mass calibration of a feature file as a scatterplot, based on work by Wolski et al., 2006. X axis is feature mass. Y axis is the distance from the nearest theoretical mass cluster. Optionally display lines indicating a given ppm deviation from theoretical mass

Usage:

--plotmasscalibration [--indir=<filepath>] [--out=<filepath>] [--outboxwhiskersplot=<filepath>] [--ppmline=<decimal>] [--showcharts=<true | false>] [--theoreticalwavelength=<decimal>] [--usemz=<true | false>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>null(no details provided)
indir<filepath>nullDirectory containing input files, all of which will be used
out<filepath>null(no details provided)
outboxwhiskersplot<filepath>nullFile to save box-and-whiskers plot to
ppmline<decimal>-1.0PPM cutoff to display on plot (default none)
showcharts<true | false>trueShow charts?
theoreticalwavelength<decimal>1.000476Theoretical mass cluster wavelength
usemz<true | false>falsePlot m/z instead of mass


plotms1ms2scancounts

argh

Usage:

--plotms1ms2scancounts [--mzxmldir=<filepath>] [--out=<filepath>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>null(no details provided)
mzxmldir<filepath>nulldirectory of mzXml Files
out<filepath>null(no details provided)


runcommandfile

The runcommandfile command allows you to run a command file, which contains one or more commands to be run in sequence, along with their respective argument values

Usage:

--runcommandfile <filepath>

Arguments:

ArgumentUsageDefaultDescription
(unnamed)<filepath>nullMacro file to run


saveimage

This command loads an mzXml file and writes out an image in which the X axis represents time, the Y axis represents M/Z, and the shade of each pixel represents intensity.

Usage:

--saveimage [--includetic=<true | false>] [--maxheight=<integer>] [--maxwidth=<integer>] [--out=<filepath>] [--outdir=<filepath>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullInput mzXml file(s)
includetic<true | false>falseInclude Total Ion Chromatogram?
maxheight<integer>2147483647Maximum height of output image
maxwidth<integer>2147483647Maximum width of output image
out<filepath>nullOutput image file
outdir<filepath>nullOutput image directory


savemzxmlwindow

This command saves out a partial mzXML file to a new file, using the specified start and end scan numbers and minimum and maximum MZ values. Any values not specified default to the start/end values from the original file

Usage:

--savemzxmlwindow [--excludems1=<true | false>] [--maxmz=<decimal>] [--maxscan=<integer>] [--minmz=<decimal>] [--minscan=<integer>] [--out=<filepath>] [--outdir=<filepath>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullInput mzXML file(s)
excludems1<true | false>falseExclude MS1 scans from output
maxmz<decimal>nullMaximum M/Z value
maxscan<integer>nullMaximum scan number
minmz<decimal>nullMinimum M/Z value
minscan<integer>nullMinimum scan number
out<filepath>nullOutput File
outdir<filepath>nullOutput Directory (for multiple inputs


spreadsheetmerge

This is for merging and comparing spreadsheets based on the value in some column ('mergecolumn').

Usage:

--spreadsheetmerge --mergecolumn=<value> [--compareout=<filepath>] [--file2column=<value>] [--keepallfile1values=<true | false>] [--multiplemergecolvaluessfirstfile=<true | false>] [--newcolname=<value>] [--out=<filepath>] [--outunique2file=<filepath>] [--plotcolumn=<value>] [--plotlog=<true | false>] [--presenceannotation=<value>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullinput spreadsheets
mergecolumn<value>nullcolumn to merge on
compareout<filepath>nulloutput file for comparing values of plotcolumn
file2column<value>nullcolumn to add from the second file. If not specified, all columns added
keepallfile1values<true | false>falseKeep all values from the first file, even if they don't occur in other files?
multiplemergecolvaluessfirstfile<true | false>falsecheck for multiple merge-column values in the first file, separated by ';'
newcolname<value>nullNew column name, for presence annotations
out<filepath>nulloutput file
outunique2file<filepath>nulloutput file for rows unique to the second spreadsheet
plotcolumn<value>nullcolumn to plot, one vs. the other
plotlog<true | false>falsePlot in log scale
presenceannotation<value>nullRather than adding columns from second file, add this string as the value for all matching mergecolumn rows, as a new column with name 'newcolname'


usermanual

Automatically create an HTML user manual for msInspect commandline functions, using the self-documentation features of the commandline modules themselves.

Usage:

--usermanual [--gui=<true | false>] [--out=<filepath>] <value>

Arguments:

ArgumentUsageDefaultDescription
(unnamed)<value>nullSingle command to document (leave blank for full manual)
gui<true | false>trueOpen in a GUI window? (otherwise HTML output is simply written to a file or to standard output
out<filepath>nullOutput file


viewspectrum

viewspectrum

Usage:

--viewspectrum --maxmz=<decimal> --maxscan=<integer> --minmz=<decimal> --minscan=<integer> [--height=<integer>] [--maxscansimageheight=<integer>] [--out=<filepath>] [--outscans=<filepath>] [--resolution=<integer>] [--scanline1=<integer>] [--scanline2=<integer>] [--scansfileimageheight=<integer>] [--showcharts=<true | false>] [--showscans=<true | false>] [--static=<true | false>] [--width=<integer>] <filepath>

Arguments:

ArgumentUsageDefaultDescription
(unnamed)<filepath>nullmzXML file
maxmz<decimal>nullmaximum m/z
maxscan<integer>nullmaximum scan number
minmz<decimal>nullminimum m/z
minscan<integer>nullminimum scan number
height<integer>1000Window height (also used for spectrum file)
maxscansimageheight<integer>4000Maximum overall height for the all-scans line plot image (overrides scansfileimageheight)
out<filepath>nullOutput image file for heatmap
outscans<filepath>nullOutput image file for single-scan line plots
resolution<integer>100resolution (number of breaks per Thompson
scanline1<integer>0Line for marking a particular scan
scanline2<integer>0Another line for marking a particular scan
scansfileimageheight<integer>100Height of EACH per-scan image, in the output file
showcharts<true | false>trueShow charts at all?
showscans<true | false>trueShow individual scan spectra?
static<true | false>falseOnly show static image? For remote invocation
width<integer>1000Window width

Quantitation

Tools related to labeled and unlabeled quantitation


icat

ICAT Quantitation

Usage:

--icat [--deconvolute=<true | false>] [--deltamass=<mass value>da|ppm] [--deltatime=<decimal>] [--heavytagweight=<decimal>] [--intensitytype=<total | max | recalculated>] [--labeledresidue=<value>] [--lighttagweight=<decimal>] [--masswindow=<decimal>] [--maxlabelcount=<integer>] [--msfile=<filepath>] [--out=<filepath>] [--outdir=<filepath>] [--scanwindow=<integer>] [--showcharts=<true | false>] [--sumintensities=<true | false>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullInput File(s)
deconvolute<true | false>falseDeconvolute
deltamass<mass value>da|ppm0.2daMass Tolerance
deltatime<decimal>10.0Time Tolerance
heavytagweight<decimal>-1.0Heavy tag weight
intensitytype<total | max | recalculated>nullIntensity type
labeledresidue<value>nullLabeled Residue
lighttagweight<decimal>-1.0Light tag weight
masswindow<decimal>0.4Mass Window
maxlabelcount<integer>3Maximum Label Count
msfile<filepath>nullmzXml File
out<filepath>nullOutput File
outdir<filepath>nullOutput Directory (for multiple files)
scanwindow<integer>6Scan Window
showcharts<true | false>falseShow Charts
sumintensities<true | false>trueIf true, deconvoluted feature intensities reflect the sum of all component feature intensities. If false, intensity of most-intense feature is kept.


peptideratiovariation

peptideratiovariation

Usage:

--peptideratiovariation --out=<filepath> [--minpprophet=<decimal>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullinput files
out<filepath>nulloutput file
minpprophet<decimal>0.8999999761581421min peptideprophet


proteinquantcharts

proteinquantcharts

Usage:

--proteinquantcharts --mzxmldir=<filepath> --outdir=<filepath> --pepxml=<filepath> --protxml=<filepath> [--appendoutput=<true | false>] [--minproteinprophet=<decimal>] [--out=<filepath>] [--protein=<value>] [--protgenefile=<filepath>]

Arguments:

ArgumentUsageDefaultDescription
mzxmldir<filepath>nullDirectory with mzXML files
outdir<filepath>nullOutput Directory
pepxml<filepath>nullPepXML file
protxml<filepath>nullProtXML file
appendoutput<true | false>trueAppend output to file, if already exists?
minproteinprophet<decimal>0.8999999761581421Minimum ProteinProphet score for proteins (if protein not specified)
out<filepath>nullOutput File
protein<value>nullProtein name
protgenefile<filepath>nullFile associating gene symbols with protein accession numbers


q3new

Run Q3 quantitation on a pepXml file. Labeled residue and mass difference must be specified.

Usage:

--q3new [--alternatemzxmldir=<value>] [--compat=<true | false>] [--d=<value>] [--debug=<true | false>] [--forceoutput=<true | false>] [--labeledresidue=<value>] [--m=<mass value>da|ppm] [--massdiff=<decimal>] [--maxfracdeltamass=<mass value>da|ppm] [--mimicxpress=<true | false>] [--minpeptideprophet=<decimal>] [--n=<value>] [--nosentinels=<true | false>] [--out=<filepath>] [--outdir=<filepath>] [--stripoldq3=<true | false>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullInput file(s)
alternatemzxmldir<value>nullAlternate mzXML directory
compat<true | false>nullMatch behavior of the original R code when the center scan has fewer than three matching isotopes (default false)
d<value>nullAlternate mzXML directory
debug<true | false>nullOutput extra debugging information in the pepXML
forceoutput<true | false>nullForce output (default false)
labeledresidue<value>nullLabeled residue
m<mass value>da|ppmnullMass tolerance
massdiff<decimal>nullMass difference between heavy and light forms of the labeled residue
maxfracdeltamass<mass value>da|ppmnullMaximum fractional delta mass
mimicxpress<true | false>nullMimic XPress? (default false)
minpeptideprophet<decimal>nullMinimum PeptideProphet score
n<value>nullLabel definition (e.g. -nC,3.0100645
nosentinels<true | false>nullNo sentinels (default false)
out<filepath>nullOutput file
outdir<filepath>nullOutput Directory (for handling multiple files)
stripoldq3<true | false>falseStrip existing analysis_results and Q3 analysis_summary elements from the file


quant

Quantitate

Usage:

--quant [--deconvolute=<true | false>] [--deltamass=<mass value>da|ppm] [--deltatime=<decimal>] [--heavytagweight=<decimal>] [--intensitytype=<total | max | recalculated>] [--labeledresidue=<value>] [--lighttagweight=<decimal>] [--masswindow=<decimal>] [--maxlabelcount=<integer>] [--msfile=<filepath>] [--out=<filepath>] [--outdir=<filepath>] [--scanwindow=<integer>] [--showcharts=<true | false>] [--sumintensities=<true | false>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullInput File(s)
deconvolute<true | false>falseDeconvolute
deltamass<mass value>da|ppm0.2daMass Tolerance
deltatime<decimal>10.0Time Tolerance
heavytagweight<decimal>-1.0Heavy tag weight
intensitytype<total | max | recalculated>nullIntensity type
labeledresidue<value>nullLabeled Residue
lighttagweight<decimal>-1.0Light tag weight
masswindow<decimal>0.4Mass Window
maxlabelcount<integer>3Maximum Label Count
msfile<filepath>nullmzXml File
out<filepath>nullOutput File
outdir<filepath>nullOutput Directory (for multiple files)
scanwindow<integer>6Scan Window
showcharts<true | false>falseShow Charts
sumintensities<true | false>trueIf true, deconvoluted feature intensities reflect the sum of all component feature intensities. If false, intensity of most-intense feature is kept.


quantcharts

Create charts showing the MS1 spectra near quantitative events for specified peptides or proteins. Includes an HTML index to all of the charts, broken down by protein, peptide, fraction, charge, etc.

Usage:

--quantcharts --outdir=<filepath> --pepxml=<filepath> [--3dheight=<integer>] [--3drotation=<integer>] [--3dshowaxes=<true | false>] [--3dtilt=<integer>] [--3dwidth=<integer>] [--fractions=<value>] [--infooncharts=<true | false>] [--maxscansimageheight=<integer>] [--minpprophet=<decimal>] [--mzpadding=<decimal>] [--mzxml=<filepath>] [--mzxmldir=<filepath>] [--numpeaksaboveheavy=<integer>] [--outhtml=<filepath>] [--outtsv=<filepath>] [--paddingscans=<integer>] [--peakdistance=<decimal>] [--peakmasstoleranceppm=<decimal>] [--peptides=<value>] [--proteins=<value>] [--resolution=<integer>] [--scan=<integer>] [--scanimageheight=<integer>] [--show3dplots=<true | false>] [--spectrumimageheight=<integer>] [--width=<integer>]

Basic Arguments:

ArgumentUsageDefaultDescription
outdir<filepath>nullOutput directory
pepxml<filepath>nullpepXML file
fractions<value>nullFraction containing desired quantitation event
minpprophet<decimal>0.0minimum PeptideProphet value
mzxml<filepath>nullmzXML file
mzxmldir<filepath>nullmzXML directory
outhtml<filepath>nullOutput HTML file
outtsv<filepath>nullOutput TSV file
peptides<value>nullcomma-separated list of peptides to examine
proteins<value>nullcomma-separated list of proteins to examine
scan<integer>0Scan number of desired quantitation event
show3dplots<true | false>trueShow 3D plot? (takes more time)

Advanced Arguments:

ArgumentUsageDefaultDescription
3dheight<integer>900Image height for 3D plot
3drotation<integer>80Rotation angle for 3D plot
3dshowaxes<true | false>trueInclude axes on 3D plot?
3dtilt<integer>20Tilt angle for 3D plot
3dwidth<integer>900Image width for 3D plot
infooncharts<true | false>falseWrite quantitation information directly on the charts?
maxscansimageheight<integer>4000Maximum overall height for the all-scans line plot image (overrides scansfileimageheight)
mzpadding<decimal>1.5amount of m/z space to display around quant
numpeaksaboveheavy<integer>4number of peaks above the heavy-ion monoisotope to display
paddingscans<integer>5number of scans before and after quant envelope to display
peakdistance<decimal>1.0Distance, in Daltons, between peaks. This is configurable in Q3, so it has to be configurable here. Used in generating the intensity sum chart
peakmasstoleranceppm<decimal>25.0Mass tolerance, in PPM, around each theoretical peak to consider part of the peptide being quantitated. Used in generating the intensity sum chart
resolution<integer>100resolution (number of breaks per Thompson
scanimageheight<integer>100Height of EACH per-scan image, in the output file
spectrumimageheight<integer>700Image height (used for spectrum, scans, and sum scan intensities charts)
width<integer>900Image width (used for spectrum, scans, and sum scan intensities charts)


qurate

Review quantitation charts

Usage:

--qurate <filepath>

Arguments:

ArgumentUsageDefaultDescription
(unnamed)<filepath>nullQuantitation summary file

Alignment

Tools for aligning multiple runs, including Peptide Arrays


align

Align feature sets

Usage:

--align --mode=<spline | quantile> [--deltamass=<mass value>da|ppm] [--mappingpolynomialdegree=<integer>] [--maxleverage=<decimal>] [--maxstudres=<decimal>] [--topn=<integer>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>null(no details provided)
mode<spline | quantile>null spline: spline quantile: quantile
deltamass<mass value>da|ppmnulldelta-mass for matching features for alignment
mappingpolynomialdegree<integer>5The degree of the polynomial to fit when mapping time to hydrophobicity nonlinearly
maxleverage<decimal>6.0Maximum NUMERATOR of the leverage of features used for regression
maxstudres<decimal>3.0Maximum studentized residual for regression
topn<integer>-1topN argument for spline-based mapping


analyzepeparray

Tools for analyzing peptide arrays, for comparing MS2 results in one set of runs to another and for summarizing overlap of MS1 features found in different runs.

Usage:

--analyzepeparray --mode=<getinfo | createfeaturefilesallmatched | countmultiplyobservedpeptides | comparepeptideintensities | createconsensusfeaturefile | compareallintensities | compareallintensitiesadd1 | comparepeptideintensitiesadd1 | comparenonpeptideintensities> [--allowhalfmatched=<true | false>] [--caserun=<value>] [--caserunlistfile=<filepath>] [--controlrun=<value>] [--controlrunlistfile=<filepath>] [--minconsensusfeatureruns=<integer>] [--minfeaturesupport=<integer>] [--minpeptidesupport=<integer>] [--minrunspergroup=<integer>] [--minsignificantratio=<decimal>] [--out=<filepath>] [--outdir=<filepath>] [--showcharts=<true | false>] <filepath>

Arguments:

ArgumentUsageDefaultDescription
(unnamed)<filepath>null(no details provided)
mode<getinfo | createfeaturefilesallmatched | countmultiplyobservedpeptides | comparepeptideintensities | createconsensusfeaturefile | compareallintensities | compareallintensitiesadd1 | comparepeptideintensitiesadd1 | comparenonpeptideintensities>null getinfo: Get basic peptide array information createfeaturefilesallmatched: Create feature files, one per run, containing only those features matched across all runs countmultiplyobservedpeptides: Count the distinct peptides observed in multiple runs comparepeptideintensities: Compare peptide intensities matched across runs createconsensusfeaturefile: Create a 'consensus' feature file, containing features (with details from the first run) that align across at least minconsensusfeatureruns runs compareallintensities: Compare intensity in the case runs vs. intensity in the control runs compareallintensitiesadd1: Compare intensity in the case runs vs. intensity in the control runs, adding 1, so that logs can be used comparepeptideintensitiesadd1: Compare intensity in the case runs vs. the control runs for features mapped to the same peptide comparenonpeptideintensities: Compare intensity in the case runs vs. the control runs for features mapped to the same peptide, adding 1, so that logs can be used
allowhalfmatched<true | false>falseWhen determining whether peptide matches are made, should it be considered a match when one run has an ID and another run has an intensity but no ID?
caserun<value>nullCase run
caserunlistfile<filepath>nullFile containing the names of runs in the case group, one per line
controlrun<value>nullCase run
controlrunlistfile<filepath>nullFile containing the names of runs in the control group, one per line
minconsensusfeatureruns<integer>2Minimum number of runs required for a feature to be included in the consensus feature set
minfeaturesupport<integer>1Minimum number of runs for which a non-peptide-conflicting feature was identified
minpeptidesupport<integer>1Minimum number of runs for which the same peptide was identified
minrunspergroup<integer>1Minimum number of runs in each group in which a feature must be located to be counted
minsignificantratio<decimal>3.0Minimum ratio of intensities considered interesting
out<filepath>nulloutput file
outdir<filepath>nulloutput directory
showcharts<true | false>falseshow charts?


peptidearray

The peptidearray command creates a peptide array from two or more feature files.

Usage:

--peptidearray --out=<filepath> [--accmz=<true | false>] [--align=<true | false>] [--alignbytags=<none | loose | strict>] [--alignmentmode=<spline | quantile>] [--alignminintensity=<decimal>] [--alignmztolerance=<decimal>] [--df=<integer>] [--featurepairselector=<mz | peptide | hybrid>] [--intensitytype=<sum | best>] [--massbuckets=<value>] [--masswindow=<decimal>] [--maxcharge=<integer>] [--maxkl=<decimal>] [--maxleverage=<decimal>] [--maxmass=<decimal>] [--maxmassdeviationppm=<integer>] [--maxmz=<decimal>] [--maxpeaks=<integer>] [--maxstudres=<decimal>] [--maxsumsquaresdist=<decimal>] [--maxtime=<decimal>] [--mincharge=<integer>] [--minintensity=<decimal>] [--minmass=<decimal>] [--minmz=<decimal>] [--minpeaks=<integer>] [--minpprophet=<decimal>] [--minscans=<integer>] [--mintime=<decimal>] [--mintotalintensity=<decimal>] [--normalize=<true | false>] [--optimize=<true | false>] [--optimizeonpeptideids=<true | false>] [--peptidematchscore=<integer>] [--peptidemismatchpenalty=<integer>] [--polynomialdegree=<integer>] [--scanbuckets=<value>] [--scanfirst=<integer>] [--scanlast=<integer>] [--scanwindow=<integer>] [--showcharts=<true | false>] [--tags=<filepath>] [--topn=<integer>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullA series of feature files to align
out<filepath>nulloutput file
accmz<true | false>nullAccurate m/z only?
align<true | false>trueshould alignment be performed?
alignbytags<none | loose | strict>noneRequest a pre-alignment within each group of tags. "None" indicates that no pre-alignment be done. "Loose" requests pre-alignment, preserving those features present in at least 3/4 of the runs in each group. "Strict" preserves those features present in all runs in each group. Unless "None", a tags file *must* be specified.
alignmentmode<spline | quantile>spline spline: Use the spline regression algorithm for alignment. This is the original algorithm implemented. It runs a bit faster than the quantile regression and behaves less oddly at the very extremes of the data. quantile: Use quantile regression algorithm for alignment. This algorithm performs better with very noisy data.
alignminintensity<decimal>100.0Minimum intensity used in picking pairs of features for alignment (if applicable)
alignmztolerance<decimal>0.10000000149011612M/Z tolerance used in picking pairs of features for alignment (if applicable)
df<integer>20Degrees of Freedom for alignment (spline mode)
featurepairselector<mz | peptide | hybrid>nullHow features should be paired when performing alignment. Default is MZ
intensitytype<sum | best>sumWhat type of intensity should we include in the array when there are conflicts? A sum of all matching features in the bucket, or the intensity of the best-looking feature?
massbuckets<value>nullcomma-separated list of decimal values for the maximum mass bucket size
masswindow<decimal>0.2number of Daltons to use as a window when aligning features
maxcharge<integer>nullMaximum charge
maxkl<decimal>nullMaximum K/L score
maxleverage<decimal>100.0Maximum NUMERATOR of the leverage of features used for alignment (denominator is N). Default value is effectively no filtering. Use values < 8 for tighter filtering
maxmass<decimal>nullMaximum mass
maxmassdeviationppm<integer>nullMaximum deviation from nearest theoretical mass cluster, in PPM
maxmz<decimal>nullMaximum M/Z value
maxpeaks<integer>nullMaximum number of peaks
maxstudres<decimal>100.0Maximum studentized residual for alignment. Default value is effectively no filtering. Use values < 3 for tighter filtering
maxsumsquaresdist<decimal>nullMaximum sum-squares distance score
maxtime<decimal>nullMaximum time
mincharge<integer>nullMinimum charge
minintensity<decimal>nullMinimum intensity
minmass<decimal>nullMinimum mass
minmz<decimal>nullMinimum M/Z value
minpeaks<integer>nullMinimum number of peaks
minpprophet<decimal>nullMinimum PeptideProphet score
minscans<integer>nullMinimum number of scans covered
mintime<decimal>nullMinimum time
mintotalintensity<decimal>nullMinimum total intensity
normalize<true | false>falseshould the intensities be normalized after alignment?
optimize<true | false>falseShould we optimize the size of the mass and scan buckets based on the number of 'perfect buckets'?
optimizeonpeptideids<true | false>falseIf optimizing, optimize based on the number of rows with agreeing peptide IDs, rather than the number of rows with one peptide (of any ID) from each row
peptidematchscore<integer>1If optimizing based on rows with agreeing peptides, give this score for each agreeing row
peptidemismatchpenalty<integer>1If optimizing based on rows with agreeing peptides, give this penalty for each mismatched row
polynomialdegree<integer>5The degree of the polynomial to fit (for quantile mode)
scanbuckets<value>nullcomma-separated list of integer values for the maximum scan bucket size
scanfirst<integer>nullMinimum scan number
scanlast<integer>nullMaximum scan number
scanwindow<integer>50number of scans to use as a window when aligning features
showcharts<true | false>falseOptionally plot the warping functions for each aligned run
tags<filepath>nulloptional file of tags for each run
topn<integer>0if > 0, sets the number of highest-intensity features from each run to use when constructing the non-linear mapping

MS/MS

Tools related to tandem mass spectrometry and the file formats used for tandem MS


calcfdr

Use reverse database hits to calculate the 'target' False Discovery Rate (#decoy/#target) for each peptide identification, based on some score (either PeptideProphet probability, or another search_score specified explicitly). Calculate q-values and use those instead of raw FDR. Filter the results using FDR cutoff 'maxfdr' and assign all results the same arbitrary PeptideProphet probability (argument 'pprophetvalue')

Usage:

--calcfdr [--bycharge=<true | false>] [--higherisbetter=<true | false>] [--maxfdr=<decimal>] [--out=<filepath>] [--outdir=<filepath>] [--outformat=<pepxml | msinspect | apml | input>] [--pprophetvalue=<decimal>] [--savechartsdir=<filepath>] [--scoretype=<pprophet | searchscore>] [--searchscorename=<value>] [--setpprophet1minusfdr=<true | false>] [--showcharts=<true | false>] [--targetdecoydbsizeratio=<decimal>] [--together=<true | false>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullInput feature file(s)
bycharge<true | false>trueCalculate FDR separately by charge state? Charge states with too few identifications will be dropped
higherisbetter<true | false>falseIs a higher value better, for this score (for 'searchscore' mode)?
maxfdr<decimal>0.05000000074505806Maximum FDR to keep in output file
out<filepath>nullOutput file (for single file processing)
outdir<filepath>nullOutput directory
outformat<pepxml | msinspect | apml | input>input pepxml: PepXML msinspect: msInspect .tsv apml: APML input: Same as input format (PepXML or msInspect)
pprophetvalue<decimal>0.949999988079071Set the PeptideProphet score of every passing feature to this value
savechartsdir<filepath>nullDirectory to save charts to
scoretype<pprophet | searchscore>searchscore pprophet: Use PeptideProphet probability searchscore: Use a search score (name must be provided)
searchscorename<value>expectName of the search score to use (for 'searchscore' mode)
setpprophet1minusfdr<true | false>falseSet PeptideProphet score to 1 - FDR?
showcharts<true | false>falsePlot an ROC curve?
targetdecoydbsizeratio<decimal>1.0Ratio of the number of peptides in the target search database to the number of peptides in the decoy search database.
together<true | false>trueCalcualte FDR on all fractions together? Otherwise, calculate FDR separately for eachrun


combinepepxmlfiles

combinepepxmlfiles

Usage:

--combinepepxmlfiles --out=<filepath> <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullinput files
out<filepath>nullOutput file


comparefastas

compare fastas

Usage:

--comparefastas --fasta1=<filepath> --fasta2=<filepath> --out=<filepath>

Arguments:

ArgumentUsageDefaultDescription
fasta1<filepath>nullFASTA file 1
fasta2<filepath>nullFASTA file 2
out<filepath>nulloutput file


correctprecursormz

Corrects the precursor m/z values in mzXML spectra, using the features found by msInspect (or any compatible feature-finder) to override the m/z values provided by the instrument. Optionally, also performs calibration of the precursor masses, and of the spectra themselves. Can be called using an existing feature file, or, if none is specified, will perform feature-finding. Can be called on one file at a time, or on multiple at once.

Usage:

--correctprecursormz --features=<filepath> [--calibrate=<true | false>] [--calibratespectra=<true | false>] [--featuresdir=<filepath>] [--fracmztolerance=<decimal>] [--initialfilterppm=<integer>] [--out=<filepath>] [--outdir=<filepath>] [--outfeatures=<filepath>] [--partitions=<integer>] [--peaksaboveprecursor=<integer>] [--peaksbelowprecursor=<integer>] [--showcharts=<true | false>] [--useinaccuratems1mz=<true | false>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullInput mzXML file(s)
features<filepath>nullFeature file to use in correction
calibrate<true | false>falseCalibrate precursor masses?
calibratespectra<true | false>falseCalibrate spectra, as well as precursor masses (only valid with calibrate option)?
featuresdir<filepath>nullDirectory of feature files to use in correction
fracmztolerance<decimal>100.0fractional M/Z tolerance, in PPM, for associating MS1 features with precursor scans
initialfilterppm<integer>0Initial ppm value used as a pre-calibration cutoff. Features deviating from theoretical clusters (BEFORE calibration) will be filtered out during calibration. However, those features WILL appear in the recalibrated featureset, with corrected masses.Default = no filter
out<filepath>nullOutput File
outdir<filepath>nullOutput Directory (for multiple inputs)
outfeatures<filepath>nullOutput recalibrated feature file
partitions<integer>1Number of partitions, by scan, to divide the run into, for calibration
peaksaboveprecursor<integer>1Number of peaks above the precursor m/z to check for MS1 features
peaksbelowprecursor<integer>3Number of peaks below the precursor m/z to check for MS1 features
showcharts<true | false>falseshow charts?
useinaccuratems1mz<true | false>falseUse an MS1 feature if m/z not "accurate"?


extractrunsfrompepxml

Extracts individual runs from a PepXML file containing multiple runs as fractions. Saves the results as individual PepXML files.

Usage:

--extractrunsfrompepxml --outdir=<filepath> [--accmz=<true | false>] [--maxcharge=<integer>] [--maxkl=<decimal>] [--maxmass=<decimal>] [--maxmassdeviationppm=<integer>] [--maxmz=<decimal>] [--maxpeaks=<integer>] [--maxsumsquaresdist=<decimal>] [--maxtime=<decimal>] [--mincharge=<integer>] [--minintensity=<decimal>] [--minmass=<decimal>] [--minmz=<decimal>] [--minpeaks=<integer>] [--minpprophet=<decimal>] [--minscans=<integer>] [--mintime=<decimal>] [--mintotalintensity=<decimal>] [--mzxmldir=<filepath>] [--outformat=<tsv | pepxml>] [--populatetimes=<true | false>] [--scanfirst=<integer>] [--scanlast=<integer>] [--sourcefilename=<value>] <filepath>

Arguments:

ArgumentUsageDefaultDescription
(unnamed)<filepath>nullInput pepXml file
outdir<filepath>nullOutput Directory
accmz<true | false>nullAccurate m/z only?
maxcharge<integer>nullMaximum charge
maxkl<decimal>nullMaximum K/L score
maxmass<decimal>nullMaximum mass
maxmassdeviationppm<integer>nullMaximum deviation from nearest theoretical mass cluster, in PPM
maxmz<decimal>nullMaximum M/Z value
maxpeaks<integer>nullMaximum number of peaks
maxsumsquaresdist<decimal>nullMaximum sum-squares distance score
maxtime<decimal>nullMaximum time
mincharge<integer>nullMinimum charge
minintensity<decimal>nullMinimum intensity
minmass<decimal>nullMinimum mass
minmz<decimal>nullMinimum M/Z value
minpeaks<integer>nullMinimum number of peaks
minpprophet<decimal>nullMinimum PeptideProphet score
minscans<integer>nullMinimum number of scans covered
mintime<decimal>nullMinimum time
mintotalintensity<decimal>nullMinimum total intensity
mzxmldir<filepath>nullDirectory to search for mzXML files (for populating times)
outformat<tsv | pepxml>pepxmlOutput format
populatetimes<true | false>falsePopulate times using mzXML file
scanfirst<integer>nullMinimum scan number
scanlast<integer>nullMaximum scan number
sourcefilename<value>nullSource File Name (without .xml)


filterpeptideregexp

Example: [^C]* will keep all peptides without a Cysteine residue

Usage:

--filterpeptideregexp --regexp=<value> [--out=<filepath>] [--outdir=<filepath>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>null(no details provided)
regexp<value>nullRegular expression that every peptide must match
out<filepath>null(no details provided)
outdir<filepath>null(no details provided)


filterpepxml

Filter pepxml files in useful ways

Usage:

--filterpepxml [--badprotprefix=<value>] [--goodprotprefix=<value>] [--out=<filepath>] [--outdir=<filepath>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>null(no details provided)
badprotprefix<value>nullExclude any peptides with any associated proteins with this prefix to their names
goodprotprefix<value>nullInclude any peptides with any associated proteins with this prefix to their names
out<filepath>null(no details provided)
outdir<filepath>null(no details provided)


filterreversedbhits

Usage:

--filterreversedbhits [--out=<filepath>] [--outdir=<filepath>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>null(no details provided)
out<filepath>null(no details provided)
outdir<filepath>null(no details provided)


findindistinguishableproteins

findindistinguishableproteins

Usage:

--findindistinguishableproteins --protfile=<filepath> [--minpprophet=<decimal>] <filepath>

Arguments:

ArgumentUsageDefaultDescription
(unnamed)<filepath>nullprotxml file
protfile<filepath>nullFile with list of proteins to look for
minpprophet<decimal>0.0Minimum ProteinProphet score.


flippepxmlratios

Flip peptide ratios and light/heavy areas

Usage:

--flippepxmlratios [--out=<filepath>] [--outdir=<filepath>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullpepXML file(s) to flip
out<filepath>nullOutput file
outdir<filepath>nullOutput directory


guessproteinsfromfasta

Populate (guess at) the protein for each identified peptide

Usage:

--guessproteinsfromfasta --fasta=<filepath> [--guessallproteins=<true | false>] [--out=<filepath>] [--outdir=<filepath>] [--outformat=<msinspect | pepxml>] [--refreshparser=<true | false>] [--striphighcharge=<true | false>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullFeature File to fix up
fasta<filepath>nullFasta file
guessallproteins<true | false>falseGuess all proteins? If false, just guess one protein
out<filepath>nulloutput file (if not specified, alters in place
outdir<filepath>nulloutput directory (if not specified, alters in place
outformat<msinspect | pepxml>pepxml msinspect: msinspect pepxml: pepxml
refreshparser<true | false>falseRun RefreshParser? RefreshParser executable must be on path.
striphighcharge<true | false>trueStrip high-charge features from output? (for ProteinProphet)


ms2scanviewer

ms2scanviewer

Usage:

--ms2scanviewer --mass=<decimal> [--masstoleranceppm=<decimal>] <filepath>

Arguments:

ArgumentUsageDefaultDescription
(unnamed)<filepath>nullmzXML file
mass<decimal>nullMass to search for scans around
masstoleranceppm<decimal>20.0PPM mass tolerance


peptidecompare

Perform a comparison of peptides identified between multiple runs (.tsv or .pep.xml files). You can analyze the overlap between peptide IDs, plot various characteristics of the identified peptides against each other (for 2 runs only), etc. The 'minpprophet' argument determines the minimum PeptideProphet value for all peptides to be compared.

Usage:

--peptidecompare --mode=<showoverlap | createfeaturefileforpeptideunion | plottimes | plotintensities | plottotalintensities | plotpprophet | plotfval | plotkscoreorxcorr | calcratios | plotratios | plotlightarea | idcluster | plotspectralcounts> [--fasta=<filepath>] [--featuresdir1=<filepath>] [--featuresdir2=<filepath>] [--includeunmatched=<true | false>] [--listallcommon=<true | false>] [--minpprophet=<decimal>] [--normalize=<true | false>] [--out=<filepath>] [--outformatpepxml=<true | false>] [--showcharts=<true | false>] [--summaryonly=<true | false>] [--withincharge=<true | false>] [--xaxislabel=<value>] [--yaxislabel=<value>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullinput files
mode<showoverlap | createfeaturefileforpeptideunion | plottimes | plotintensities | plottotalintensities | plotpprophet | plotfval | plotkscoreorxcorr | calcratios | plotratios | plotlightarea | idcluster | plotspectralcounts>null showoverlap: Show overlap between peptide identifications in two or more files createfeaturefileforpeptideunion: Create a feature file containing all the features in the first file whose peptides are found in all other files, as well plottimes: Plot time in one set vs. time in the other set, by peptide plotintensities: Plot intensity in one set vs. intensity in the other set, by peptide plottotalintensities: Plot total intensity in one set vs. total intensity in the other set, by peptide plotpprophet: Plot PeptideProphet probability vs. PeptideProphet probability in the other set, by peptide plotfval: Plot PeptideProphet fval vs. PeptideProphet fval in the other set, by peptide plotkscoreorxcorr: Plot kscore or xcorr score in one set (which is available) against kscore or xcorr score in the other set, by peptide calcratios: Calculate ratios (run 1 : run 2) for each peptide plotratios: Plot peptide ratios against each other plotlightarea: Plot light areas (for peptides with ratios) idcluster: Cluster runs by peptide identifications plotspectralcounts: Plot spectral counts
fasta<filepath>nullfasta file
featuresdir1<filepath>nullFirst directory full of feature files
featuresdir2<filepath>nullSecond directory full of feature files
includeunmatched<true | false>trueinclude unmatched peptides (for ratio mode)
listallcommon<true | false>trueList all peptides common to all runs?
minpprophet<decimal>0.0Minimum PeptideProphet score
normalize<true | false>truenormalize intensities (for ratio mode)
out<filepath>nullOutput file
outformatpepxml<true | false>falseoutput to pepxml
showcharts<true | false>falseshow charts
summaryonly<true | false>falseSummary-level info only? For directories
withincharge<true | false>falseOnly compare peptides within charge states
xaxislabel<value>nulllabel for X axis
yaxislabel<value>nulllabel for Y axis


picktargetedms2candidates

picktargetedms2candidates

Usage:

--picktargetedms2candidates --fasta=<filepath> --modifications=<residue><massdiff>[V][,...] --out=<filepath> --protlistfile=<filepath> [--excluderesidue=<value>] [--maxmz=<decimal>] [--maxpeptidesperprotein=<integer>] [--minmz=<decimal>] [--minpprophet=<decimal>] [--minproteinprophet=<decimal>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullprotxml file(s)
fasta<filepath>nullFASTA file
modifications<residue><massdiff>[V][,...]nullModifications
out<filepath>nulloutput file
protlistfile<filepath>nullProtein list file
excluderesidue<value>nullResidue to exclude
maxmz<decimal>1800.0Maximum m/z for targets
maxpeptidesperprotein<integer>3Maximum peptides per protein
minmz<decimal>400.0Minimum m/z for targets
minpprophet<decimal>0.8999999761581421Minimum PeptideProphet probability
minproteinprophet<decimal>0.8999999761581421Minimum ProteinProphet probability


plotdeltamasses

Plot deltaMass values against feature masses, and against time. Also histograms delta masses. This tool can be used to assess mass calibration as well as precursor mass accuracy

Usage:

--plotdeltamasses [--fractional=<true | false>] [--out=<filepath>] [--ppmline=<decimal>] [--showregressionline=<true | false>] [--useppm=<true | false>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>null(no details provided)
fractional<true | false>trueFractional masses?
out<filepath>nullOutput file for chart
ppmline<decimal>-1.0PPM cutoff to display on plot (default none)
showregressionline<true | false>falseShow a simple regression line through the data
useppm<true | false>falseUse PPM instead of Daltons


populatems2times

This tool reaches back to the mzXML file to populate the clock times of each MS2 feature, based on scan number

Usage:

--populatems2times --mzxmldir=<filepath> [--outdir=<filepath>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>null(no details provided)
mzxmldir<filepath>null(no details provided)
outdir<filepath>null(no details provided)


postprocesspepxml

Post-process PepXML. This provides tools for stripping out peptides and median-centering log ratios.

Usage:

--postprocesspepxml [--adjustquantzeroareas=<true | false>] [--badproteinprefix=<value>] [--bynumcysteines=<true | false>] [--filterbyproteinprefix=<true | false>] [--goodproteinprefix=<value>] [--label=<acrylamide | silac>] [--maxexpect=<decimal>] [--maxfracdeltamass=<mass value>da|ppm] [--maxquantexpect=<decimal>] [--mediancenter=<true | false>] [--minmediancenterratios=<integer>] [--minmedianpprophet=<decimal>] [--minpprophet=<decimal>] [--minquantpprophet=<decimal>] [--out=<filepath>] [--outdir=<filepath>] [--protprefixexcludequantonly=<true | false>] [--requirepepxmlextension=<true | false>] [--showcharts=<true | false>] [--strippeptidefile=<filepath>] [--stripquantmissingheavy=<true | false>] [--stripquantmissinglightorheavyacrossruns=<true | false>] [--stripquantmissinglightorheavywithinrun=<true | false>] [--stripquantzeroareas=<true | false>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullPepXML files to process
adjustquantzeroareas<true | false>falseAdjust zero values for light or heavy areas in quantitation (and ratios) to the 1 percentile of all the (nonzero) values
badproteinprefix<value>nullExclude any peptides with any associated proteins with this prefix to their names
bynumcysteines<true | false>falseMedian-center ratios separately by number of Cysteines?
filterbyproteinprefix<true | false>falseFilter peptides based on prefixes of the protein names that they're associated with?
goodproteinprefix<value>nullInclude any peptides with any associated proteins with this prefix to their names
label<acrylamide | silac>acrylamide acrylamide: Acrylamide (3.0106Da on C) silac: SILAC Lycine labeling (134.115092 on K)
maxexpect<decimal>3.4028234663852886E38Maximum expect score to keep
maxfracdeltamass<mass value>da|ppmnullMaximum fractional delta mass
maxquantexpect<decimal>3.4028234663852886E38Maximum expect score for quantitation
mediancenter<true | false>falseMedian-center ratios?
minmediancenterratios<integer>10Minimum number of ratios necessary in order to perform median-centering
minmedianpprophet<decimal>0.75Minimum PeptideProphet score to be counted in median calculation
minpprophet<decimal>0.0Minimum PeptideProphet score to keep
minquantpprophet<decimal>0.0Minimum PeptideProphet score for quantitation
out<filepath>nullOutput file
outdir<filepath>nullOutput directory
protprefixexcludequantonly<true | false>falseWhen excluding peptides based on protein prefix, exclude only quantitation? If false, excludes entire ID
requirepepxmlextension<true | false>falseWhen looking for files in a pepxmldir, require that they end with .pep.xml?
showcharts<true | false>falseShow charts?
strippeptidefile<filepath>nullFile containing a list of peptides to strip from results, one per line, all caps
stripquantmissingheavy<true | false>falseStrip quantitation events in which the heavy isotope was never identified, in any run
stripquantmissinglightorheavyacrossruns<true | false>falseStrip peptides that we haven't seen in both light and heavy states, across all runs. This ONLY makes sense for multiple metabolically-labeled experiments with a label flip
stripquantmissinglightorheavywithinrun<true | false>falseStrip peptides that we haven't seen in both light and heavy states, within a single run
stripquantzeroareas<true | false>falseStrip quantitation with zero values for light or heavy areas


proteinfractionsspreadsheet

asdfasdf

Usage:

--proteinfractionsspreadsheet --out=<filepath> --protxml=<filepath> [--grouplevel=<true | false>] [--minpprophet=<decimal>] [--minproteinprophet=<decimal>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullMS2 feature files
out<filepath>null(no details provided)
protxml<filepath>nullProtXML File
grouplevel<true | false>falseGroup-level? (default is accesion-number level)
minpprophet<decimal>0.0Minimum peptideprophet
minproteinprophet<decimal>0.0Minimum proteinprophet


protxmlcompare

Compare two protXML files -- compare probabilities for each protein, show protein overlap, etc

Usage:

--protxmlcompare [--listunique2proteins=<true | false>] [--minpprophet=<decimal>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullprotxml files to compare
listunique2proteins<true | false>falseList the proteins unique to the second file
minpprophet<decimal>0.0Minimum ProteinProphet score.


reversefasta

append a reversed version of a fasta file to a fasta file

Usage:

--reversefasta --out=<filepath> <filepath>

Arguments:

ArgumentUsageDefaultDescription
(unnamed)<filepath>null(no details provided)
out<filepath>null(no details provided)


searchscorecutoff

Use reverse database hits to determine the performance of a search score. Can be used on PeptideProphet probability or on any search_score. You specify a maximum false-to-true ratio, and this will give you the score cutoff that gives you that ratio, and optionally an output feature file containing just those features (with false-to-true ratio for each feature in the description)

Usage:

--searchscorecutoff --maxfar=<decimal> --mode=<pprophet | searchscore> [--higherisbetter=<true | false>] [--out=<filepath>] [--plotroc=<true | false>] [--searchscorename=<value>] [--setpprophet=<true | false>] <filepath>

Arguments:

ArgumentUsageDefaultDescription
(unnamed)<filepath>null(no details provided)
maxfar<decimal>nullmaximum false assignment rate
mode<pprophet | searchscore>null pprophet: Use PeptideProphet probability searchscore: Use a search score (name must be provided)
higherisbetter<true | false>trueIs a higher value better, for this score?
out<filepath>nullOutput file
plotroc<true | false>falsePlot an ROC curve?
searchscorename<value>nullName of the search score to use
setpprophet<true | false>falseSet the PeptideProphet score of every passing feature to 1 - the FAR at that score


spectralcount

Create a spreadsheet with spectral count information

Usage:

--spectralcount --mode=<peptide | gene | proteingroup> [--genelookupfile=<filepath>] [--out=<filepath>] [--protxml=<filepath>] [--showcharts=<true | false>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullMS2 Feature file(s)
mode<peptide | gene | proteingroup>null peptide: Peptide-level counts gene: Gene-level counts proteingroup: protein group-level counts
genelookupfile<filepath>nullGene lookup file for IPI numbers
out<filepath>nulloutput file
protxml<filepath>nullProtXML file
showcharts<true | false>falseshow charts?


summarizeprotxml

Summarize the contents of one or more protXML files

Usage:

--summarizeprotxml [--minpprophet=<decimal>] [--protgenefile=<filepath>] [--showcharts=<true | false>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullprotxml file(s)
minpprophet<decimal>0.0Min proteinprophet for MA plot
protgenefile<filepath>nullFile associating gene symbols with protein accession numbers
showcharts<true | false>falseshow charts?

AMT

Accurate Mass and Time analysis tools


amtdiagnostic

Get various kinds of information (mostly in chart form) about an AMT database. The 'saveallcharts' mode will generate all possible charts and save them to a directory

Usage:

--amtdiagnostic --mode=<compareobshcalch | comparecalchtime | plotthmaps | histhydrostddev | plotrunstddevs | saveallcharts | plotmassvsobshydro | basicinfo | histmasses | plotrunhvsmedian | peptidedetails | plotmassh | histidprobs> [--ms1features=<filepath>] [--out=<filepath>] [--outdir=<filepath>] [--peptide=<value>] [--showcharts=<true | false>] <filepath>

Arguments:

ArgumentUsageDefaultDescription
(unnamed)<filepath>nullAMT database file
mode<compareobshcalch | comparecalchtime | plotthmaps | histhydrostddev | plotrunstddevs | saveallcharts | plotmassvsobshydro | basicinfo | histmasses | plotrunhvsmedian | peptidedetails | plotmassh | histidprobs>null compareobshcalch: Compare Observed vs. Calculated H, per run comparecalchtime: Compare Calculated H vs. Time, per run plotthmaps: Plot the T->H mappings for each run histhydrostddev: Histogram of the hydrophobicity standard deviations across all observations for each peptide plotrunstddevs: Bar chart of the mean difference between predicted and observed H, per run saveallcharts: Save all charts to image files in a specified directory plotmassvsobshydro: Plot peptide mass vs. observed hydrophobicity, per run basicinfo: Return basic AMT database information histmasses: Histogram all peptide masses plotrunhvsmedian: Plot observed hydrophobicity against median peptide hydrophobicity, by run peptidedetails: Show details about a single peptide plotmassh: Plot mass and H for every entry in the DB histidprobs: Histogram the probabilities of all peptide entry IDs' correctness
ms1features<filepath>nullMS1 feature file to show along with database entries (plotmassandh mode only)
out<filepath>nulloutput filepath (for individual charts)
outdir<filepath>nulloutput directory (for saving all charts)
peptide<value>nullPeptide to get details about (for mode peptidedetails only)
showcharts<true | false>falseshow charts?


amtlabeledquant

Performs labeled quantitation by mining AMT results for isotopic pairs. Calculates ratios for each peptide within each charge state and then takes the geometric mean.

Usage:

--amtlabeledquant [--maxratio=<decimal>] [--minratio=<decimal>] [--minratiohighpprophet=<decimal>] [--minratiolowpprophet=<decimal>] [--othermods=<residue><massdiff>[V][,...]] [--out=<filepath>] [--outdir=<filepath>] [--percharge=<true | false>] [--residue=<value>] [--separation=<decimal>] [--showcharts=<true | false>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullAMT matching result file(s)
maxratio<decimal>15.0Maximum ratio to keep
minratio<decimal>0.06666667014360428Minimum ratio to keep
minratiohighpprophet<decimal>0.699999988079071Minimum AMT probability for consideration in a ratio: the higher of the two probabilities must be at least this high
minratiolowpprophet<decimal>0.05000000074505806Minimum AMT probability for consideration in a ratio: the lower of the two probabilities must be at least this high
othermods<residue><massdiff>[V][,...]C57.021,M16.0V,C14.01557a list of other modifications applied to sample
out<filepath>null(no details provided)
outdir<filepath>null(no details provided)
percharge<true | false>trueCalculate ratios per charge (vs. all charges together)?
residue<value>CLabeled residue (leave blank for n-terminal)
separation<decimal>3.0101light-heavy separation
showcharts<true | false>falseshow charts?


combineamtms2

Combine MS/MS results (pepxml or feature files) with AMT results (pepxml or feature files)

Usage:

--combineamtms2 --ms2dir=<filepath> [--amtdir=<filepath>] [--fasta=<filepath>] [--guessproteins=<true | false>] [--out=<filepath>] [--outdir=<filepath>] [--outformat=<pepxml | feature>] [--refreshparser=<true | false>] [--restrictcharge=<true | false>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullpepXml files from MS2 search (these can be specified individually or using the 'ms2dir' argument
ms2dir<filepath>nullDirectory of pepXML files from MS2 search
amtdir<filepath>nullDirectory of AMT matching results
fasta<filepath>nullFasta file
guessproteins<true | false>falseGuess initial proteins for peptides? (Requires fasta)
out<filepath>null(no details provided)
outdir<filepath>null(no details provided)
outformat<pepxml | feature>pepxmlOutput format
refreshparser<true | false>falseRun RefreshParser to assign all possible proteins to peptides? (RefreshParser must be on path, and fasta must be specified, and guessproteins must be specified)
restrictcharge<true | false>nullCap feature charge in output files at 5? (the maximum allowed by ProteinProphet)


createamt

Create an AMT database to store peptide observations from several, or many, LC-MS/MS runs. Many of the arguments for this command have to do with filtering the peptides used in the database.

Usage:

--createamt --mode=<directories | ms2featurefile | amtxmls | randompeptides> [--accmz=<true | false>] [--align=<true | false>] [--deltamassppm=<decimal>] [--deltatime=<decimal>] [--fasta=<filepath>] [--maxcharge=<integer>] [--maxkl=<decimal>] [--maxmass=<decimal>] [--maxmassdeviationppm=<integer>] [--maxmz=<decimal>] [--maxpeaks=<integer>] [--maxsrforinclusion=<decimal>] [--maxsrforregression=<decimal>] [--maxsumsquaresdist=<decimal>] [--maxtime=<decimal>] [--mincharge=<integer>] [--minintensity=<decimal>] [--minmass=<decimal>] [--minmz=<decimal>] [--minpeaks=<integer>] [--minpprophet=<decimal>] [--minscans=<integer>] [--mintime=<decimal>] [--mintotalintensity=<decimal>] [--ms1dir=<filepath>] [--ms1features=<filepath>] [--ms2dir=<filepath>] [--ms2features=<filepath>] [--mzxml=<filepath>] [--mzxmldir=<filepath>] [--numpeptides=<integer>] [--out=<filepath>] [--scanfirst=<integer>] [--scanlast=<integer>] [--scanortimemode=<scan | time>] <filepath> <filepath> ...

Basic Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullInput file (for 'ms2features' mode)
mode<directories | ms2featurefile | amtxmls | randompeptides>null directories: supply directories for MS2 and mzXML files ms2featurefile: create an AMT database from a single MS2 and mzXML file amtxmls: combine multiple existing AMT databases randompeptides: create a database of random peptides from a FASTA file
accmz<true | false>nullAccurate m/z only?
fasta<filepath>nullFASTA file to pull random peptides from ('randompeptides' mode only
maxcharge<integer>nullMaximum charge
maxkl<decimal>nullMaximum K/L score
maxmass<decimal>nullMaximum mass
maxmassdeviationppm<integer>nullMaximum deviation from nearest theoretical mass cluster, in PPM
maxmz<decimal>nullMaximum M/Z value
maxpeaks<integer>nullMaximum number of peaks
maxsumsquaresdist<decimal>nullMaximum sum-squares distance score
maxtime<decimal>nullMaximum time
mincharge<integer>nullMinimum charge
minintensity<decimal>nullMinimum intensity
minmass<decimal>nullMinimum mass
minmz<decimal>nullMinimum M/Z value
minpeaks<integer>nullMinimum number of peaks
minpprophet<decimal>nullMinimum PeptideProphet score
minscans<integer>nullMinimum number of scans covered
mintime<decimal>nullMinimum time
mintotalintensity<decimal>nullMinimum total intensity
ms1dir<filepath>nullDirectory of MS1 feature files (for 'directories' mode)
ms1features<filepath>nullInput MS1 feature file (for 'ms1featurefile' mode)
ms2dir<filepath>nullDirectory of MS2 feature files (for 'directories' mode)
ms2features<filepath>nullInput MS2 feature file (for 'ms2featurefile' mode)
mzxml<filepath>nullInput mzXml file (for 'ms2featurefile' mode), only necessary if retention times are not populated in the MS2 feature file
mzxmldir<filepath>nullDirectory of mzXML files (for 'directories' mode), only necessary if retention times are not populated in the MS2 feature file
out<filepath>nulloutput file
scanfirst<integer>nullMinimum scan number
scanlast<integer>nullMaximum scan number

Advanced Arguments:

ArgumentUsageDefaultDescription
align<true | false>falseuse nonlinear alignment when mapping time to hydrophobicity. This is not necessarily recommended, as the manageamt command has a mode ('alignallruns') for nonlinearly aligning all runs to a single scale that is much more effective.
deltamassppm<decimal>10.0Mass tolerance for MS1 feature match with MS2 in order to retrieve MS1 feature times
deltatime<decimal>25.0Time tolerance (in seconds) for MS1 feature match with MS2 in order to retrieve MS1 feature times
maxsrforinclusion<decimal>2.0maximum studentized residual for inclusion in database. Any observation with a higher studentized residual, based on the RT->NRT regression, will be excluded
maxsrforregression<decimal>2.0maximum studentized residual for use in regression calculation for transforming RT to NRT
numpeptides<integer>50000Number of random peptides to use in database creation ('randompeptides' mode only)
scanortimemode<scan | time>nullUse scans or times from features (default 'time')


createamtfeatureset

This tool takes an AMT database as input and produces a feature set with one feature per peptide entry. Intensity is set to an arbitrary value, and scan number is set to a value that relates linearly to median observed hydrophobicity

Usage:

--createamtfeatureset [--featuremassadjustment=<decimal>] [--modifications=<residue><massdiff>[V][,...]] [--out=<filepath>] <filepath>

Arguments:

ArgumentUsageDefaultDescription
(unnamed)<filepath>nullAMT database for matching
featuremassadjustment<decimal>0.0Adjust the masses of all AMT database features by this amount (in Daltons; for false positive testing)
modifications<residue><massdiff>[V][,...]nulla list of modifications to match on
out<filepath>nulloutput filepath


manageamt

Refine an AMT database by removing outlier observations or peptides, or nonlinearly aligning all runs to each other

Usage:

--manageamt --mode=<removeoutlierobservations | removepredictedhoutliers | removefewobservations | removerunswithoutmassmatches | alignallruns | adjustacrylamide | removepeptideswithresidue | removefastapeptides | filterobservationsbypprophet> [--alignmentdegree=<integer>] [--fasta=<filepath>] [--fromacryltonot=<true | false>] [--maxentries=<integer>] [--maxruns=<integer>] [--minmassmatchpercent=<integer>] [--minobservations=<integer>] [--minpprophet=<decimal>] [--ms1features=<filepath>] [--out=<filepath>] [--residue=<value>] [--showcharts=<true | false>] <filepath>

Basic Arguments:

ArgumentUsageDefaultDescription
(unnamed)<filepath>nullAMT database file
mode<removeoutlierobservations | removepredictedhoutliers | removefewobservations | removerunswithoutmassmatches | alignallruns | adjustacrylamide | removepeptideswithresidue | removefastapeptides | filterobservationsbypprophet>null removeoutlierobservations: Remove all individual observations that are at least 3 standard deviations from the median for that peptide, for peptides with at least three observations removepredictedhoutliers: Remove all peptides with only one observation, for which that observation is at least 2 standard deviations away from the prediction removefewobservations: Remove all peptides with fewer than minobservations observations removerunswithoutmassmatches: Make mass matches between each run's entries and an MS1 feature file. Remove all runs that don't mass-match at least minmassmatchpercent percent of peptides alignallruns: Nonlinearly align all runs in the database to a single run, starting with the run with the most peptide overlap with other runs in the database. This is an extremely important step. adjustacrylamide: Adjust all Cysteine-bearing observations to take the H contribution of acrylamide into account. Direction of adjustment depends on the 'fromacryltonot' parameter removepeptideswithresidue: Remove all peptides containing a given residue removefastapeptides: Remove all peptides that occur in a specified FASTA database filterobservationsbypprophet: Remove all observations below 'minpprophet' PeptideProphet probability
minobservations<integer>2Minimum number of observations for features kept in the database
minpprophet<decimal>nullMinimum PeptideProphet score (for 'filterobservationsbypprophet' mode)
out<filepath>null(no details provided)
residue<value>nullResidue (for 'removepeptideswithresidue' mode)
showcharts<true | false>falseShow charts?

Advanced Arguments:

ArgumentUsageDefaultDescription
alignmentdegree<integer>5Degree of polynomial to use in alignment (for 'alignallruns' mode)
fasta<filepath>nullFASTA database (removefastapeptides mode only)
fromacryltonot<true | false>nullFor mode adjustacrylamide. If true, adjusts all observations to _remove_ the effect of acrylamide. If false, adjusts observations to _add_ the effect.
maxentries<integer>2147483647Maximum DB entries (removerunswithoutmassmatches mode only)
maxruns<integer>2147483647Maximum DB runs (removerunswithoutmassmatches mode only)
minmassmatchpercent<integer>20Minimum percent of peptides mass-matched to MS1, per run (removerunswithoutmassmatches mode only)
ms1features<filepath>nullMS1 features (removerunswithoutmassmatches mode only)


matchamt

This tool matches MS1 features to an AMT database using mass and Normalized Retention Time. It assigns peptide IDs to the features matched, with confidence values from 0 to 1. If embedded MS2 features are available for the MS1 features, they can be used to establish the Time->Hydrophobicity mapping -- either via the MS2 times themselves or via the times of MS1 features that match to them. Otherwise, mapping is done using a two-step process that starts with strict mass-only matching and then uses quantile regression to find the best mapping.

Usage:

--matchamt --mode=<singlems1 | ms1dir> [--amtdbstructure=<value>] [--calcfdr=<true | false>] [--calibratematches=<true | false>] [--deltamassms1ms2ppm=<decimal>] [--deltatimems1ms2=<decimal>] [--dummymatch=<true | false>] [--embeddedms2=<filepath>] [--loosedeltaelution=<decimal>] [--loosedeltamass=<mass value>da|ppm] [--mappingpolynomialdegree=<integer>] [--massmatchdeltamass=<mass value>da|ppm] [--maxemiterations=<integer>] [--maxfractionstokeep=<integer>] [--maxregressionleverage=<decimal>] [--maxregressionstudres=<decimal>] [--maxsecondbestprob=<decimal>] [--minemiterations=<integer>] [--minfractionstokeep=<integer>] [--minmatchprob=<decimal>] [--minpprophet=<decimal>] [--minsecondbestprobdiff=<decimal>] [--modifications=<residue><massdiff>[V][,...]] [--ms1=<filepath>] [--ms1dir=<filepath>] [--ms2dir=<filepath>] [--mzxml=<filepath>] [--mzxmldir=<filepath>] [--out=<filepath>] [--outdir=<filepath>] [--removefractions=<true | false>] [--savechartsdir=<filepath>] [--showcharts=<true | false>] [--usems1foralignment=<true | false>] <filepath>

Basic Arguments:

ArgumentUsageDefaultDescription
(unnamed)<filepath>nullAMT database for matching
mode<singlems1 | ms1dir>null singlems1: Match against a single MS1 feature file ms1dir: Match against a directory of MS1 files, one by one
calibratematches<true | false>trueCalibrate MS1 feature masses using AMT matches? This is a good idea if you suspect there might be a miscalibration in the MS1 data. Even a small miscalibration can have a significant effect on matching by breaking the assumption that mass match error is distributed normally.
embeddedms2<filepath>nullEmbedded MS2 feature file from the same run that the MS1 features from matching are from. This will be used to help develop the mapping between Retention Time and Retention Time and Normalized Retention Time (the scale of the AMT database) for this run. (for 'singlems1' mode)
loosedeltaelution<decimal>0.15000000596046448A loose deltaElution value. The EM probability model will be fit using all AMT matches in the loose match. The appropriate value for this parameter may depend somewhat on data, so you should adjust it accordingly if you find true matches being excluded or all of the true matches clustering near the center of the RT distribution.
loosedeltamass<mass value>da|ppm20.0ppmA loose mass tolerance for the initial AMT match. The EM probability model will be fit using all AMT matches in the loose match. The appropriate value for this parameter is largely data-independent.
massmatchdeltamass<mass value>da|ppm5.0ppmA mass tolerance value to be used when developing the RT->NRT map based on mass-only matching. This value is not used if the 'embeddedms2' or 'ms2dir' argument is specified.
minmatchprob<decimal>0.10000000149011612Minimum AMT match probability to keep in output
minpprophet<decimal>0.9Minimum PeptideProphet score to use from the embedded MS2 feature file(s) in building the RT->NRT map
modifications<residue><massdiff>[V][,...]C57.021,M16.0VA list of modifications to use in matching. This list should contain all of the expected modifications in your MS1 data. During matching, AMT feature masses will be adjusted to account for any static mods specified here, and multiple features will be created to account for any variable mods. The default value is appropriate for non-isotopically-labeled MS1 data with iodoacetylated Cysteine and possibly oxidized Methionine.
ms1<filepath>nullInput MS1 feature file for matching (for 'singlems1' mode)
ms1dir<filepath>nullDirectory full of ms1 feature files for matching (for 'ms1dir' mode)
ms2dir<filepath>nullEmbedded MS2 feature file (e.g., pepxml) directory. For 'ms1dir' mode. For each MS1 file, the corresponding MS2 feature file will be located in this directory by filename and used to aid in the mapping between Retention Time and Normalized Retention Time for the run.
mzxml<filepath>nullmzXML file used to populate MS2 scan times, for use in developing the RT->NRT map. This argument is not necessary if the MS2 feature file already contains retention times (see the 'populatems2times' command). (for 'singlems1' mode)
mzxmldir<filepath>nullDirectory containing mzXML files from the same runs as the MS1 feature files. For each embedded MS2 feature file, the corresponding mzXML file will be located by filename and used to populate MS2 scan times, for use in developing the RT->NRT map. This argument is not necessary if the MS2 feature files already contain retention times (see the 'populatems2times' command). (for 'ms1dir' mode)
out<filepath>nullOutput filepath for matching results (for 'singlems1' mode)
outdir<filepath>nullOutput directory for all matching result files (for 'ms1dir' mode)
savechartsdir<filepath>nullDirectory to save charts to. This can be used with or without 'showcharts'
showcharts<true | false>falseShow useful charts created when matching? Not recommended when matching large numbers of files
usems1foralignment<true | false>trueUse MS1 times, rather than MS2 times, for alignment? This is done by matching MS1 and MS2 in a tight window

Advanced Arguments:

ArgumentUsageDefaultDescription
amtdbstructure<value>nullFor multi-fraction AMT databases from one or more experiments. Defines the arrangement of runs within the AMT database. This is only used to produce fancy heatmap charts of matches. Of the format '#rows,#cols,row|col,#experiments', e.g., '12,11,col,2' for a database with two experiments, each with 12 rows and 11 columns, whose runs are in order by column within the database
calcfdr<true | false>falseCalculate FDR for all results. We do this by making half of the database into decoy features, then repeating with the other half. This is for purposes of evaluating the EM model _only_! The probabilities calculated this way are not as accurate as the probabilities calculated without the decoy hits, because the decoy hits add to the background complexity of the null distribution.
deltamassms1ms2ppm<decimal>10.0Mass tolerance for MS1 feature match with MS2 in order to retrieve MS1 feature times
deltatimems1ms2<decimal>25.0Time tolerance (in seconds) for MS1 feature match with MS2 in order to retrieve MS1 feature times
dummymatch<true | false>falseDo a dummy match against a mass-shifted database, rather than a real match. This is only used for visualizing the false match density.
mappingpolynomialdegree<integer>5The degree of the polynomial to fit when mapping time to hydrophobicity nonlinearly. If you notice the mapping overfitting, you may reduce this value. If you think the mapping is not capturing all of the nonlinear quirks of the data, try increasing it.
maxemiterations<integer>200Maximum number of iterations for the EM algorithm deciding probability values
maxfractionstokeep<integer>0Maximum number of fractions to keep (for "removefractions"). Default is actually the number of runs in the database
maxregressionleverage<decimal>12.0Maximum leverage /numerator/ (denominator is N) for features included in the modal regression to map RT to Hydrophobicity. If you have spurious features at the beginning or end of the gradient, you may want to reduce this value.
maxregressionstudres<decimal>3.0Maximum studentized residual for features included in the modal regression to map RT to Hydrophobicity. You may want to decrease this value if many spurious matches are throwing off the regression, or increase it if legitimate features are being excluded.
maxsecondbestprob<decimal>0.5Maximum probability of the second-best AMT match, in order to keep best match
minemiterations<integer>30Minimum number of iterations for the EM algorithm deciding probability values
minfractionstokeep<integer>1Minimum number of fractions to keep (for "removefractions")
minsecondbestprobdiff<decimal>0.10000000149011612Minimum difference between best and secodn-best probability, in order to keep best match
removefractions<true | false>falseRemove fractions from the database that are unlike the MS1 matching fraction. This is only recommended for very dense, extensively fractionated databases built from hundreds of runs.


proteinrollup

Provides a naive mechanism for generating lists of possible proteins given a list of peptides and a Fasta file.

Usage:

--proteinrollup --mode=<digestprotxml | tabfile | createpepxmlfromtabfile | collapsepeptides | rollupgenes | rollupgenesfrompeptides> [--amtxml=<filepath>] [--expanded=<true | false>] [--fasta=<filepath>] [--genelookupfile=<filepath>] [--indir=<filepath>] [--minpeptides=<integer>] [--minprotxmlprobability=<decimal>] [--minuniquepeptides=<integer>] [--out=<filepath>] [--outdir=<filepath>] [--peptidelistfile=<filepath>] [--pepxml=<filepath>] [--protxml=<file>,<file>,...] [--showcharts=<true | false>] <filepath> <filepath> ...

Arguments:

ArgumentUsageDefaultDescription
(unnamed ...)<filepath>nullInput feature file(s)
mode<digestprotxml | tabfile | createpepxmlfromtabfile | collapsepeptides | rollupgenes | rollupgenesfrompeptides>null digestprotxml: Digest the output of ProteinProphet tabfile: Take as input a single tab-delimited ratio file in a special format createpepxmlfromtabfile: Create a pepXML file, using an input tab-delimited ratio file collapsepeptides: collapse per-peptide row entries into one per protein rollupgenes: Roll up proteins to gene level rollupgenesfrompeptides: Rollup peptides to proteins and then to gene level in one step
amtxml<filepath>nullAMT database file (for spectral count info)
expanded<true | false>falsePeptide expanded format (for gene rollup)
fasta<filepath>nullInput protein database
genelookupfile<filepath>nullGene lookup file for IPI numbers
indir<filepath>nullDirectory of input files
minpeptides<integer>1Minimum peptides for a protein to be collapsed
minprotxmlprobability<decimal>0.0Minimum probability assigned by protXml required for the protein to be considered to be identified
minuniquepeptides<integer>1Minimum number of unique peptides for a protein to be considered to be identified in a protXml file
out<filepath>nulloutput filepath
outdir<filepath>nulloutput directory
peptidelistfile<filepath>nullInput file containing one peptide sequence per line
pepxml<filepath>nullpepXml file for use in digesting protXml file
protxml<file>,<file>,...nullProtXML file(s)
showcharts<true | false>falseShow charts

MRM

The MRMer tools for Multiple Reaction Monitoring


mrm

MRMer is a visual editor and analysis tool for MRM assays and assay development. It is written in Java and must be used with Java version 1.6 or higher.

When you run MRMer from the command line, or if you are creating your own batch or script file, there are a number of options you can place on the java command. Typically the command will look something like:

 java -Xmx500m -jar viewerApp_v0.98.jar --mrm

followed by one or more of the options below, followed by the mzXML file you wish to analyze.

Usage:

--mrm [--auc_cutoff=<decimal>] [--peak_height_cutoff=<decimal>] [--peakstrategy=<BasicElutionCurveStrategy | BasicLowIntensityElutionCurveStrategy | ThermoElutionCurveStrategy>] [--precursor_tolerance=<decimal>] [--product_tolerance=<decimal>] [--selected_ion_monitoring=<true | false>] [--sic_tolerance=<decimal>] [--synclh=<true | false>] [--trace_all_fragments=<true | false>] <filepath>

Arguments:

ArgumentUsageDefaultDescription
(unnamed)<filepath>nullinput mzXML file containing SRM/MRM scans
auc_cutoff<decimal>0.0Use "AUC_CUTOFF=nnnnn" to define a minimum peak area to accept
peak_height_cutoff<decimal>0.0Use "PEAK_HEIGHT_CUTOFF=nnnnn" to define minimum peak height (within best curve) to accept
peakstrategy<BasicElutionCurveStrategy | BasicLowIntensityElutionCurveStrategy | ThermoElutionCurveStrategy>BasicElutionCurveStrategyUse peakstrategy to set the elution curve discovery and AUC determination algorithms
precursor_tolerance<decimal>0.009999999776482582Use "PRECURSOR_TOLERANCE=nnnn" to set the tolerance for discriminating precursor mass sets
product_tolerance<decimal>0.10000000149011612Use "PRODUCT_TOLERANCED=nnnn" to set the tolerance for discriminating between the masses of different product ions
selected_ion_monitoring<true | false>falseSet "SELECTED_ION_MONITORING" to TRUE if MS1 SIM scans are present and you want to use them exclusively for precursor chromatagrams
sic_tolerance<decimal>1.0Use "SIC_TOLERANCE=nnnn" to set the tolerance around the precursor ion for MS1 single ion chromatograms
synclh<true | false>trueSet "SYNCHLH" to TRUE to synchronize heavy and light elution regions (applicable in AQUA/SILAC analyses; transition.tsv file must be present)
trace_all_fragments<true | false>trueSet "TRACE_ALL_FRAGMENTS" to TRUE to draw pale elution curves over all product ions, instead of gray spikes

Quality Assurance

Quality Assurance tools


qaexperiment

Perform QA analysis on a single experiment

Usage:

--qaexperiment --allpepxml=<filepath> --allprotxml=<filepath> --protgenefile=<filepath> --qadir=<filepath> [--force=<true | false>] [--labelmassdiff=<decimal>] [--minpeptideprophet=<decimal>] [--minproteinprophet=<decimal>] [--mzxmldir=<filepath>] [--noms1=<true | false>]

Arguments:

ArgumentUsageDefaultDescription
allpepxml<filepath>nullall.pep.xml filepath
allprotxml<filepath>nullall.prot.xml filepath
protgenefile<filepath>nullFile associating gene symbols with protein accession numbers
qadir<filepath>nullQA Output Root Directory
force<true | false>falseForce re-creation of output files if they exist?
labelmassdiff<decimal>3.0Isotopic label mass difference
minpeptideprophet<decimal>0.75Minimum PeptideProphet probability
minproteinprophet<decimal>0.8999999761581421Minimum ProteinProphet probability
mzxmldir<filepath>nullmzXML Directory
noms1<true | false>falseNo MS1 analysis -- only pepXML and protXML


qaprotxml

Perform QA analysis on a single protXML file

Usage:

--qaprotxml --out=<filepath> --protgenefile=<filepath> [--minpprophet=<decimal>] <filepath>

Arguments:

ArgumentUsageDefaultDescription
(unnamed)<filepath>nullall.prot.xml filepath
out<filepath>nullOutput File
protgenefile<filepath>nullFile associating gene symbols with protein accession numbers
minpprophet<decimal>0.0Minimum ProteinProphet score to keep in output