Hi all, I’d just want to say thank you for porting...
# dropm
My Tran
09/14/2026, 7:20 AMHi all, I’d just want to say thank you for porting the pipeline! I was able to finish most of the pipeline based on your guide here with our data. But the last MultiQC never finished, despite letting the step run for 18h+, with memory usage reaching up to 280 GB. So I eventually stopped the pipeline. I don’t know if this is a problem with MultiQC itself? And if so, is this still necessary to keep it?
n
Nicolas Vannieuwkerke
09/14/2026, 7:34 AMHi that seems like more than necessary! How many samples did you use in your run?
m
My Tran
09/14/2026, 9:35 AMI have 227 samples of 4 groups for AE and AS while for MAE I have 122
My Tran
09/14/2026, 9:38 AMInitially, I didn’t assign any specific memory to MultiQC; the setting was the default. The job was OOM-killed at 3h15min at 48GB, then after that I substantially increased the memory up to 400GB
n
Nicolas Vannieuwkerke
09/14/2026, 9:41 AMThe pipeline should be able to handle that sample size. Could you make an issue on the pipeline repository?
m
My Tran
09/14/2026, 2:28 PMIt seems like issue creation is restricted on my side. Can you please check if you have the time? Many thanks!
n
Nicolas Vannieuwkerke
09/15/2026, 12:49 PMEveryone with a github account should be able to make the issue 🤔. I'd prefer it if you could make the issue since it would be easier to report back to you in that way
2 Views