This issue can be closed when the following items have been included in temoa-uiuc:

• Config file that runs monte carlo for temoa
• Results figures

This issue can be closed when a synthetic history is produced that

• has the same statistics as a typical history
• reflects physical reality

For wind data I am waiting on Mike Marquissee to fulfill a data request. One possibility is also to use wind speed data, produce a synthetic history for that variable, and calculate the power.

This folder will contain abstract for the ANS Student conference 2020.

This issue can be closed when a folder is created and populated with the ANS latex templates.

This issue can be closed when all publications are neatly organized into a publications folder.

This issue can be closed when the following items have been updated:

• Figures (replace typical figures with typical/synthetic figures).
• Introduction/Methodology (anywhere that says I'm not working on Steam...)
• Update the simplifying assumption from MWe baseload power to MWth "baseload" (this way the reactor can supply steam OR electricity).
• Add the assumption that steam be delivered at 325 PSI (this replaces the steam produced by gas turbines).

This issue can be closed when a reasonable explanation for the measured data has been established.

I'm not sure why this hasn't been done previously. But a .gitignore file should be added.
This issue can be closed when a .gitignore file has been added that ignores:

• pycache
• ipynb-checkpoints
• latex built-files
• sqlite files
• temoa built files
• pytest-cache
  Possibly others. But for now this is the minimum.

This issue can be closed when a notebook is added that creates specific figures for the optimal sizing publication.

This issue can be closed when a PR is merged that does the following:

• Adds hospital data to the EIA market analysis functions
• Creates an ipynb that displays graphs of the data similar to the education_market_analysis.ipynb
• Updates test functions to match

This issue can be closed when a typical time history of APP's generation has been produced.

This issue can be closed when a SQL database that represents the UIUC embedded grid has been created.

The x-axis labels created by data_parser.py are squished when the dataframe is too long. This issue can be closed when a fix is added to handle dataframes of larger sizes.

Attached is the draft of the ANS Abstract after Gavin's review.

main.pdf

The functions in temoa-uiuc/data_parser.py need to have associated unit tests.

This is a good first issue for new students/researchers.

For guidance on writing unit tests, please see "Effective Computation in Physics by Huff, Scopatz."

This issue can be closed when:

• test_data_parser.py has been added to the tests folder in pride/ (this folder may need to be created, depending on the status of Issue #103).
• Each function in data_parser.py has an appropriate unit test, covering edge and corner cases if applicable.
• All tests pass by running pytest in the top level of the repository.

This issue can be closed when a PR is made that contains synthetic steam production.

(I'm being careless, it is steam demand. At UIUC the demand and the production are identical because APP fulfills all of the demand).

The current carbon limits are actually shifted by a few years and should be corrected.
This issue can be closed when the 0x_uiuc.sql databases are updated to reflect the correct carbon limits based on the iCAP document.

This issue can be closed when a document or jupyter notebook has been created to answer the following questions (with detailed steps on how to replicate the answers):

• Determine the total fuel demand in gallons of gasoline equivalent for each technology type.

• What is the CO2 equivalent per gallon-gasoline-equivalent. Note: It's important that this an equivalent because emissions might consist of more than just CO2. E.g. 1 ton of CH4 released might be the same as 3 tons of CO2. So report 3 tons of CO2eq.

• Determine the cost of each type of fuel

• Determine conversion rates for each type of fuel (e.g. 1 kWh(e) = 10 gallons-gasoline)

• Document to replicate answers and sources cited.

Vehicles should be sorted by fuel type (E85, Diesel, Unleaded, Lithium-ion, H2 fuel-cell).

edit1: for clarity

edit 2: updates goal

dotson.pdf

This issue can be closed with a PR that handles the comments from the Huff review, including items from the writing checklist that should be reviewed again:

• Other misused/overused words include: code, input, output, different, value, amount, model.
• clunky nouns -> spunky verbs (progression, expression --> progress, express)
• reduce vague words (important, methodological)
• get rid of extraneous prepositions (the meeting happened on monday -> the meeting happened monday) (they agreed that it was true -> they agreed it was true)
• get rid of passive voice (is/was/are/were/be/been/am + past tense verb), replace with active voice
• use strong verbs (use sparingly: is, are, was, were, be, been, am)
• avoid turning verbs into nouns ("obtain estimates of" -> "estimates"; "provides a description of" -> "describes") (management of power systems -> power systems management, to the task of net load prediction -> to predict net load, the task of net load forecasting -> to forecast net load)
• don't bury the verb (keep the predicate close to the subject at the beginning of the sentence)
• Always use isotopic notation like $^{239}Pu$. Never $Pu-239$ or plutonium-239.
• A phrase of the form ion of is probably clearer as ion. (For example, convert "calculation of velocity" to "velocity calculation".)
• Cite all software. Review the principles and try CiteAs if necessary.
• Refer to software consistently by name.

Additional Table and Figure Checklist:

• When referring to figures by their number, use Figure 1 and Table 1. They should be capitalized and not abbreviated (not fig. 1 or figure 1.)

Additional Math Comments

• define all variables, with units. If unitless, indicate that this is the case $[-]$.
• Variables should be defined in the align environment as well, not buried in paragraphs.
  Here’s an example of an equation:

The line is defined as
\begin{align}
y&=mx + b
\intertext{where}
y&= \mbox{ height of the line, also known as rise [m]}\nonumber\\
m&= \mbox{ slope [-]}\nonumber\\
x&=\mbox{ independent parameter, known as run [m]}\nonumber\\
b&= \mbox{ y intercept [m].}
\end{align}

This issue can be closed when

• a jupyter notebook containing preliminary carbon price analysis has been added
• a folder containing a skeleton paper for carbon-pricing has been added

This issue can be closed when a script has been created that can

• parse and graph activity by sector
• parse and graph capacity by sector
• parse and graph emissions by sector
• parse and graph total emissions

This issue can be closed once

• Files required for temoa analysis are in a temoa-uiuc folder

This issue can be closed when a synthetic history is produced that

• has the same statistics as a typical history
• reflects physical reality

It is possible that

1. This data should not be modeled using an ARMA
2. More parameters are needed to capture the correct behavior
3. Another method of generating these series should be devised

This issue can be closed when

• mass flow rate of steam has been converted to thermal energy requirements
• sythetic histories have been generated

This issue can be closed when a RAVEN input file is created that will generate synthetic histories for APP generation.

There are tests in this repo, but they aren't run in CI for each PR. This issue can be closed with a merged PR (and adjusted repository settings) that runs the tests for all PRs.

@samgdotson can do this, or could perhaps guide @datw0258 , @nsryan2 , or @Dayvis7 as they figure out how to.

At the moment, optimal-sizing-pres doesn't compile.
It is missing the file Methods.tex.
The file is called methods.tex.
This issue can be closed when the main .tex file calls methods.tex instead of Methods.tex

This issue can be closed when

• the README.md file includes instructions for users to access EIA data
• publicly shared links are included in README.md.
• a description of the analysis is added (e.g. This notebook analyzes data from the EIA about electricity production from the education sector.)

This issue can be closed when the analysis done in Google Colab has been moved Jupyter Notebooks.

This issue can be closed when an abstract for the ANS Winter meeting has been uploaded and submitted to ANS.

This issue can be closed when

• An Elsevier template has been added to the repository
• Basic information has been replaced

This issue can be closed when

• a .sql database has been added to the repository that includes a transportation sector for UIUC
• using data about gasoline/diesel demand. All transportation demand should be in a "gasoline energy equivalent."

The file should be called 0x_uiuc.sql and have an associated config file called run_scenario0x.txt, similar to the other scenarios in temoa-uiuc.

Transportation Demand

All of the data analysis for transportation demand has been done in fuel-analysis, hydro-requirement, and uiuc_transportation_demand. This should be enough information to update the TEMOA model.

Guidance:

1. Add an experimental branch in your forked repository

git checkout -b iss43

2. Each subsequent TEMOA model should build on the previous one (in most cases). Thus, copy the most recent model, in this case scenario04.

cp data_files/04_uiuc.sql data_files/05_uiuc.sql
cp data_files/run_scenario04.txt data_files/run_scenario04.txt

3. Edit the configuration file, run_scenario05.txt and change the name of the input database to data_files/05_uiuc.sqlite

   • Also change the scenario name, and the output file name.

4. In Snakefile comment out the "All Scenarios" block, and uncomment the "Experimental Scenario" block. Replace the name in experimental scenario with the name of the model you're working on.

5. Edit the .sql database to add a new sector, transportation. (You can visually check the model at model.temoacloud.com)

6. Run the model by executing

source activate temoa-py3
snakemake --cores=4

7. If the results look appropriate, add the experimental scenario to all scenarios in the snakefile (maybe run it again with all files) and make a pull request.

This issue can be closed when Temoa config files are added for

• Business-as-usual
• Scenario 1
• Scenario 2
• Scenario 3
• Scenario 3, with uncertainty and sentitivity analysis

This issue can be closed when a reasonable model for the operating costs of a micro-reactor on this campus has been established [$/kwh]

This issue can be closed when I have calculated the amount of energy that can be stored (in MWh).

This issue can be closed when a PR updates hydrogen-production-pres presentation.

This issue can be closed with a PR that updates the reservoir computing paper in a manner that handles the review comments below.

Reviewer 1

• In Fig. 3, it appears that there are two local minima (rho = 0.9, noise = 10^-4; rho = 1.3, noise = 10^-2) which are both close to the global minimum. How did you select between these two? Since the two input parameters vary quite a bit between these two, I suspect that the output of the model using the other minimum would be significantly different, too.
• What more quantitative metrics could be used to evaluate the quality of forecasts? How many Lyapunov times are useful before some accuracy threshold is reached?

Reviewer 2

• Interesting work. Might help to clearly state the objectives of this initial phase of research towards the beginning of the paper.

Reviewer 3

• The summary is well written but needs some discussion on verification of the proposed methodology.
• What is the basis for selection of hyperparameters and some sensitivity and parametric analysis needs to be done in order to ensure confidence in results.
• How dependent is the methodology and results on the training length and network size ?

Submit

• A suitably revised summary must be uploaded no later than August 17 into the same system that you submitted your original paper (https://epsr.ans.org/meeting/?m=308). If your revised summary is not received by the deadline date, your original summary will be published as is.

This issue can be closed when

• Clearer assumptions
• Clear conclusions
• back up slides for anticipated questions

This issue can be closed when presentation and abstract folders have been renamed something more appropriate than ans-abs or pres. So that everyone can see what it contains.

Create a branch the ANS presentation, supply the basic outline of the presentation.

This issue can be closed when a complete draft of the abstract has been submitted.

This issue can be closed when the following calculation is added:

• how much CO2 won't be emitted if the fleets (UIUC and MTD) switched to H2

Currently, the figures in this notebook look like this:

This issue can be closed when a PR fixes the labels.
Some possibilities are making the bars wider or rotating the labels slightly.

This issue can be closed when

• the README.md file has been updated to reflect changes to the goals of the repository. The original scenarios are no longer accurate.

This issue can be closed when

• the emissions_plot() function in data_parser.py includes a method to graph the iCAP goals.

This issue can be closed when the make_increasing() function in data_funcs.py has added cases for

• sort = True, strict = False
• sort = False, strict = False
• sort = True, strict = True

and appropriate tests have been added for each.

The next step for this methodology is to use RAVEN to generate synthetic time histories (training data for an reduced order model).

Read the section in the user guide on trainARMA

This issue can be closed when a RAVEN input file for generating typical time histories has been created.

This issue can be closed when a 50% draft has been

• added to the publications folder
• reviewed by @katyhuff, @datw0258, @robfairh

Recently received actual wind power data from Mike Marquissee.
This issue can be closed when that data has been analyzed and a typical and series of synthetic histories have been generated.

This issue can be closed when a file called railsplitter-data.csv has been uploaded to Box (or sent to Sam) that has two columns Date and Time and Buyer's Share where the latter refers to the actual MWh delivered to the UIUC campus for a given hour by Rail Splitter Wind Farm.