The random number generator is tracked by a global state, which is a
violation of functional programming. This is unavoidable. This is why we
really don't want packages to EVER touch the random number state for
example by setting the seed. You can also be affected by this if any
function you
This does sound like a BiocParallel side effect, and I would suggest
holding off for another week so for the BiocParallel changes to be
finalized.
On 9/24/21, 2:05 PM, "Bioc-devel" wrote:
Hello,
My package `clusterExperiment` has not changed but is hitting errors on the
devel branch. I’ve
Hello,
My package `clusterExperiment` has not changed but is hitting errors on the
devel branch. I’ve pinpointed it to the fact that a small dataset I am running
the tests on is randomly subsetted from a larger subset and is no longer
choosing the same observations. I have already in previous
Hello Bioconductor Community!
The newest db0s, OrgDbs, and TxDbs annotation packages for the upcoming
Bioconductor 3.14 release are up and available for download in the devel version
of Bioconductor.
The deadline for submitting contributed annotations will be Wednesday October
20th.
The new
Hi Hervé, Hi all,
Yes, I totally understand and agree with the standard of Bioc packages
development. I always try to follow it as best as I can. But regarding the
"real rerunnable vignettes", I think there are several scenarios that make
it really difficult to follow this standard way:
1. Some
Errors that are intermittent and platform-specific are often due to memory
corruption, and can be investigated on Linux platforms with valgrind or
similar tools. Have you taken this approach?
On 9/24/21, 3:22 AM, "Bioc-devel" wrote:
Hi,
for several years xcms is suffering from absolutely
Hi,
for several years xcms is suffering from absolutely spurious
issues on macOS.
There is no pattern regarding release/devel, R versions, different
macOS machines like merida1 in 2019, to machv2 today and a few
occurances inbetween. The tssue usually resolves itself after a few
days without
