numerical_exp_report.pdf

This issue can be closed when the comments in the above attached review have been merged into the repository. Please excuse the handwriting (was missing my stylus).

A checklist exists for writing properly...
http://arfc.github.io/manual/guides/writing/checklist/

This issue can be closed when the following items have been checked in the DDCA July 2019 report.

• Run a spell checker.
• The Oxford comma appears in ("lions, tigers, and bears.")
• Do not use the word "where" unless referring to a location (try "such that" or "in which").
• Articles such as "a" "the" "some" "any" and "each" 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
• 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.

This issue can be closed when I have reviewed @robfairh's draft of the final report plots.

This issue can be closed with @robfairh reviews the new quarterly report draft and pings katyhuff for final review.
report.pdf

This issue can be closed by merging a PR that adds the coversheet to the July 2019 report.
There is a template for the ARFC report coversheet here .

Leave the report number as a draft report number for now.

My comments are included in this PDF.
ddcareport-gwencomments.pdf

This issue can be closed when @robfairh provides a revised final report addressing these comments.

There is both a directory called "final" and one called "final-report."

(Neither, in fact, is the project's final report, which is distinct from the report satifying the final milestone and has not yet been written.)

I have made a PR that changes the name of "final-report" to uiuc-arfc-2019-05.

But -- I can't figure out the purpose or proper fate of the directory called "final". This issue can be closed when someone:

• explains what the deal is.
• and/or a pull request is merged which changes the name of that directory or deletes it entirely.

This issue can be closed after @katyhuff reviews the summer transition scenarios report.
report.pdf

Currently, the analytical solution table lists No. of source facilities decommissioned. However the values denote the facilities decommissioned due to end of lifetime. The table should reflect what the Insitution does, not what is happening in the entire simulation.

This Issue can be closed once @katyhuff reviews first draft of Numerical Experiments Report Draft 1

Currently the report lists initial demand and growth rate.
Since we want to move away from that nomenclature and want stepwise functions to define our demand,
plots should be included as well as the equations in the report to help the reader understand the test parameters.

This issue can be closed when @gwenchee reviews the second draft of the final report.
The .pdf can be found here:
report.pdf

The report should add the demonstrations of d3ploy capabilities using the transition scenarios.

Addressed by #25

The .pdf can we found here:
report.pdf

This issue can be closed when @robfairh updates the report.

Submit a draft with all the important results for the transition scenarios.

This is issue can be closed when @FlanFlanagan @robfairh and I put together the first draft of the final report. It is split:

Intro: @FlanFlanagan
Method: @FlanFlanagan
Demonstration: @gwenchee
Transition Scenarios: @robfairh

This issue can be closed after @katyhuff reviews the d3ploy summer transition report:
report.pdf. Should i tag Sonata and Roberto to read it now or only after your review?

An 'intuitive' way of labeling the tests should be implemented.

Currently,

A - source only
B - source & reactor
subsequent letters reflect more sophisticated supply chains

1 - Test only deployment capability
2 - Test only decommissioning capability
3 - Test mixed capability.

However, the status quo presents a problem when moving forward, and is a bit confusing.

This issue can be closed once a better labeling is implemented.

See scribbles in this pdf for to-do recommendations:
no_numerical_exp_report.pdf

This issue can be closed when a PR handling these suggestions has been merged.

This issue can be closed after @sonatav2 and @robfairh read the summer transition report. In the report, I candidly added some comments and recommendations for setting up the large transition scenario. In the conclusions section, I made a recommendation for what @sonatav2 could work on while @robfairh is in Sweden taking the nuclear waste course. Feel free to reach out to me if y'all need any help :)

report.pdf

Also, could someone merge #22 if you are satisfied with the report.

This issue can be closed when @katyhuff has reviewed the report. The .pdf can be found here:
report.pdf