# 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:** 3

<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/3 "2024-08-14T15:32:09Z")

</div>

@kejohnson9 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/8):
>
> On the call, I asked if we could employ the [tidymodels](https://www.tidymodels.org/) approach where the community has [developed guidelines for developing models](https://tidymodels.github.io/model-implementation-principles/). I think this is a really great point, and I completely agree with your assessment that taking the time now to streamline these would have a huge impact going forward. As someone relatively new to this, I would say it would also be really helpful because it would remove some of these decisions about interface/formatting inputs and outputs that we face as developer…

---

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