Due to the very high IO necessary for trimmomatic's log production, some machines will halt this process to a crawl. A fix has been done in PR #178 but I don't consider this an ideal solution as it does not address the IO issue.
A potential solution is to no save the log file but instead obtain the trimming statistics from the trimmed reads themselves, as it's implemmented in INNUca
Due to the very high IO necessary for trimmomatic's log production, some machines will halt this process to a crawl. A fix has been done in PR #178 but I don't consider this an ideal solution as it does not address the IO issue.
A potential solution is to no save the log file but instead obtain the trimming statistics from the trimmed reads themselves, as it's implemmented in INNUca