Closed rbartelme closed 4 years ago
Note: iRODS v4.1 is not currently working, but this is non-essential for this specific analysis.
Stan is a real pain to install inside a container, this is going to be quite complex.
https://github.com/stan-dev/rstan/wiki/Installing-RStan-on-Linux and https://github.com/antoine-sachet/rocker-ML/ helped get Stan running inside the rocker/verse container environment locally. Testing the container on VICE today.
rstan
version 2.19
causes R session to abort on the DE when it loads. It does not abort when the container is run locally. It's possible this is a server side K8s issue.
Container runs on VICE but dies when I run brm
function, same abort message that the DE throws when I simply try to load the package.
After talking to Julian, Sarah and @tyson-swetnam about this, it seems the clang
configs were incorrect for the user rstudio
that runs the container. Local test of the container was able to run the diagnostic script for rstan:
stancode <- 'data {real y_mean;} parameters {real y;} model {y ~ normal(y_mean,1);}'
mod <- stan_model(model_code = stancode)
Pushing to CyVerse VICE, will test with the diagnostic script there. If the diagnostic script runs without throwing C++ errors, then I will likely need to just refactor my model for the canopy_height
.
DE is still throwing errors, but the container runs fine locally. Sarah is looking into it.
Works fine on the DE after Sarah recompile rstan in the container with the K8s admin tools. Container runs fine on GPU06 and is updated to R4.0 with Ubuntu 18 LTS.
stan
,rstan
,tidybayes
,ggfortify
,brms
cyversevice/rstudio-bayes-cpu:3.6.2