Christopher Paciorek

sporadic `test-ADlaplace.R` failures

2

These have been hard to pin down. I got it to happen once on my laptop but then rerunning doesn't invoke the error. Also the same error seems to occur...

use of `%*%` with two vectors has a strange behavior with unhelpful warning message

2

The manual says that doing matrix multiplication with two vectors should work but creates a 1x1 matrix. One would think one can therefore do this: ``` code

better error trap when constant equals 1

5

This came up as a possible parallelization question, but the error seems like it is probably simply triggered by using `T` without defining it and coercion to the value 1....

use of `na.rm` in `max` in nf code gives untrapped error

3

The presence of a second arg seems to cause the compiler to try to use `pairmax` which causes problems. See about error trapping the use of `na.rm` and possible enhanced...

``` code= nimbleCode({ y[2] ~ dnorm(0,1) }) m

computational issues in `runCrossValidate`

4

For predictive loss, we calculate the loss using the uncompiled model. Also, in line 46 of `crossValidation.R` we need to save the result of `compileNimble` in order for it to...

behavior of `availableWorkers` when Slurm `--nodes`, `--ntasks` and `--cpus-per-task` are provided

9

I noticed that in this case, available workers is based on `-c` (`--cpus-per-task`) and not `-n` (`--ntasks`). ```bash paciorek@smeagol:~> srun --ntasks=4 --cpus-per-task=2 --pty bash paciorek@scf-sm11:~> Rscript -e "parallelly::availableWorkers()" [1] "scf-sm11"...

symphony ignores OMP_NUM_THREADS

1

I have symphony installed on an Ubuntu 16.04 system, version 5.6.14 (installed from source) as well as version 5.6.1 (installed via Ubuntu package). symphony ignores the value of OMP_NUM_THREADS and...

warning in AD-enabled nimbleEcology

3

We'll need to address this warning that arises for `dCJS`: ``` [Note] Detected use of function(s) that are not supported for derivative tracking in a function or method for which...