Due to the way Nanocompore passes data between threads, when a transcript has a large amount of data associated with it (e.g. the transcript has very high coverage or is very long), Nanocompore gets stuck trying to push the data through the queue.
We are working on a permanent solution, but as a temporary fix when Nanocompore gets stuck indefinitely we recommend re-running it with --downsample-high-coverage set to a smaller number, e.g. 5000.
Due to the way Nanocompore passes data between threads, when a transcript has a large amount of data associated with it (e.g. the transcript has very high coverage or is very long), Nanocompore gets stuck trying to push the data through the queue.
We are working on a permanent solution, but as a temporary fix when Nanocompore gets stuck indefinitely we recommend re-running it with
--downsample-high-coverageset to a smaller number, e.g. 5000.