Skip to content

Commit

Permalink
deploy: 63c5e1a
Browse files Browse the repository at this point in the history
  • Loading branch information
kennedy-mindermann committed Apr 10, 2024
1 parent 80e704d commit 9195e3a
Show file tree
Hide file tree
Showing 7 changed files with 4 additions and 3 deletions.
Binary file modified .doctrees/environment.pickle
Binary file not shown.
Binary file modified .doctrees/faq.doctree
Binary file not shown.
Binary file modified .doctrees/model_information.doctree
Binary file not shown.
Binary file modified .doctrees/sources.doctree
Binary file not shown.
3 changes: 2 additions & 1 deletion _sources/faq.md.txt
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,8 @@ If you'd like to reduce the model solve time, consider making some of the follow
## How often are updates made to ReEDS?
Every year we target June 1 for the bulk of model changes to be completed, which allows us to meet the hard deadline for having a working, updated version of the model by June 30. We typically make minor updates to the model over the summer and tag a final version for that year in August or September. This version is then used to produce the Standard Scenarios and Cambium data products.

Additionally, changes are made throughout the year and a new version is created and published roughly every month. You can find current and past ReEDS versions here: {{ github_releases_url }}
Additionally, changes are made throughout the year and a new version is created and published roughly every month. You can find current and past ReEDS versions here: {{ '[ReEDS-2.0 Releases]({})'.format(github_releases_url) }}


If you would like to run ReEDS with a previous version, you can either download the source code directly or check out that version using the tag.

Expand Down
2 changes: 1 addition & 1 deletion faq.html
Original file line number Diff line number Diff line change
Expand Up @@ -151,7 +151,7 @@ <h2>Is there a way to reduce solve time?<a class="headerlink" href="#is-there-a-
<section id="how-often-are-updates-made-to-reeds">
<h2>How often are updates made to ReEDS?<a class="headerlink" href="#how-often-are-updates-made-to-reeds" title="Link to this heading"></a></h2>
<p>Every year we target June 1 for the bulk of model changes to be completed, which allows us to meet the hard deadline for having a working, updated version of the model by June 30. We typically make minor updates to the model over the summer and tag a final version for that year in August or September. This version is then used to produce the Standard Scenarios and Cambium data products.</p>
<p>Additionally, changes are made throughout the year and a new version is created and published roughly every month. You can find current and past ReEDS versions here: https://github.com/NREL/ReEDS-2.0/releases</p>
<p>Additionally, changes are made throughout the year and a new version is created and published roughly every month. You can find current and past ReEDS versions here: <a class="reference external" href="https://github.com/NREL/ReEDS-2.0/releases">ReEDS-2.0 Releases</a></p>
<p>If you would like to run ReEDS with a previous version, you can either download the source code directly or check out that version using the tag.</p>
<p>To check out a previous version using its tag, you can run the following command from your command line or terminal (ensure you have the main branch of the repo checked out):</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">git</span> <span class="n">checkout</span> <span class="n">tags</span><span class="o">/</span><span class="p">{</span><span class="n">version</span> <span class="n">number</span><span class="p">}</span>
Expand Down
2 changes: 1 addition & 1 deletion searchindex.js

Large diffs are not rendered by default.

0 comments on commit 9195e3a

Please sign in to comment.