David Carlson
12/10/2025, 4:34 PMdev branch), that the p-values reported tend to fall in discrete clusters instead of being more continuously spread. For example, sorting from smallest to largest, the p-values I'm seeing are a series of the following:
0
1.00E-04
2.00E-04
3.00E-04
4.00E-04
5.00E-04
6.00E-04
7.00E-04
etc.
Dozens or hundreds of genes have these same p-values, and there are no values in between these groups of numbers. In prior runs of the pipeline, p-values were more continuously spread (e.g., I might have values between 0 and 1.00E-04 or between 1.00E-04 and 2.00E-04).
Is this difference due to some change in the way that the pipeline (or DESeq2) is rounding the p-values, or is this a peculiarity of my specific data set?David Carlson
12/10/2025, 6:48 PMDavid Carlson
12/10/2025, 6:50 PMDelfina Terradas
12/15/2025, 4:50 PM--round_digits parameter that has been implemented since the last release. By default the pipeline uses 4 digits, but you can try changing this for a higher number.David Carlson
12/15/2025, 5:19 PM--round_digits parameter?David Carlson
12/17/2025, 2:22 PM--round_digits parameter in the current dev version. I've set the parameter to 8 and 12, and I'm still seeing many p-values set to zero when they are not zero in the release version:
This is true in both the results table and the report. See the following screenshot:Uri David Akavia
02/22/2026, 9:02 PMapply(data.frame(comp.results), 2, function(x) sprintf(paste0("%g" opt\$round_digits), x)) I'd have to check and see exactly how to write this in R.
This will print everything below significant digits in E format, but still keep a fixed amount of significant digits.
I can open an issue, but this will need to be fixed on multiple modules. Would you like me to do that? If so, would you like me to have one PR per module, or one big PR that shifts all the R code (and the relevant snapshots)?