arfc/2020-fairhurst-hydrogen-production

This repository holds data analysis of the hydrogen required by the UI fleet and MTD fleet to become carbon free.

2020-fairhurst-hydrogen-production

This repository holds:

• data of the fuel consumed by the MTD and UI fleet.
• analysis of the hydrogen required by those fleet to become carbon free.
• information of different methods to produce hydrogen.

2020-fairhurst-hydrogen-production's Issues

Zotero entries missing metadata

As noted in #3 the zotero entries for this are missing lots of key metadata.

Please review zotero standards and process here.
This issue can be closed when zotero, the bib file, and the refs in the document have been updated to include authors, years, and titles for all references.

Add document with more information about iodine-sulfur cycle

This issue can be closed when more information about the iodine-sulfur thermochemical cycle for producing hydrogen is added to the repository. This information should also contain more accurate data about the energy (both thermal and electric) demanded by the process.

Add 2020 ANS Annual meeting presentation

This issue can be closed when a first draft of the presentation is added to the repository.

Add duck curve analysis

This issue can be closed when an analysis of the duck-curve phenomenon likelihood is carried out on the UIUCs grid.

Add UIUC fleet fuel consumption and its respective analysis

This issue can be closed when the following tasks are completed:

• Add to the repo the fuel consumption annual data of UIUC Facilities and Services fleet.
• Add a script to analyze such data.

Acks currently don't follow the Acknowledgements guidelines.

The acknowledgements currently state:
"This work was supported by an NRC grant and the Dept. of Nuclear, Plasma, and Radiological Engineering UIUC."

The "how to acknowledge" document has been a little out of date until recently. Sorry! Because of the combined funding amongst the three authors, the acknowledgements should read:

"Roberto E. Fairhurst Agosta and Prof. Huff are supported by the Nuclear Regulatory Commission (NRC) Faculty Development Program (award NRC-HQ-84-14-G-0054 Program B). Samuel G. Dotson is supported by the NRC Graduate Fellowship Program. Prof. Huff is also supported by the Blue Waters sustained-petascale computing project supported by the National Science Foundation (awards OCI-0725070 and ACI-1238993) and the state of Illinois, the DOE ARPA-E MEITNER Program (award DE-AR0000983), the DOE H2@Scale Program (award ), and the International Institute for Carbon Neutral Energy Research (WPI-I2CNER), sponsored by the Japanese Ministry of Education, Culture, Sports, Science and Technology."

Concept Clarity Correction.

I think this sentence fundamentally misrepresents the issue:
"Although using hydrogen does not produce CO2, some of the hydrogen production methods still do it."

The hydrogen production methods that produce CO2 (e.g. methane reforming) capture that CO2 on site. This is not the source of CO2 that is of concern.

ALL hydrogen production methods are only as carbon-free as the source of energy they rely on (electric, heat, or both) to drive the process. That is where the main CO2 issue exists in a hydrogen economy, and that is where nuclear comes in.

This issue can be closed with a pull request to the paper that clarifies this.

Create abstract for ANS Student Conference 2020

This issue can be closed when a first draft of the abstract is added to the repo.

Add document with general information about H2 applications

This issue can be closed when a document containing general information about the use of hydrogen in different industrial sectors is added to the repository.
For example, the document should contain information about:

• Nitrogen fertilizers
• Syngas
• Hydrogen buses

Apply Writing Checklist

All documents should be reviewed in the context of the writing checklist before technical review. This issue can be closed when the writing checklist below has been applied to your document.

• Run a spell checker.
• The Oxford comma must appears in lists ("lions, tigers, and bears.")
• Do not use the word "where" unless referring to a location (try "such that" or "in which").
• Do not use the word "when" unless referring to a time (try "if" instead).
• Only use "large" when referring to size.
• Use of "very" suggests that a cooler word exists.
• Other misused/overused words include: code, input, output, different, value, amount, model.
• Articles such as "a" "the" "some" "any" and "each" must appear where necessary.
• All subjects match the plurality of their verbs ( no: "Apples is tasty" yes: "Apples are tasty")
• Avoid run-on sentences.
• clunky nouns -> spunky verbs (progression, expression --> progress, express)
• reduce vague words (important, methodologic)
• reduce acronyms / jargon
• expand all acronyms on first use (rely on the acros.tex file and glossaries package to automate this)
• get rid of unnecessary prepositional phrases -- author clearing throat (It can be shown that)
• get rid of extraneous adverbs (very, really, quite, basically, generally)
• get rid of there are / there is
• turn negatives to positives (she was not often right -> she was usually wrong)
• 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")
• don't bury the verb (keep the predicate close to the subject at the beginning of the sentence)
• data is plural (the data are critical)
• compare to (point out similarities between different things) vs. compared with (point out differences between similar things)
• punctuation helps you to vary your sentence structure
• Power to separate in increasing power: comma, colon, dash, parentheses, semicolon, period
• In increasing order of formality: dash, parentheses, all of the others. Don't overdo it with the dash and parentheses
• semicolon: connects two independent clauses. OR used to separate when the items in the list contain internal punctuation.
• use a colon to introduce a list, quote, explanation, conclusion, or amplification
• if there's a list in a sentence, it shouldn't come before the colon
• use a dash to insert something in the middle of the sentence. Don't overuse it.
• Always use isotopic notation like $^{239}Pu$. Never $Pu-239$ or plutonium-239.
• Elemental symbols (Ni, Li, Na, Pu) are capitalized, but their names are not (nickel, lithium, sodium, plutonium).
• A phrase of the form <verb>ion of <noun> is probably clearer as <noun> <verb>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:

• The text should refer to all tables and figures.
• 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.)
• In tables, align all columns of numbers such that the decimals line up.
• In a single column, all values should probably have the same number of significant digits.
• Give units for each numerical column.
• A table should have only 3 horizontal lines (no vertical lines and no more than 3.)

Additional Math Comments:

• define all variables, with units. If unitless, indicate that this is the case $[-]$.
• subscripts should be brief and can be avoided with common notation. For example, $\dot{m}$ is better than $m_f$ which is superior to $m_{flow}$.
• variable names should be symbols rather than words m is better than mass and \ksi is better than one_time_use_variable.
• The notation $3.0\times10^12$ is preferred over $3e12$.
• Equations should be part of a sentence.
• Equations should be in the align environment. Align them at the = sign.
• Variables should be defined in the align environment as well, not buried in paragraphs.

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}

Add document with more information about electrolysis

This issue can be closed when more information about electrolysis for producing hydrogen is added to the repository. This information should also contain more accurate data about the energy (both thermal and electric) demanded by the process.

"The same report estimates"

In the abstract, section 2.3 : "The same report estimates" is out of place, because no report has been discussed. I recognize you are referring to reference 6, but to use "The same" in this way, there must be an antecedent to which "same" refers.

This issue can be closed with a PR that corrects this sentence.

Add UIUC fuel consumption analysis

This issue can be closed when the .tex file adds the fuel consumption analysis for UIUC fleet.

Add document with more information about steam methane reforming

This issue can be closed when more information about steam methane reforming for producing hydrogen is added to the repository. This information should also contain more accurate data about the energy (both thermal and electric) demanded by the process.

More details regarding MicroReactor requirement

This paragraph appears in the current version.

"Both fleets combined would consume 2240.8 kg/day of H2. A micro-reactor feeding a iodine-sulfur thermochemical cycle would need 10 MWth of power to meet that daily average demand of hydrogen."

But, it seems that the hydrogen production methods will have very different energy requirements, and different splits between thermal and electricity energy. Much, much more detail in this paragraph is warranted. As is, it reads like a guesstimate.

(also, for grammatical purposes, the sentence should read "...a micro-reactor feeding an iodine-sulfur... ")

This issue can be closed with a PR that contains much more analysis regarding the size and operation of a nuclear micro-reactor appropriate for supporting the H2 needs of these fleets for various hydrogen production processes detailed in the preceding paragraphs.