Mercurial > repos > bornea > saint_preprocessing
comparison SAINT_preprocessing.xml @ 20:0ac97a6298c2 draft
Uploaded
author | bornea |
---|---|
date | Thu, 14 Apr 2016 17:24:05 -0400 |
parents | 3953103b56f9 |
children | d9592cc1df99 |
comparison
equal
deleted
inserted
replaced
19:9329d9ec60b0 | 20:0ac97a6298c2 |
---|---|
69 <param name="input" value="fa_gc_content_input.fa"/> | 69 <param name="input" value="fa_gc_content_input.fa"/> |
70 <output name="out_file1" file="fa_gc_content_output.txt"/> | 70 <output name="out_file1" file="fa_gc_content_output.txt"/> |
71 </test> | 71 </test> |
72 </tests> | 72 </tests> |
73 <help> | 73 <help> |
74 # Pre-Processing | |
74 | 75 |
75 Pre-processing: | 76 * * * |
76 | 77 |
77 APOSTL is able to recognize either a Scaffold "Samples Report" file (tab-delimited txt file) or the "peptides.txt" file output in the MaxQuant "txt" output folder. No modifications should be made to these files. Using the "Bait Create" tool, you can create your "bait.txt" file. It is important that the individual bait names match the bait names within your scaffold or MaxQuant output. APOSTL uses the bait file to findthe user's baits of interest. Additionally there is an option to make the prey file (Y/N). When making a prey file, APOSTL queries Uniprot ( http://www.uniprot.org ) in order to extract protein amino acidlengths and gene names. This takes several minutes depending on your internet connection. Some users may want to run SAINTexpress using the same data set while changing which baits are considered test or control It is useful to toggle "Make Prey" off in order to save time by circumventing this step as the same prey file can be used for both SAINTexpress runs. | 78 This tool will read in a Scaffold _Samples Report_ file (tab-delimited txt file) or a MaxQuant _peptides.txt_ file and process them to generate a _Bait File, Prey File,_ and _Inter File_ for SAINTexpress analysis. |
78 | 79 |
79 INPUTS: | 80 #### 1) MaxQuant or Scaffold |
80 | 81 |
81 Scaffold file: | 82 APOSTL is able to recognize either a Scaffold _Samples Report_ file (tab-delimited txt file) or the _peptides.txt_ file output in the MaxQuant _txt_ output folder. No modifications should be made to these files. Please designate which one is being provided. |
82 | 83 |
83 - Scaffold "Samples Report" output (tab-delimited txt file) | 84 #### 2) Scaffold or MaxQuant File Input |
84 | 85 |
86 Select the corresponding _Samples Report_ or _peptides.txt_ here. | |
85 | 87 |
86 MaxQuant file: | 88 #### 3) Create Prey File |
87 | 89 |
88 - MaxQuant "peptides.txt" file (tab-delimited txt file) | 90 Select whether or not you would like APOSTL to generate a prey file. |
91 | |
92 When making a prey file, APOSTL queries a user provided FASTA database (see below) in order to extract protein amino acid lengths and gene names. This may take several minutes depending on your computer and if your Galaxy distribution is cluster enabled. Some users may want to run SAINTexpress using the same data set while changing which baits are considered test or control. It is useful to toggle **Create Prey File** off in order to save time by circumventing this step as the same prey file can be used for both SAINTexpress runs. | |
93 | |
94 #### 4) Provide Uniprot FASTA database | |
95 | |
96 Please specify a FASTA file containing the protein sequence. You can download the latest release of Uniprot's reviewed sequences (Swiss-Prot) [here](http://www.uniprot.org/downloads). For computing efficiency, please limit your FASTA file to your species of interest. It is generally advised to use the same FASTA database that was used for your database searches during peptide and protein ID. | |
97 | |
98 #### 5) Are You Providing Your Own Bait File? | |
99 | |
100 Users have two options for providing a _Bait_ file. If you would like to create your own _Bait_ file, select <kbd>Yes</kbd> and designate the file below. If you would like to use the **Bait Create** tool to create a _Bait_ file within Galaxy, please select <kbd>No</kbd> and proceed to the **Bait Create** tool. | |
101 | |
102 #### 6) Bait File | |
103 | |
104 If you selected <kbd>Yes</kbd> above, please specify the _Bait_ file you would like to provide. If you selected <kbd>No</kbd> above, ignore this argument and proceed to the **Bait Create** tool. | |
105 | |
106 > **Note:** Individual bait names must match to the sample names within your Scaffold or MaxQuant output exactly and must contain no whitespace characters (e.g. spaces) or dashes. | |
107 | |
108 #### 7) Bait Create | |
109 | |
110 Using the **Bait Create** tool, you can create your _bait.txt_ file. | |
111 | |
112 > **Note:** Individual bait names must match to the sample names within your Scaffold or MaxQuant output exactly and must contain no whitespace characters (e.g. spaces) or dashes. | |
113 | |
114 APOSTL uses this bait file to find the user's baits of interest within a _Samples Report_ or _peptides.txt_ file and when preparing the _inter.txt_ file. | |
115 | |
116 * * * | |
117 | |
118 Once your parameters have been finalized, please press the <kbd>Execute</kbd> button to start processing. This may take a few minutes. Once your process has been completed, you will see your _Bait File, Prey File,_ and _Inter File_ on the right hand side of your panel highlighted in green. | |
89 </help> | 119 </help> |
90 </tool> | 120 </tool> |