-
Notifications
You must be signed in to change notification settings - Fork 1
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
FileNotFoundError in PDF generation #72
Comments
Hmm - OK - I will test this again here. Could you make sure that before you run it again you manually delete the folder :/data/robin2/robin2-res/NA12878_05_NB4_06_22Rv1_07 Thanks |
I can confirm that we did remove the output folder when we re-tried running Robin and the report today. Update on my local tests, though - this was run on macOS, and the filesystem doesn't seem to care about upper/lower case:
Our tests earlier today were done on a PromethION, which runs Linux - so I think that explains why my tests ran successfully before |
OK. I'll have a look at this. |
Though the new code was supposed to be completely case insensitive! |
Please could you update to the latest version and test to see if the report now works. |
Please re-open this issue if it isn't fixed - sorry it's taken a while. |
Just realised I never replied here - I can confirm that all is well. We've been running this on Linux with a case-sensitive filesystem and have had no problems with this since this PR was merged. Thanks! |
Upon running a PDF report in the GUI, the generation process fails with a stack trace:
Looking at the results folder, we find the files NanoDX_scores.csv and PanNanoDX_scores.csv. When the PDF generation process runs in src/reporting/report.py:
name
will be 'NanoDX' anddf_name
will be 'nanoDX_scores.csv'files_in_directory
will be ['NanoDX_scores.csv', 'PanNanoDX_scores.csv', ...]in
will pass and theif
will runfile_path
will end up as 'path/to/output/nanoDX_scores.csv', which still doesn't exist, causing 154 to crashIf we try fixing lines 142 and 143 to match the file names present, the report runs successfully:
I'm not sure how this didn't get picked up when I tested the fix for #70 - will try another test run from scratch.
The text was updated successfully, but these errors were encountered: