-
Notifications
You must be signed in to change notification settings - Fork 61
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
model problem #343
Comments
Hi, That's not normal. Can you run this test inside the 'test' folder of TADbit? python test_all.py 13 That will run a simple modelling that should take seconds to compute. Regards David |
How did you generate your matrix with "tadbit bin"? |
I did not use "tadbit bin" to generate the matrix, but directly used JuicerTools dump to generate the matrix.And then I did it with the whole chromosome matrix. |
Then I'm sure TADbit is trying to rebuild the full matrix and that's taking forever if your computer has not a lot of memory and speed.
So, David |
OK, I'll try it right away.Thank you for your help. |
I have converted my data to the following format and reduced the matrix scope to 2M (target region). CRM Chr2 2000000Chr2:0-200 resolution:10000MASKED0 0 1135.049 Then, I run it with the following command, but it has been running for 3 days and is not over yet. tadbit model -w test/both --input_matrix Chr2_2M.abc --noX --optimize --beg 1 --end 2000000 --reso 10000 --maxdist 400:500:100 --upfreq=-0.2:0:0.1 --lowfreq=-0.4:-0.2:0.1 --nmodels 20 --nkeep 20 -j 60 --cpu 60 I noticed in the background that Tadbit was sleeping and the system had free memory and CPU. Why is that? |
Hi, -j 60 --cpu 60 You don't need any job id. Regards David |
No, I installed it from source code, like this
|
When I ran the test data, I found that module Modelling took too long. It was expected to take 6 minutes, but I ran it in 2334 minutes.When I tested it with my own data, it ran for more than 20 days and didn't finish.Is it my system?I use the Centos7 system.
The text was updated successfully, but these errors were encountered: