Mitzi Morris

> I would suggest grabbing the values after the var_context is used to extract the values and the results fed through write_array. We can't read from the var_context twice because...

in CmdStan `command.hpp` this isn't hooked up to anything. https://github.com/stan-dev/cmdstan/blob/fd7d8faf88a791d078500cc5fd7458a8d68f7b17/src/cmdstan/command.hpp#L154

I understand that it needs to be stored somewhere. the question is where and how to label it so that it's easily interpretable.

> These all seem non-optimal. exactly. which is why Aki's hack is needed (for now) - documented it in the Stan User's Guide, section 9.5.4 - https://mc-stan.org/docs/2_24/cmdstan-guide/mcmc-config.html#initializing-parameters

thanks for reporting. I think you're right that there was discussion about whether or not this is a bug or feature. (it's a bug). at this point, stanc2 compiler isn't...

wecome Ishvana and Anika! happy to help answer your questions! just curious - where are you taking this swe class and for what program?

this issue is the result of a suggestion made during code review: >This pattern is everywhere, and while it's simple, I'd rather not see this test everywhere. Can we just...

further on, in the code review discussion - https://github.com/stan-dev/stan/pull/2570#discussion_r201151286 - the reviewer had related request: [future request] > Our loggers should just take these, as in: ``` logger.info()

what is the current proposal? initial proposal was this: > In Stan, update the writers so that it prints something not OS dependent. That's this file: src/stan/callbacks/stream_writer.hpp unassigned myself per...

The current implementations are: https://github.com/stan-dev/stan/blob/develop/src/stan/callbacks/logger.hpp https://github.com/stan-dev/stan/blob/develop/src/stan/callbacks/stream_logger.hpp As used in CmdStan, the calling function instantiates a logger where debug and info messages are sent to std::cout and the rest are sent...