Skip to content

Why is there no FRiP score section in my MultiQC report? #291

Open

Description

@RnapolyMerase1212

Description of the bug

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.

The primary code I used was:

nextflow run nf-core/cutandrun      \
    -latest                      \
    -params-file nf-params.json  \
    -resume                      \
    -r 3.2.2                    \
    --igenomes_base /data/bio/igenomes/references  

And the code in my nf-params.jason file is:

{"use_control": true, 
"peakcaller": "SEACR,MACS2", 
"spikein_fasta": "/PATH/TO/Ecoli/FASTA/FILE", 
"spikein_bowtie2": "PATH/TO/Ecoli/INDEX", 
"fasta": "https://ftp.ensembl.org/pub/release-109/fasta/homo_sapiens/dna/Homo_sapiens.GRCh38.dna.primary_assembly.fa.gz", 
"gtf": "https://ftp.ensembl.org/pub/release-109/gtf/homo_sapiens/Homo_sapiens.GRCh38.109.gtf.gz", 
"macs_gsize": 2913022398, 
"macs2_pvalue": 0.05, 
"macs2_narrow_peak": true, 
"input": "samplesheet.csv", 
"outdir": "./results"}

Command used and terminal output

Relevant files

No response

System information

No response

Activity

  1. gianmore commented on Mar 30, 2026

    @gianmore

    Hi, I'm having the same issue with the version 3.2.2

  2. bio15anu commented on Nov 10, 2026

    @bio15anu

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions