Closed ananya-0729 closed 3 months ago
Not sure what branch this was on or what the config was, but try pulling the latest from Main. We pulled in some bug fixes that may have this covered. If not, please post some details like the options you were using so we can try to replicate.
Not sure what branch this was on or what the config was, but try pulling the latest from Main. We pulled in some bug fixes that may have this covered. If not, please post some details like the options you were using so we can try to replicate.
I've added the parameters of neat_config.yml. The content of neat_config.yml is as listed: reference: ecoli_genome.fna read_len: 250 threads: 8 coverage: 100 avg_seq_error: 0.0
All right, I will try to replicate this week!
We're working on a fix for this. I tested against E. coli with a coverage depth of 200 and read length of 250 on one of the compute nodes at NCSA and it ran for 10 hours and still didn't finish. Once we get the fix finalized, the only thing I'll add is that currently, our threading feature isn't working, but that is next on the to-do list. I would recommend trying to run NEAT several times on the same file and combine the results together to get to 200 depth coverage, rather than trying to run it all in one go. I think it will end up running faster that way.
I believe this is fixed!
Hi, I'm encountering a problem when trying to simulate read data: The content of neat_config.yml is as listed, reference: ecoli_genome.fna read_len: 250 threads: 8 coverage: 100 avg_seq_error: 0.0
Thanks in advance!