You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Why is there no FRiP score section in my MultiQC report? #291
Hello, I'm new to nfcore/cutandrun. I ran it recently and got peaks in most of my samples in my MultiQC report. However, there isn't the FRiP score section. I'd like to understand why.
I had the same issue with version 3.2.2 but I solved it in my case by specifying the --skip_deduplication parameter. In my experimental setup I was running 6 samples without any IgG control, in which case you expect the default behaviour to simply skip deduplication altogether. I believe what happens however is the flowswitch config still defines params.run_remove_dups as true in this case, so the pipeline expects to run a deduplication process which never actually takes place because there are only target inputs, and hence the deduplication output and the subsequent input for the PEAK_FRIP process never arrives.
Until the bug is fixed, specifying either --skip_deduplication or --dedup_target_reads would seem to send the appropriate signal to the pipeline depending on the desired outcome.
Activity
gianmore commentedon Mar 30, 2026
Hi, I'm having the same issue with the version 3.2.2
bio15anu commentedon Nov 10, 2026
I had the same issue with version 3.2.2 but I solved it in my case by specifying the
--skip_deduplicationparameter. In my experimental setup I was running 6 samples without any IgG control, in which case you expect the default behaviour to simply skip deduplication altogether. I believe what happens however is the flowswitch config still definesparams.run_remove_dupsas true in this case, so the pipeline expects to run a deduplication process which never actually takes place because there are only target inputs, and hence the deduplication output and the subsequent input for thePEAK_FRIPprocess never arrives.Until the bug is fixed, specifying either
--skip_deduplicationor--dedup_target_readswould seem to send the appropriate signal to the pipeline depending on the desired outcome.