Immortalin / peptide-shaker

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

protein export option not working #6

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. open any .omx file generated by searchgui 
2. export, protein, select all, export 
3.

What is the expected output? What do you see instead?
textfile containing details but we see text file containing only headers and no 
protein information

What version of the product are you using? On what operating system?
peptide shaker 12.2. Windows XP with service pack3

Please provide any additional information below.

Original issue reported on code.google.com by brautmah...@gmail.com on 29 Dec 2011 at 8:30

GoogleCodeExporter commented 9 years ago
Thank you for reporting the bug. I've been able to reproduce it and will try to 
fix it at release a new version.

Original comment by harald.b...@gmail.com on 29 Dec 2011 at 10:15

GoogleCodeExporter commented 9 years ago
Seems like I was a bit quick on calling this a bug. The export function works, 
the problem is that by clicking 'Select All' one also selects the 'Request 
Starred' option, and if you don't have any starred proteins (and the same for 
the peptides and psms exports) you will get an empty export with just the 
column headers.

However, the 'Request Starred' should perhaps not be included in the 'Select 
All' features. I'll fix this in the next release. For now you can just deselect 
'Request Starred' and you should get more data in your export results.

Original comment by harald.b...@gmail.com on 29 Dec 2011 at 10:43

GoogleCodeExporter commented 9 years ago
OK, the required code changes have been made. The fix will be included in the 
next release. Probably out next week.

Original comment by harald.b...@gmail.com on 29 Dec 2011 at 11:00

GoogleCodeExporter commented 9 years ago

Original comment by harald.b...@gmail.com on 29 Dec 2011 at 11:01

GoogleCodeExporter commented 9 years ago
PeptideShaker v0.13.0 has now been relased fixing this issue.

Original comment by harald.b...@gmail.com on 4 Jan 2012 at 2:55