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

two questions #32

Open
zmz1988 opened this issue Jul 10, 2023 · 1 comment
Open

two questions #32

zmz1988 opened this issue Jul 10, 2023 · 1 comment

Comments

@zmz1988
Copy link

zmz1988 commented Jul 10, 2023

Hi PengNi,

Thanks for providing the nice tool. Here I got two questions to ask you, if you don't mind.

First, I'm running modification base calling step with command CUDA_VISIBLE_DEVICES=0 deepsignal_plant call_mods. However, our cluster admin doesn't allow me to use CUDA_VISIBLE_DEVICES=0 on our GPU cluster, because the cluster setting already set this number. However, when I delete this CUDA_VISIBLE_DEVICES=0, my job seems not running even if it was assigned to a GPU device. May I ask how I can run on a GPU device if I don't set this option in the command? I mean I submit the job and request a GPU device for the job to run.

Secondly, may I ask when will the new version of deepsignal come? I have Nanopore R9.4.1 data, and I think deepsignal is so far the best option for the old Nanopore data to call methylation in all context. But the large file number generated by tombo limits how many jobs I can run in parallel. I have >20 samples to be called modified bases, and each takes more than a week to finish, if everything goes well. So far I can only run one sample per time due to the number of single read fast5. Will the new deepsignal improve this problem? Or how can I solve this problem with your expertise?

Thanks a lot and looking forward to your reply!

@PengNi
Copy link
Owner

PengNi commented Jul 28, 2023

Hi @zmz1988 , sorry for the delay.

  1. without setting CUDA_VISIBLE_DEVICES, deepsignal-plant will most likely use all available GPUs automatically. However, I don't have a cluster like yours, so I can not try in an environment exactly the same as yours.

  2. Yes, the time cost issue is something we are now planning to improve. We'd like to skip (or change) the tombo resquiggle step, maybe we can release an new version at the end of this year.

Thank you very much for using deepsignal-plant.

Best,
Peng

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