# Proposal for consolidated output

**URL:** <https://discourse.mc-stan.org/t/proposal-for-consolidated-output/4263>\
**Category:** Developers\
**Tags:** features\
**Created:** [May 21, 2018, 12:41pm UTC](https://discourse.mc-stan.org/t/proposal-for-consolidated-output/4263 "2018-05-21T12:41:52Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![sakrejda](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.mc-stan.org/sakrejda/32/845_2.png) [@sakrejda](https://discourse.mc-stan.org/u/sakrejda)\
**Post date:** [May 25, 2018, 10:21am UTC](https://discourse.mc-stan.org/t/proposal-for-consolidated-output/4263/10 "2018-05-25T10:21:15Z")

</div>

> [@Bob\_Carpenter](#):
>
> I’m going to expand this thread a bit to generalize the idea to consolidated inputs across the board. We can move this to a separate issue if others don’t think this is appropriate here. I don’t think it’ll open a can of worms, as I think the high-level path forward is pretty clear on this.

Putting on the forum moderator hat for a sec.:

1. The writers/loggers/interrupts _are_ different because the interfaces have to specify a whole set of behaviors when building a “relay” for the loggers whereas for most other items the interface just supplies a few int/double values.
2. I agree the high-level discussion of the builder pattern is on-topic here, we should share a builder pattern.
3. Detailed discussion about which args belong in which bundle should be in its own thread or (ideally) a design doc on the Wiki
4. `var_context` also brings up a host of unrelated issues (including performance IIRC) and belongs in the `var_context` thread: [Var\_context, what do we want from it?](http://discourse.mc-stan.org/t/var-context-what-do-we-want-from-it/3665)

- Removed the slightly derogatory ‘bike-shedding’, I didn’t mean it like that.

---

_[View the full topic](https://discourse.mc-stan.org/t/proposal-for-consolidated-output/4263)._