-
Notifications
You must be signed in to change notification settings - Fork 2
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
Problems running ASimulatoR from within DICAST #2
Comments
Hi Andre, Pardon the long wait. This is my first public repository on git and my first issue, and somehow I missed linking the notifications to my email. :) Welcome to the DICAST's git. For now, I suspect that you've got Meanwhile I'll reach out to ASimulatoR guys about this bug. Thanks for your inputs so far. I hope we can get ASimulatoR running for you soon. |
Hi Amit, thanks for your reply and no worries about the delay. I had a look and I made no modifications to I tried your suggestion to remove any files
Please let me know if any other information is required from my end. Lastly, one more question. Is the simulation data you used for the evaluations in your DICAST preprint publicly available? Thanks and Cheers, Andre |
Hi Andre, Sorry we haven't the data public, because it is several 100GBs big, but if I could have a little more of your patience, ASimulatoR will give you many more datasets for you to try DICAST with. Furthermore, the author of ASimulatoR will join us by next week, if we haven't solved this by then. Can I ask for the outputs of Thanks in advance. |
Also, perhaps, if it's faster, I would ask you to install ASimulatoR directly in your R environment. https://github.com/biomedbigdata/ASimulatoR. unfortunately, I still haven't been able to replicate your error message. Funny we were hoping that Docker in linux and mac would behave the same. |
Hi Amit, As requested, following the output of
and
I can also give ASimulatoR a try directly. I assume, I could then still use the datasets within DICAST, as long as they are stored in the pre-defined structure? Cheers, |
Hi Andre, Thank you for you patience, I'd ask you to try a quick hack for me. This is so I may know if this bug comes from something funny DICAST does, vs something that I should talk to the authors of ASimulatoR about. Can you please make a quick bash script with the code below in your favorite new directory and see if it works. This is to run ASimulatoR with the same configurations as the default run on DICAST. This re-downloads the essential files needed for ASimulatoR. This is the minimal code needed to run ASimulatoR independently.
I'd copy the Furthermore, I'd ask you to copy the Everything else should work fine. |
Hi Amit, thanks for posting the script. I gave it a try, but got the same error in the end. I skip the output of the download section in the beginning and will only paste the log after:
I did not make any changes to the script that you posted above. Let me know if I should have. Thanks and Cheers, Andre |
Thank you Andre, for your quick response. Are you running this in a Mac environment? Can we have the specs from your machine and of the OS? Do you have access to a linux machine you could use? if not, we can try and figure out how to transfer the data we had from ASimulatoR for transparency's sake. Unfortunately this might be where we learn that ASimulatoR doesn't run on mac and maybe DICAST too :(. |
Hi Amit, I am running on a Mac with the following setup:
Let me know if you need any more details. Happy to try it on an a linux machine. I will let you know how it went. Just out of curiosity, would the setup also run with Singularity instead of Docker? Thanks and Cheers, Andre |
Thanks Andre, This is perfect. We do plan to develop on Singularity soon, but unfortunately this is still in future work.. We wanted to start with dockers and port docker images to singularity images. Stay tuned at this repo for further news. Thanks for your support so far. |
Hi Andre, Finally, I found some time to look at this issue and the only thing I can identify is that somehow the exon_superset file gets corrupted. You have helped us a lot already, might I ask you to try to use the attached superset instead of the one you generated? You'll have to rename it to Thank you in advance. |
Hi Quirin, finished loading superset assign variants to supersets... exporting gtf for read simulation... |
Hi @NormanRog, Best, |
After looking into this more deeply, this looks like a memory issue because of too many processes being spawned.
but
Forking 20 processes probably took too much memory, which led to some being killed and not delivering results in both steps: creating the superset and7or the variants (a corrupted superset will lead to the error I added a few lines to the ASimulatoR for better documentation and limited Hope this helps. |
Dear DICAST team,
After some setup issues (outlined in #1), I was able to successfully start the GUI. I selected to simulate reads with ASimulatoR and am currently stuck at the following error message:
As a setup procedure, I used the script
initializing-dicast.sh
to populate the input structure and unzipped its contents. Then I started the GUI, selected the input directory, acknowledged possible overwrites and ticked the box for "Do you want to run ASimulatoR?".Let me know if you need additional info from my side.
Cheers,
Andre
The text was updated successfully, but these errors were encountered: