# Modular post-processing

**URL:** https://community.epinowcast.org/t/modular-post-processing/38
**Category:** Developers
**Tags:** package-extension
**Created:** [23 August 2022 15:48 UTC](https://community.epinowcast.org/t/modular-post-processing/38 "2022-08-23T15:48:13Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![adrianlison](https://dub1.discourse-cdn.com/flex005/user_avatar/community.epinowcast.org/adrianlison/32/27_2.png) [@adrianlison](https://community.epinowcast.org/u/adrianlison)
#### Post date: [23 August 2022 15:48 UTC](https://community.epinowcast.org/t/modular-post-processing/38/1 "2022-08-23T15:48:13Z")

</div>

Porting the discussion from [here](https://github.com/epiforecasts/epinowcast/discussions/124).

@samabbott wrote:

> We now have a modular system of pre-processing and it would be nice if we could do the same for stan code and postprocessing. Of these modular stan code is the hardest so likely best to focus on modular post-processing. The first step towards this is reviewing the current code with a eye to making it modular and making methods downstream of `epinowcast` infer what to extract (and what is available to extract) from the `epinowcast` object.