linux command-line requires data folder #14
Comments
|
The data folder has to be either inside the zip file (which can be done by adding the -output_data to the SearchGUI command line), or Reporter should look for the data in the original folder used as input to SearchGUI.
Correct, as the input to Reporter is the output from PeptideShaker after processing the identification files, thus the identification files themselves are no longer needed at this stage. |
|
Unless Reporter explicitly has that data folder, it will not run. Without ./data folder from searchgui_out.zip (I renamed it to datax): With data folder (partial output): searchgui_out.zip is also present in the folder and the original files used to run SearchGUI are in their original locations. Incidentally, the same issue prevents Peptideshaker on Windows from loading .psdb files generated on linux. You have to have the ./data folder or it won't load (same error message) (it may happen in other cases but this is the most common for me) |
|
Can you share the Reporter log file? You'll find it via the Reporter Welcome dialog > Settings & Help > Help > Bug Report. |
|
I wonder if there's a series of related issues. If I run PeptideShakerCLI (command-line) without the -fasta_file option, it will load searchgui_out.zip and process it and save the psdb without issue, but then when I try to run ReportCLI (command-line), it can't find the FASTA file with the following message in Peptideshaker.log: For the Reporter error it is similar: So clearly it expects to find the FASTA in a temp folder that no longer exists because it expects it to be in the directory created by extracting searchgui_out.zip, but that directory is removed once PeptideShakerCLI is done and thus not available for ReportCLI. Note that Reporter doesn't work even if I used the -fasta_file option to generate the psdb originally but ReportCLI for peptideshaker will work. However, the error message for Reporter changes: |
|
If you want to use the PeptideShakerCLI output as input to ReportCLI, please use the -zip option when running PeptideShakerCLI. This will ensure that all of the needed files are included in the zip file. However, if you know that you want to export the reports when processing data in PeptideShaker, I would rather recommend adding the ReportCLI options directly to the PeptideShakerCLI command line. This is much faster, as there is no need to reopen the project, and has the advantage that all of the required files will always be available. As for Reporter, I would recommend using the -zip option in PeptideShaker there as well. |
|
I didn't know that regarding Peptideshaker although I prefer to keep the commands separate for other reasons. However, if I try loading a zip into Reporter (which should be supported), it doesn't work either. From the command line message showing it should be supported: So then:
I realize all that happens is that the zip gets extracted (so I can extract it myself), but zipping via Peptideshaker just to immediately unzip for Reporter doesn't seem desirable (zipping is slow) when the files are already present, in their original locations, and unzipped in the first place. If Reporter needs certain files beyond the psdb, it seems like it would be better to let us have the option to specify the location as there seems to be something amiss with detecting where the files are with the psdb only (i.e. it might point to a temp folder that was removed). Well, either way, I can make my pipeline work as is so if it's just more of a philosophical difference about how to handle files, we can consider my case resolved. Thanks! |
|
There was a typo in the Reporter code for recognizing the .zip file extension (or rather the "." was missing), hence the file was assumed to be a psdb file instead. I will release a new version later, as I just noticed that Reporter has a similar issue with the progress display that you noted for the FastaCLI. With regards to the initial issue, you are correct in that the problem is that the data files are inside the searchgui.zip file and thus only available as long as this zip file is temporarily unzipped during the processing in PeptideShaker. After the PeptideShaker project has been saved, the searchgui.zip file will be closed and the zipped data folder will no longer accessible. The solution may be a be counter-intuitive, but if you do not use the -output_data option when running SearchGUI the original file locations will be the ones used in PeptideShaker (as provided via the PeptideShakerCLI options -fasta_file and -spectrum_files). This means that PeptideShaker will inform Reporter of the original file locations and, if these can still be found, Reporter should no longer complain about missing data files. Note that both PeptideShaker and Reporter looks for the data files in three locations: first the original location, then a folder called "data" next to the psdb file, and finally, in the same folder as the psdb file. Hence, if you put your data files in either of the two latter locations, this works as a quick fix for when the original files have been moved or can no longer be found. Adding the -fasta_file and -spectrum_files options for ReporterCLI sounds like a good idea as well though. I'll see what I can do. |
|
I just released a new version of Reporter that supports using zipped PeptideShaker projects as input to the command line. (I have not yet looked at the other data folder issues.) |
Hello,
When importing a psdb in linux (command line), it's required that the data folder inside searchgui_out.zip is present.
For example, if the psdb file is at /data/test, there needs to be a folder /data/test/data containing the files from the data folder inside searchgui_out.zip
There also doesn't seem to be an option to do -identification_files to select the searchgui_out.zip as with peptideshaker.
Thanks!
The text was updated successfully, but these errors were encountered: