-
This is the documentation for manually generating predicted speclib from FASTA + DIA then running analysis with improved speclib (i.e. match-between-runs):
Please let me know if this is correct. Step 1:
Step 2:
Using these two steps as a pipeline, how do I set speclib input for Step 2 if it hasn't been generated yet? Do I just create an empty file with the same name as output speclib and assume it will be overwritten? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Hi Sooheon, Step 0: generate a predicted spectral library (no raw files specified during this). This also applies to a normal MBR search, should start with a predicted (or empirical) library.
Yes.
The input lib is in .tsv format (1.9) or .parquet (1.9.1), you can just type the right file name in 'Spectral library' field, even if the file does not exist yet. Best, |
Beta Was this translation helpful? Give feedback.
Hi Sooheon,
Step 0: generate a predicted spectral library (no raw files specified during this). This also applies to a normal MBR search, should start with a predicted (or empirical) library.
Step 1: In this case, 'FASTA digest' and 'Deep learning' should be unchecked, as the library already contains predicted spectra, RTs and IMs. FASTA still needs to be provided, but purely for protein annotation. Modifications should be selected if you want them scored, please see the PTMs section in the docs.
Step 3: 'FASTA digest' and 'Deep learning' should be unchecked. Precursor generation settings: only modifications specified matter, everything else has no effect.