<?xml version="1.0" encoding="UTF-8"?>
<rss  xmlns:atom="http://www.w3.org/2005/Atom" 
      xmlns:media="http://search.yahoo.com/mrss/" 
      xmlns:content="http://purl.org/rss/1.0/modules/content/" 
      xmlns:dc="http://purl.org/dc/elements/1.1/" 
      version="2.0">
<channel>
<title>EpiAware</title>
<link>https://epiaware.github.io/news/</link>
<atom:link href="https://epiaware.github.io/news/index.xml" rel="self" type="application/rss+xml"/>
<description>Updates, releases, and writing from the EpiAware project.</description>
<generator>quarto-1.9.38</generator>
<lastBuildDate>Wed, 08 Jul 2026 00:00:00 GMT</lastBuildDate>
<item>
  <title>A composable ecosystem for infectious disease modelling</title>
  <dc:creator>Sam Abbott</dc:creator>
  <link>https://epiaware.github.io/news/posts/hello-epiaware.html</link>
  <description><![CDATA[ 





<p>Real-time infectious disease analysis usually forces a choice between two hard paths. You either chain separate models together, passing point estimates between them and losing the uncertainty along the way, or you write one large model tuned to a single problem that is hard to adapt or reuse.</p>
<p>EpiAware takes a third path. It is a set of small Julia packages that each do one thing — handling censored delays, convolving distributions, composing them — and combine into joint models that propagate uncertainty correctly. The package that ties them together, <a href="../../packages/composableturingidmodels.html">ComposableTuringIDModels.jl</a>, lets you assemble a model from interchangeable infection and observation parts and turns it into a single <a href="https://turinglang.org">Turing</a> model you can simulate from and fit.</p>
<section id="where-it-is-today" class="level2">
<h2 class="anchored" data-anchor-id="where-it-is-today">Where it is today</h2>
<p>The ecosystem is at an early stage. <a href="../../packages/censoreddistributions.html">CensoredDistributions.jl</a> is the most developed and usable today; the joint-modelling and distribution packages are in active development, and some interfaces will change. Each package’s page says how settled it is.</p>
</section>
<section id="get-involved" class="level2">
<h2 class="anchored" data-anchor-id="get-involved">Get involved</h2>
<p>We are actively looking for collaborators — whether you contribute code, documentation, examples, or a modelling problem that composable tools could help with. See <a href="../../get-involved.html">Get involved</a>, or start a conversation on the <a href="https://community.epinowcast.org/">epinowcast forum</a>.</p>


</section>

 ]]></description>
  <category>announcement</category>
  <guid>https://epiaware.github.io/news/posts/hello-epiaware.html</guid>
  <pubDate>Wed, 08 Jul 2026 00:00:00 GMT</pubDate>
</item>
</channel>
</rss>
