Building Peptide Atlas
From SPCTools
| Revision as of 18:20, 20 October 2008 Tfarrah (Talk | contribs) ← Previous diff |
Revision as of 19:26, 20 October 2008 Tfarrah (Talk | contribs) Next diff → |
||
| Line 3: | Line 3: | ||
| A project is a set of related experiments. For example, a project may study proteins found in normal and diseased liver, and may include 4 experiments: tissue from two normal patients and from two diseased patients. The pepXML files should be created by searching the spectra with a database search engine such as SEQUEST, X!Tandem, or SpectraST, then validating the hits using PeptideProphet. | A project is a set of related experiments. For example, a project may study proteins found in normal and diseased liver, and may include 4 experiments: tissue from two normal patients and from two diseased patients. The pepXML files should be created by searching the spectra with a database search engine such as SEQUEST, X!Tandem, or SpectraST, then validating the hits using PeptideProphet. | ||
| - | A project may also represent the iProphet combined results of several projects by several researchers, searched by several different search engines. | + | A project may at some point also represent the iProphet combined results of several projects by several researchers, searched by several different search engines. |
| ===Register projects and experiments using SBEAMS interface.=== | ===Register projects and experiments using SBEAMS interface.=== | ||
| *Go to db.systemsbiology.net. | *Go to db.systemsbiology.net. | ||
| Line 10: | Line 10: | ||
| *Fill out fields. Owner of project should be the experimenter who created the data, or the computational biologist who combined the data using iProphet. Project tag should match name of subdirectory in /sbeams/archive/<project_owner> that contains the data. | *Fill out fields. Owner of project should be the experimenter who created the data, or the computational biologist who combined the data using iProphet. Project tag should match name of subdirectory in /sbeams/archive/<project_owner> that contains the data. | ||
| ===Obtain search batch IDs for each experiment and create an experiments list.=== | ===Obtain search batch IDs for each experiment and create an experiments list.=== | ||
| + | |||
| ===Run ProteinProphet on all pepXML files combined to create a single protXML file=== | ===Run ProteinProphet on all pepXML files combined to create a single protXML file=== | ||
| ===Run PeptideAtlas build "pipeline".=== | ===Run PeptideAtlas build "pipeline".=== | ||
Revision as of 19:26, 20 October 2008
Here is how I built a human urine PeptideAtlas in October 2008. The details of how to do each step are found in regis.systemsbiology.net:~tfarrah/PeptideAtlasBuild/HumanUrine_2008-09.notes.
Start with one or more pepXML files for each experiment in each project.
A project is a set of related experiments. For example, a project may study proteins found in normal and diseased liver, and may include 4 experiments: tissue from two normal patients and from two diseased patients. The pepXML files should be created by searching the spectra with a database search engine such as SEQUEST, X!Tandem, or SpectraST, then validating the hits using PeptideProphet.
A project may at some point also represent the iProphet combined results of several projects by several researchers, searched by several different search engines.
Register projects and experiments using SBEAMS interface.
- Go to db.systemsbiology.net.
- Login to SBEAMS.
- Click tab "My Projects" or "Accessible Projects" and click "Add new project" at bottom.
- Fill out fields. Owner of project should be the experimenter who created the data, or the computational biologist who combined the data using iProphet. Project tag should match name of subdirectory in /sbeams/archive/<project_owner> that contains the data.
Obtain search batch IDs for each experiment and create an experiments list.
Run ProteinProphet on all pepXML files combined to create a single protXML file
Run PeptideAtlas build "pipeline".
Scripts can be found in /net/db/projects/PeptideAtlas/pipeline/run_scripts. Each script ultimately calls /net/db/projects/PeptideAtlas/pipeline/run_scripts/run_Master_current.csh, and this is where the meat of the pipeline resides.
