generated quantities is shoehorned into exactly same constraint as all other information - the problem is that all information from a draw - sampler state, params, and generated quantities variables - are output using exactly the same c++ output stream and the precision is set on the output stream, not the individual items.
the solution is finer-grained outputs. there’s been some discussion around this -
**_Static, Logger-Style Output:_**
**Functional and Technical Specifications**
**_Motivation_**
This is a proposal for static, logger-style output to handle data and message output from the Stan services. The goal is to make it easier to do three things
1. Add a new type of data output to an existing service.
1. Add a new algorithm, service, model method, etc.
1. Write handlers in the interfaces.
The basis of the refactor will be to have a single, statically accessible output handler used for all output communication to interfaces.
**_Functional Specification_**
The proposal is to use a singleton to route all output in the style of traditional loggers.
**Types of output**
show original
Rather than hijacking the original topic , I’m opening a new one to discuss a radical rethinking of how we can handle output that @seantalts and I have been discussing. We brought it up briefly during this week’s Stan meeting, but I thought I’d write up what we’ve been thinking about.
Comments obviously welcome—that’s why it’s up here!
Current services output
The interfaces talk to Stan through the Stan services methods, which are in the stan-dev/stan repo in directory src/stan/services. Ther…