-
Notifications
You must be signed in to change notification settings - Fork 9
The 'postprocessing' step is too slow. #137
Comments
Hi @nottwy, The Typically this step is fast compared to the rest of the pipeline, so I'm surprised that it's taking that long. Is there any output to the console? |
Also could you share |
The size of edges.hinges is 113 M and of hinge.list is 27 M.
Wait for your reply! |
These are very large edge/hinges files. Does your genome have telomeres/centromeres? I suspect that the graph could be very dense in these repetitive parts. Do you have Also, I remember that a while back you were trying to use the devG3 branch (see #129). Were you able to use it? Setting |
yeah, I still remember this thing and plan to do it. But now I just want to run your software successfully at this time. I'll give you response if I have any progress. And if I want to try del_telomeres, which step should I start from? |
Now it took me ~20 days at this step. Could you please make a little change to this step ('postprocessing') which makes the program reports the progress? |
Yes, we can do that. But I think it would be helpful if we could have your edges.hinge and hinges.list files. Could you write an email to ilanshom@gmail.com, so that we can coordinate a way for you to send us the files? Thanks! |
@ilanshom , |
Yes, thank you. We got your files and are working on it. Sorry for the delay. We'll keep you posted. |
Hi @nottwy, |
Great Work! |
Dear developers,
Now I'm at the 'postprocessing' step. The command is presented below. But it takes too much time.
Run postprocessing
hinge clip ecoli.edges.hinges ecoli.hinge.list
My data size is: 855 Gb .las file. Do you have any suggestions?
The text was updated successfully, but these errors were encountered: