<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ready4 – Status - unreleased</title>
    <link>/tags/status-unreleased/</link>
    <description>Recent content in Status - unreleased on ready4</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Thu, 05 Jan 2017 00:00:00 +0000</lastBuildDate>
    
	  <atom:link href="/tags/status-unreleased/index.xml" rel="self" type="application/rss+xml" />
    
    
      
        
      
    
    
    <item>
      <title>Docs: Modules pipeline</title>
      <link>/docs/model/modules/pipeline/</link>
      <pubDate>Thu, 05 Jan 2017 00:00:00 +0000</pubDate>
      
      <guid>/docs/model/modules/pipeline/</guid>
      <description>
        
        
        
      </description>
    </item>
    
    <item>
      <title>Docs: Pipeline of people modules</title>
      <link>/docs/model/modules/pipeline/pipeline-people/</link>
      <pubDate>Thu, 05 Jan 2017 00:00:00 +0000</pubDate>
      
      <guid>/docs/model/modules/pipeline/pipeline-people/</guid>
      <description>
        
        
        &lt;p&gt;Our current pipeline of modules for modelling people is principally focused on developing tools for:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;creating synthetic household datasets from multiple longitudinal datasets of varying structure, including modules specifically designed to streamline wrangling data from the HILDA and LSAC datasets (both from Australia); and&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;implementing agent based model simulations.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;A significant amount of work has already been completed on both projects and initial &lt;a href=&#34;/docs/software/status/development-releases/&#34;&gt;development releases&lt;/a&gt; of each, along with one scientific manuscript, are anticipated in late 2023 / early 2024.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: Pipeline of places modules</title>
      <link>/docs/model/modules/pipeline/pipeline-places/</link>
      <pubDate>Thu, 05 Jan 2017 00:00:00 +0000</pubDate>
      
      <guid>/docs/model/modules/pipeline/pipeline-places/</guid>
      <description>
        
        
        &lt;p&gt;Our current pipeline of modules for modelling places extends the &lt;a href=&#34;https://ready4-dev.github.io/vicinity/&#34;&gt;vicinity&lt;/a&gt; and &lt;a href=&#34;https://ready4-dev.github.io/aus/&#34;&gt;aus&lt;/a&gt; libraries to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;predict prevalence and incidence by area; and&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;provide a user-interface (i.e. software to implement an updated version of the currently deprecated &lt;a href=&#34;/docs/model/analyses/decision-aids/springtides-app/&#34;&gt;Springtides app&lt;/a&gt;).&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Although unreleased, the source code for the above projects has been used to &lt;a href=&#34;/blog/2021/02/18/modelling-the-mental-health-impacts-of-covid-19/&#34;&gt;generate analysis during the early phase of the COVID-19 pandemic&lt;/a&gt;. Initial &lt;a href=&#34;/docs/software/status/development-releases/&#34;&gt;development releases&lt;/a&gt; of places module &lt;a href=&#34;/docs/software/libraries/&#34;&gt;libraries&lt;/a&gt;, along with an updated app, are anticipated in the second half of 2023.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: Pipeline of platforms modules</title>
      <link>/docs/model/modules/pipeline/pipeline-platforms/</link>
      <pubDate>Thu, 05 Jan 2017 00:00:00 +0000</pubDate>
      
      <guid>/docs/model/modules/pipeline/pipeline-platforms/</guid>
      <description>
        
        
        &lt;p&gt;Our current pipeline of modules for modelling platforms includes code for implementing:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;a discrete event simulation of primary mental health services for young people;&lt;/li&gt;
&lt;li&gt;a simple cohort model of early psychosis services; and&lt;/li&gt;
&lt;li&gt;a blended (systems dynamics / discrete event simulation) model for optimising eligibility and referral policies across multiple services.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The first two of the above models are currently implemented in R and are sufficiently advanced to produce exploratory analysis. However, neither are adequately documented or tested and need to be redeveloped as ready4 model modules and re-validated prior to &lt;a href=&#34;/docs/software/status/development-releases/&#34;&gt;development releases&lt;/a&gt;.  The optimisation model was implemented in Java and was populated with toy data - this will require more substantial development prior to public release.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: Unreleased code</title>
      <link>/docs/software/status/unreleased/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/software/status/unreleased/</guid>
      <description>
        
        
        &lt;p&gt;Currently, a new ready4 software project initiated by the ready4 core team will by default be made public as a pre-release version in the &lt;a href=&#34;https://github.com/ready4-dev&#34;&gt;ready4 GitHub organisation&lt;/a&gt;. However, there are some important exceptions. Principally, these exceptions relate to code that we authored in the initial phase of ready4&amp;rsquo;s development to which some or all of the following apply:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;the code is highly unstable because it has not been (fully) updated to account to major changes implemented in core dependencies;&lt;/li&gt;
&lt;li&gt;the code uses outdated naming conventions and is potentially confusing when used in conjunction with other elements of the ready4 suite; and/or&lt;/li&gt;
&lt;li&gt;the code repository has yet to be cleansed of artefacts that are not yet appropriate for public dissemination (e.g. renders of draft scientific manuscripts).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Depending on which of the above issues apply to a code repository, that repository will either be:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;a private repository (not accessible to anyone outside the core development team); or&lt;/li&gt;
&lt;li&gt;a public repository stored in a location other than the ready4 GitHub organisation.&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
  </channel>
</rss>
