Compiler message for stan?

[ahartikainen]

See my earlier answer in this thread.

@ahartikainen

real_path() {
[[ $1 = /* ]] && echo “$1” || echo “PWD/{1#./}”
}

stan_path=“<full_path_here>/cmdstan-2.16.0”

stan_make() {
local output_relative={@: -1} local head_args={@:1:#-1} local output=(real_path $output_relative)
make -C $stan_path $head_args $output
}

stan_summary() {
local summary=“bin/stansummary”
local path=$stan_path/$summary
path @
}

stan_stanc() {
local stanc=“bin/stanc”
local path=$stan_path/$stanc
path @
}

stan_cmd() {
make -C stan_path @
}

[bhomass]

Ah yes, I didn’t take it seriously last time. But I tested it out and it does work.

I create these functions inside a .sh file, which I source inside ~/.bash_profile. After that I can call

stan_make my model

inside my working directory.

Thanks again.

as a side note, I wonder if this can be release as a legitimate executable along side stanc.

[sakrejda]

The problem with these is making them cross-platform and reliable. If somebody is willing to take that on it would be great to release something like this but otherwise it’s just a bag of tricks.

[syclik]

@sakrejda

The problem with these is making them cross-platform and reliable. If somebody is willing to take that on it would be great to release something like this but otherwise it’s just a bag of tricks.

I completely agree with @sakrejda here. Shipping additional scripts that aren’t well-tested with different boundary conditions will just add to the maintenance burden and confusion. If anyone can actually write scripts that will work (and really list the conditions under which it won’t), we can distribute those.

@bhomass, here’s how a Stan program is compiled on my Mac using clang++:

clang++ -I src -I stan/src -isystem stan/lib/stan_math/ -isystem stan/lib/stan_math/lib/eigen_3.3.3 -isystem stan/lib/stan_math/lib/boost_1.62.0 -isystem stan/lib/stan_math/lib/cvodes_2.9.0/include -Wall -DEIGEN_NO_DEBUG  -DBOOST_RESULT_OF_USE_TR1 -DBOOST_NO_DECLTYPE -DBOOST_DISABLE_ASSERTS -DFUSION_MAX_VECTOR_SIZE=12 -DNO_FPRINTF_OUTPUT -pipe  -Wno-unused-function -ftemplate-depth-256    -O3 -o examples/bernoulli/bernoulli src/cmdstan/main.cpp -include examples/bernoulli/bernoulli.hpp stan/lib/stan_math/lib/cvodes_2.9.0/lib/libsundials_nvecserial.a stan/lib/stan_math/lib/cvodes_2.9.0/lib/libsundials_cvodes.a 

The C++ compilers that we work with (clang++, g++) don’t have issues with spaces, so you can adjust that line to have it compile from an arbitrary directory. All you would have to do is change paths for all the includes and the input and output filenames.

[sakrejda]

@bhomass

I am not frustrated, just moving along and reporting progress

Ok, then I would generally recommend that, unless you have a really good reason to do otherwise, if you are asking for help you should: a) respond to requests like when @ahartikainen asked for output for your CmdStan path and model path; b) if you ignore somebody’s suggestion please say something about why; and c) post the command you ran and the output you got as cut-and-paste from the terminal so that what you tried is clear.