You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any way how to find out more details what exactly went wrong? I ran
mono ThermoRawFileParser1.4.5/ThermoRawFileParser.exe -i=20220830_JL-4884_Forster_Ecoli_DMSO_rep2_EG-2.raw -f=2 -o=./ --logging=1
2025-04-07 15:31:12 INFO Started parsing 20220830_JL-4884_Forster_Ecoli_DMSO_rep2_EG-2.raw
2025-04-07 15:31:12 ERROR RAW file cannot be processed because of an error - ThermoFisher.CommonCore.RawFileReader.Facade.RawFileLoader
2025-04-07 15:31:12 INFO Processing completed 1 errors, 0 warnings
I tried both using the quantms docker container as well as locally (above).
this error usually means that the file is corrupted. The file size is about two times smaller compared to other replicates in the dataset - I guess, it was broken during transfer or acquisition.
I tried to use MSConvert on it with no success - I am afraid there is nothing to do here.
We will need to look into more human-understandable error reporting, though
Thanks for looking into it Vladimir! I just got confirmation from Caroline that she also could not open the first two raw files, exactly the ones I tested... Remindes me to be more random in selecting my test data...
Activity
caetera commentedon Apr 7, 2025
Hi @enryH,
this error usually means that the file is corrupted. The file size is about two times smaller compared to other replicates in the dataset - I guess, it was broken during transfer or acquisition.
I tried to use MSConvert on it with no success - I am afraid there is nothing to do here.
We will need to look into more human-understandable error reporting, though
enryH commentedon Apr 8, 2025
Thanks for looking into it Vladimir! I just got confirmation from Caroline that she also could not open the first two raw files, exactly the ones I tested... Remindes me to be more random in selecting my test data...
Should we close for now?
caetera commentedon Apr 9, 2025
I pushed a commit for the upcoming release #193 which should provide cleaner error messages for such cases.