-
Notifications
You must be signed in to change notification settings - Fork 58
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
Unable to create HTML report (Cellbender version 0.3.0) #278
Comments
Okay thanks for clarifying. Is there any more to that traceback or error message? It looks like it is erroring out when I try to postprocess the HTML here
At that point, the HTML file should already exist, but it seems the error is saying the file does not exist. I am a bit confused because I would be expecting some other error message earlier on that indicates that the HTML was not produced for some other reason. |
There are no other traceback or error messages. I can send you the entire log file. Is there an email that I can send it to? |
Yeah that would be great! [email protected] |
I think I may need to be able to side-step the postprocessing function by creating a |
FWIW, we're also experiencing the exact same issue as @TeodoraTockovska, on a Linux cluster, running CellBender v0.3.0 (from singularity container). I agree with @sjfleming as well, the error indicates the file should already exist but doesn't, so it's probably a red herring. (re-edit) I re-rested using the tiny dataset generated via your
It works in Docker, but didn't in Singularity. The issue (in our case) is that Singularity was loading
This was preventing the temporary In any case, for anyone else using Singularity, be sure to use the
Problem fixed |
Hello Cellbender team!
I was browsing the troubleshooting page here, and it states to report any issues if HTML files fail to generate. My log file reported an error and it couldn't generate the HTML report. Please see the error message below:
I ran the tool using the following command, omitting "--cuda" (ran using CPU instead of GPU):
The text was updated successfully, but these errors were encountered: