Difference between revisions of "Parse output.pl"
Kalemanovm (talk | contribs) |
Kalemanovm (talk | contribs) |
||
| Line 7: | Line 7: | ||
The flag <code>--pdb_full</code> must be given if HHblits run was performed against the pdb_full database and <code>--pdb70</code> must be given if the clustered pdb70 database was used. If uniprot20 was used, no extra flag has to be given. It is because the databases have different formats of headers of the cluster master sequences, where the IDs of cluster members are listed (and for pdb70 an extra mapping must be used). <br> |
The flag <code>--pdb_full</code> must be given if HHblits run was performed against the pdb_full database and <code>--pdb70</code> must be given if the clustered pdb70 database was used. If uniprot20 was used, no extra flag has to be given. It is because the databases have different formats of headers of the cluster master sequences, where the IDs of cluster members are listed (and for pdb70 an extra mapping must be used). <br> |
||
| + | |||
'''Note:''' As Psi-BLAST output file contains results for each iteration, it must be devided according to iterations before, which can easily be done with the script '''<code>devide_psiblast_out.pl</code>''' (found in the same directory). <br> |
'''Note:''' As Psi-BLAST output file contains results for each iteration, it must be devided according to iterations before, which can easily be done with the script '''<code>devide_psiblast_out.pl</code>''' (found in the same directory). <br> |
||
Usage: perl devide_psiblast_out.pl <psiblast output file> <br> |
Usage: perl devide_psiblast_out.pl <psiblast output file> <br> |
||
| − | Output: for example, if the original output file <code>psiblast-big-2iter</code> has results from two iterations, if will be split into two files <code>psiblast-big-2iter_1</code> (first iteration) and <code>psiblast-big-2iter_2</code> (second iterations). The files will be written into the same directory. Then you can be parse the iteration you need with <code>parse_output.pl</code>. |
+ | Output: for example, if the original output file <code>psiblast-big-2iter</code> has results from two iterations, if will be split into two files <code>psiblast-big-2iter_1</code> (first iteration) and <code>psiblast-big-2iter_2</code> (second iterations). The files will be written into the same directory. Then you can be parse the iteration you need with <code>parse_output.pl</code>. <br> |
| − | The output is a tab-separated file with the columns: |
+ | The output of <code>parse_output.pl</code> is a tab-separated file with the columns: |
*id |
*id |
||
*evalue |
*evalue |
||
| Line 21: | Line 22: | ||
The number of found hits is outputted onto stdout. If both HHblits and (Psi-)BLAST files are given, the overlap of hits with the same ID is calculated. <br> |
The number of found hits is outputted onto stdout. If both HHblits and (Psi-)BLAST files are given, the overlap of hits with the same ID is calculated. <br> |
||
| − | '''Note:''' The script "filters the duplicates": if more than one HSPs with the same ID are found in one output file, only one HSP with the lowest E-value is taken (for both the calculations and the output). |
+ | '''Note:''' The script "filters the duplicates": if more than one HSPs with the same ID are found in one output file, only one HSP with the lowest E-value is taken (for both the calculations and the output). <br> |
The usage will be extended to '''evaluate PDB hits against COPS''' and create files for plotting - work in progress. |
The usage will be extended to '''evaluate PDB hits against COPS''' and create files for plotting - work in progress. |
||
Revision as of 10:56, 5 May 2013
You can find the script parse_output.pl here on biocluster: /mnt/home/student/kalemanovm/master_practical/Assignment2_Alignments/scripts/task1. The usage of the script till now is parsing of (Psi-)BLAST and HHblits hhr output files:
Usage: perl parse_output.pl --out_h <hhblits hhr file> [--out_p <(psi-)blast output file>]
Optional parameters:
--pdb70, if HHblits was done against pdb70
--pdb_full, if HHblits was done against pdb_full
The flag --pdb_full must be given if HHblits run was performed against the pdb_full database and --pdb70 must be given if the clustered pdb70 database was used. If uniprot20 was used, no extra flag has to be given. It is because the databases have different formats of headers of the cluster master sequences, where the IDs of cluster members are listed (and for pdb70 an extra mapping must be used).
Note: As Psi-BLAST output file contains results for each iteration, it must be devided according to iterations before, which can easily be done with the script devide_psiblast_out.pl (found in the same directory).
Usage: perl devide_psiblast_out.pl <psiblast output file>
Output: for example, if the original output file psiblast-big-2iter has results from two iterations, if will be split into two files psiblast-big-2iter_1 (first iteration) and psiblast-big-2iter_2 (second iterations). The files will be written into the same directory. Then you can be parse the iteration you need with parse_output.pl.
The output of parse_output.pl is a tab-separated file with the columns:
- id
- evalue
- identity
- similarity
- length
- score
- probabilty (only for HHblits)
The number of found hits is outputted onto stdout. If both HHblits and (Psi-)BLAST files are given, the overlap of hits with the same ID is calculated.
Note: The script "filters the duplicates": if more than one HSPs with the same ID are found in one output file, only one HSP with the lowest E-value is taken (for both the calculations and the output).
The usage will be extended to evaluate PDB hits against COPS and create files for plotting - work in progress.
