Closed PoisonAlien closed 5 years ago
Hi @PoisonAlien
Thanks for reporting this. It is not a bug in the software, DecompPipeline follows a very stringent way of probe filtering: It determines for each probe if any of the samples is outside of the quantile range, and removes this probe if only one sample does not follow the criterion. Thus, setting min.int.quant=0.05
and max.int.quant=0.95
is pretty stringent.
If you want to remove fewer sites, I'd recommend to have values of 0.01/0.99 or even 0.001/0.999.
The min.n.beads
option is independent of the intensity filtering.
Got it! Thank you.
Hi @lutsik and @schmic05 ,
I am running DecompPipeline on EPIC arrays, and it seems that most of the probes (~90%) are filtered due to intensity filtering. Here is the log,
Is it a bug ? I lowered
min.n.beads
argument to 2 and yet it removed so much of the probes. Should I disable any of the arguments ?In case you need to know, input
tall_rnb_set
is an Rnbeads object created with following command.