Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Filter command: panic: Cannot write file. cannot create protein report #506

Open
hcadre opened this issue Oct 14, 2024 · 4 comments
Open

Comments

@hcadre
Copy link

hcadre commented Oct 14, 2024

- Upload your log file
log_2024-10-14_13-22-46.txt

- Describe the issue or question:
I tested the DIA_SpecLib_Quant_diaPASEF workflow with diaTracer integrated on a single diaPASEF file using default settings (FragPipe 22.0; diaTracer 1.1.5). The workflow finished the PhilosopherFilter step, buth then stopped at PhilosopherReport with "Cannot write file. cannot create protein report"

Anny suggestion on how to proceed?

Best,

Hannes

@fcyu fcyu transferred this issue from Nesvilab/FragPipe Oct 14, 2024
@fcyu fcyu changed the title SpecLib_Quant_diaPASEF error Filter command: panic: Cannot write file. cannot create protein report Oct 14, 2024
@anesvi
Copy link

anesvi commented Oct 14, 2024

Perhaps the disk is full? Cannot say anything from the log.

@anesvi
Copy link

anesvi commented Oct 14, 2024

Everything is fine (and good number of peptides/proteins identified) up to the writing report file stage. You can try to rerun from diatracer.mzML file on another computer to see if works there. Load diatracer.mzML as DDA file and the original .d file as DIA-Quant ( no need to reconvert with diatracer again)

@hcadre
Copy link
Author

hcadre commented Oct 15, 2024

I successfully reran the analysis - on the same computer (!) - from diatracer.mzML (DDA) and from the original .d file (DIA-Quant) as you suggested. I then repeated everything from scratch (.d file copied to new folder; data type set to DIA; diaTracer enabled) - again successfully. No idea, what had happened during the first attempt.... But thank you so much for your comments - they gave me another go.

@anesvi
Copy link

anesvi commented Oct 15, 2024

Glad to know it work. If you have any feedback on our new diatracer workflow, let us know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants