[moved to stan-dev]
> On Jun 23, 2016, at 3:04 PM, Andrew Gelman <
gel...@stat.columbia.edu> wrote:
>
> Hey, this is an example of a mistake that would've been caught by my parser!
>
>> On Jun 23, 2016, at 5:39 PM, Andrew Gelman <
gel...@stat.columbia.edu> wrote:
>>
>> Don't do this:
>> sigma2 ~ inv_gamma(0.001,0.001) ;
>>
>> Instead, just put a prior on sigma directly, for example a half-normal or half-Cauchy with peak at 0.
I take it the nagging means you want me to make this my top
priority? I can push everything else down my stack (the top
of which used to be adding random number generators to transformed
data).
Question 1: What should the messages say?
Question 2: Should this be a compiler option (e.g., "--andrew-mode")
or always on?
Question 3: If an option, what do we call it?
Question 4: If not always on, how do we control this?
Question 5: If not always on, do we allow our other message
types to be turned off the same way?
Time estimate:
always on, someone formulates exact messages for me: 1 day
not always on, need to design control, need to fish through
all the interfaces: who knows?
- Bob
P.S. A biggy that's a lot harder to code is catching undefined
variables, which also bites a lot of people.