google-code-export / peptide-shaker

Automatically exported from code.google.com/p/peptide-shaker
1 stars 1 forks source link

Export Identification Features #40

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
> What steps will reproduce the problem?
Not too sure if this is a issue or me missing something.

My FASTA file contains contains decoy sequences which were added by the 
SearchGUI software. I do my search and open the results in Peptideshaker. I 
then export the identification features via peptides tab, with the following 
criteria selected:

- Protein Accession
- Protein Description
- Peptide Sequence
- Modification Status
- Precursor Charges 

I then select export. Here is where I think there is an issue. In my exported 
results it contains Reverse matches. But in the peptide shaker GUI (under 
protein window in description) there are not any hits with the reverse 
sequence. I this an issue or a setting I need to select?

> What is the expected output? What do you see instead?
No reversed sequences in my exported output. 

> What version of the product are you using? On what operating system?

> Please provide any additional information below.

> If the reported issue resulted in the tool crashing, please
> also upload the file called PeptideShaker.log (found in the
> PeptideShaker-X.Y.Z\resources folder).

Original issue reported on code.google.com by harpal28...@gmail.com on 27 Feb 2014 at 4:40

GoogleCodeExporter commented 9 years ago
As the decoy matches are only interesting when validating the results the decoy 
matches are not displayed in the Overview tab of PeptideShaker. You can see the 
decoy matches in some of the other tabs, for example in the Spectrum IDs tab.

When you export data you will get all the matches in both target and decoy. But 
you can easily filter out the decoys in the exported file by using the column 
called 'Decoy', where every decoy match will here have a '1' and every target 
match a '0'.

(I hope this answers your question and I'm therefore closing the issue.)

Original comment by harald.b...@gmail.com on 27 Feb 2014 at 8:26