Closed Arthfael closed 3 months ago
Since all three software not just MSFragger failed in processing your data, you probably need to double check your data acquisition parameters.
Just in case , you need to have the Visual C++ Redistributable installed to make the Bruker's library work. It probably isn't the cause of the errors because most Windows operating systems already have it installed.
Best,
Fengchao
Yes, sorry, I guess I figured out that the problem may be at an earlier level as I was writing the error report and trying a few things to provide more info. Still, I hoped that the FP error may shed some light on the cause of the issue.
On Mon, Aug 5, 2024 at 4:33 PM Fengchao @.***> wrote:
Since all three software not just MSFragger failed in processing your data, you probably need to double check your data acquisition parameters.
Just in case , you need to have the Visual C++ Redistributable https://aka.ms/vs/16/release/VC_redist.x64.exe installed to make the Bruker's library work. It probably isn't the cause of the errors because most Windows operating systems already have it installed.
Best,
Fengchao
— Reply to this email directly, view it on GitHub https://github.com/Nesvilab/FragPipe/issues/1707#issuecomment-2269225587, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSHV4IFOKOB2DVYA3V6EYTZP6EJ3AVCNFSM6AAAAABMANSRQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRZGIZDKNJYG4 . You are receiving this because you authored the thread.Message ID: @.***>
Hi,
My search on simple QC files is failing with the following error:
This would suggest that there is an issue with the .d folders, yet they look normal to me:
I have tried to convert the files to mzML to see if maybe that would work. Here is the outcome:
As far as I know, the only specificity of these files is that immediately before acquiring them we switched from using a nanoElute 2 to an Ultimate 3000 nano as the HPLC. Could this be causing issues with the method? Is there something which we would need to configure in the Bruker software for these to run correctly? The Bruker ProteoScape search also failed (which could mean anything, seeing how it randomly fails for a lot of stuff - but in this case does work as further supporting evidence that something isn't quite right).