# Streamlining of epi modeling tools

**URL:** <https://community.epinowcast.org/t/streamlining-of-epi-modeling-tools/241>\
**Category:** Uncategorized\
**Created:** [14 August 2024 15:31 UTC](https://community.epinowcast.org/t/streamlining-of-epi-modeling-tools/241 "2024-08-14T15:31:18Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [14 August 2024 15:32 UTC](https://community.epinowcast.org/t/streamlining-of-epi-modeling-tools/241/4 "2024-08-14T15:32:33Z")

</div>

@jamesazam replied:

> [@Community Seminar 2024-08-07 - Kaitlyn Johnson - Wastewater modeling to forecast hospital admissions in the US: Challenges and opportunities](https://community.epinowcast.org/t/community-seminar-2024-08-07-kaitlyn-johnson-wastewater-modeling-to-forecast-hospital-admissions-in-the-us-challenges-and-opportunities/237/9):
>
> Yes, exactly. For example, there is a similar conversation happening in EpiNow2 about restructuring the [output class](https://github.com/epiforecasts/EpiNow2/issues/451) and returning the summarised output in a [ready format for use with scoringutils](https://github.com/epiforecasts/EpiNow2/issues/618). Here, scoringutils could dictate the structure of outputs but we must be wary of tightly coupling these tools instead of making them interoperable. See a similar restructuring exercise in [serofoi](https://github.com/epiverse-trace/serofoi/issues/89). Other standardisations could include function and input naming conventions, etc.

---

_[View the full topic](https://community.epinowcast.org/t/streamlining-of-epi-modeling-tools/241)._