-
Notifications
You must be signed in to change notification settings - Fork 51
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
Singularity container creation #233
Comments
Thanks for the feedback! This is something that we are hoping to have in a future release. We will update here when it is ready. |
I've built a docker image for the SigProfiler tools. I haven't extensively tested it, but it builds just fine. GRCh37 and GRCh38 are installed. https://hub.docker.com/repository/docker/lculibrk/sigprofiler
|
Update on my previous comment, The container runs into the errors outlined here: #247 I'll try to rebuild and see if that helps. @mdbarnesUCSD , if this is an issue inherent to containerizing the SigProfiler suite, is there any guidance you can provide to workaround the issue? Happy to share the Dockerfile too. |
There are some issues that originate from the default behavior for SigProfilerMatrixGenerator and SigProfilerPlotting because of how they save and load files from site-packages. There are some updates that we are rolling out that enable this behavior to change by adding a parameter "volume" for a user specified location. SigProfilerExtractor will also need to be updated to utilize these changes before a singularity container will work. Here are the recent updates to SigProfilerAssignment. |
I tested the tool inside your Singularity container and it runs into the same errors as yours: #247 |
It would be helpful to have a Singularity container (image) of your package!
The text was updated successfully, but these errors were encountered: