Split
623f760084
Edit mode system:
- \editmode{1} enables comments + wider margins
- \editmode{0} hides all comments for final output
Comment types (color-coded):
- \splitnote{} (green): General observations, good work
- \splitsuggest{} (yellow): Suggestions to consider
- \splitpolish{} (orange): Needs polish, should fix
- \splitfix{} (red): Must fix, not acceptable
Comments added throughout all sections with substantive feedback
on structure, wording, and Gopen-style improvements.
Also fixed typos: 'ivariant' → 'invariant', 'excess' → 'access'
249 lines
22 KiB
TeX
249 lines
22 KiB
TeX
\relax
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Strong, direct opening. Sets scope immediately.}{i}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid1}{10005341}{44941311}
|
|
\pgfsyspdfmark {pgfid4}{33755687}{44915575}
|
|
\pgfsyspdfmark {pgfid5}{36070152}{44675891}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{yellow!60}{\textcolor {yellow!60}{o}}\ Consider: ``operators'' appears 3x in two sentences. Maybe: ``Based on these procedures and their interpretation of plant conditions, they make critical decisions...''}{i}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid6}{15536702}{41140223}
|
|
\pgfsyspdfmark {pgfid9}{33755687}{40539187}
|
|
\pgfsyspdfmark {pgfid10}{36070152}{40299503}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{orange!50}{\textcolor {orange!50}{o}}\ ``But, reliance'' — the comma after ``But'' is unusual. Either drop it or restructure: ``However, this reliance...'' or ``This reliance, however, has created...''}{i}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid11}{24132805}{40189951}
|
|
\pgfsyspdfmark {pgfid14}{33755687}{26505721}
|
|
\pgfsyspdfmark {pgfid15}{36070152}{26266037}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{yellow!60}{\textcolor {yellow!60}{o}}\ ``are needed that can'' — passive. Try: ``Autonomous control systems must safely manage...''}{i}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid16}{11376844}{36388863}
|
|
\pgfsyspdfmark {pgfid19}{33755687}{13363545}
|
|
\pgfsyspdfmark {pgfid20}{36070152}{13123861}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Clear statement of approach.}{i}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid21}{30785862}{34488319}
|
|
\pgfsyspdfmark {pgfid24}{33755687}{5421997}
|
|
\pgfsyspdfmark {pgfid25}{36070152}{5182313}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Nice parallel structure showing the gap.}{i}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid26}{19909561}{29736959}
|
|
\pgfsyspdfmark {pgfid29}{33755687}{1936899}
|
|
\pgfsyspdfmark {pgfid30}{36070152}{1697215}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{yellow!60}{\textcolor {yellow!60}{o}}\ This paragraph is dense. Consider breaking after the three stages, then a new paragraph for the compositional verification point and Emerson demo.}{i}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid31}{29147912}{16433151}
|
|
\pgfsyspdfmark {pgfid34}{33755687}{-2439489}
|
|
\pgfsyspdfmark {pgfid35}{36070152}{-2679173}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{orange!50}{\textcolor {orange!50}{o}}\ ``can be used for'' — weak. Try: ``...will demonstrate that autonomous control can manage complex nuclear power operations while maintaining safety guarantees.'' Or even stronger: ``...enables autonomous management of complex nuclear power operations with safety guarantees.''}{i}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid36}{21883461}{14532607}
|
|
\pgfsyspdfmark {pgfid39}{33755687}{-14690375}
|
|
\pgfsyspdfmark {pgfid40}{36070152}{-14930059}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Good practical framing — emphasizes accessibility.}{i}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid41}{27551156}{7225343}
|
|
\pgfsyspdfmark {pgfid44}{33755687}{-38528031}
|
|
\pgfsyspdfmark {pgfid45}{36070152}{-38767715}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Strong industrial grounding — the ``platforms they already use'' point is compelling for adoption.}{ii}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid46}{15325447}{39239679}
|
|
\pgfsyspdfmark {pgfid49}{33755687}{39213943}
|
|
\pgfsyspdfmark {pgfid50}{36070152}{38974259}
|
|
\@writefile{toc}{\contentsline {section}{Contents}{iii}{}\protected@file@percent }
|
|
\@writefile{toc}{\contentsline {section}{\numberline {1}Goals and Outcomes}{1}{}\protected@file@percent }
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Clear thesis statement. Gets right to it.}{1}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid51}{30597830}{44563390}
|
|
\pgfsyspdfmark {pgfid54}{33755687}{44537654}
|
|
\pgfsyspdfmark {pgfid55}{36070152}{44297970}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Stakes established immediately — good hook.}{1}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid56}{11072977}{41712574}
|
|
\pgfsyspdfmark {pgfid59}{33755687}{40308378}
|
|
\pgfsyspdfmark {pgfid60}{36070152}{40068694}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{yellow!60}{\textcolor {yellow!60}{o}}\ The ``and'' here joins two distinct issues (autonomy barrier + economics). Consider making the causal link explicit: ``This reliance on human operators not only prevents autonomous control capabilities but also creates...'' or split into two sentences.}{1}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid61}{19272391}{36010942}
|
|
\pgfsyspdfmark {pgfid64}{33755687}{35931990}
|
|
\pgfsyspdfmark {pgfid65}{36070152}{35692306}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{orange!50}{\textcolor {orange!50}{o}}\ ``What is needed is'' — Gopen would call this a weak topic position. The sentence buries the subject. Try: ``Autonomous control systems must safely manage complex operational sequences...'' Puts the actor in the topic position.}{1}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid66}{20791156}{31259582}
|
|
\pgfsyspdfmark {pgfid69}{33755687}{14768204}
|
|
\pgfsyspdfmark {pgfid70}{36070152}{14528520}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Excellent setup of the gap — shows why neither approach alone is sufficient.}{1}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid71}{7117565}{23657406}
|
|
\pgfsyspdfmark {pgfid74}{33755687}{-3868824}
|
|
\pgfsyspdfmark {pgfid75}{36070152}{-4108508}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Hypothesis is clear and testable.}{1}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid76}{16705748}{18906046}
|
|
\pgfsyspdfmark {pgfid79}{33755687}{-10771970}
|
|
\pgfsyspdfmark {pgfid80}{36070152}{-11011654}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{yellow!60}{\textcolor {yellow!60}{o}}\ This qualifications paragraph feels orphaned here. It's important context but reads as an afterthought. Consider integrating it into the approach paragraph (``...demonstrated on Emerson hardware through our partnership with the Cyber Energy Center'') or moving to a ``Why This Will Succeed'' framing later.}{1}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid81}{30785862}{14154686}
|
|
\pgfsyspdfmark {pgfid84}{33755687}{-14109956}
|
|
\pgfsyspdfmark {pgfid85}{36070152}{-14349640}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ ``cold shutdown through criticality to power operation'' — concrete and impressive scope.}{2}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid86}{22235661}{34488319}
|
|
\pgfsyspdfmark {pgfid89}{33755687}{34462583}
|
|
\pgfsyspdfmark {pgfid90}{36070152}{34222899}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Clear ``what's new'' statement.}{2}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid91}{27214487}{28884991}
|
|
\pgfsyspdfmark {pgfid94}{33755687}{25629745}
|
|
\pgfsyspdfmark {pgfid95}{36070152}{25390061}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Strong closing — ties technical work to real-world impact and economic necessity.}{2}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid96}{18188851}{21282815}
|
|
\pgfsyspdfmark {pgfid99}{33755687}{21257079}
|
|
\pgfsyspdfmark {pgfid100}{36070152}{21017395}
|
|
\citation{NUREG-0899,10CFR50.34}
|
|
\citation{10CFR55.59}
|
|
\citation{WRPS.Description,gentillon_westinghouse_1999}
|
|
\@writefile{toc}{\contentsline {section}{\numberline {2}State of the Art and Limits of Current Practice}{3}{}\protected@file@percent }
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Good roadmap — tells reader exactly what's coming.}{3}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid101}{13036184}{40762302}
|
|
\pgfsyspdfmark {pgfid104}{33755687}{40736566}
|
|
\pgfsyspdfmark {pgfid105}{36070152}{40496882}
|
|
\@writefile{toc}{\contentsline {subsection}{\numberline {2.1}Current Reactor Procedures and Operation}{3}{}\protected@file@percent }
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{yellow!60}{\textcolor {yellow!60}{o}}\ This paragraph is doing a lot. Consider splitting: first paragraph on the hierarchy and compliance, second on the lack of formal verification. The ``No mathematical proof exists...'' sentence is powerful and deserves emphasis.}{3}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid106}{17724053}{25831016}
|
|
\pgfsyspdfmark {pgfid109}{33755687}{25805280}
|
|
\pgfsyspdfmark {pgfid110}{36070152}{25565596}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{orange!50}{\textcolor {orange!50}{o}}\ This repeats the ``No mathematical proof exists...'' sentence almost verbatim from the paragraph above. Either cut it from the paragraph or from the LIMITATION box.}{3}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid111}{27570105}{19179112}
|
|
\pgfsyspdfmark {pgfid114}{33755687}{7168252}
|
|
\pgfsyspdfmark {pgfid115}{36070152}{6928568}
|
|
\citation{operator_statistics}
|
|
\citation{10CFR55}
|
|
\citation{10CFR50.54}
|
|
\citation{Kemeny1979}
|
|
\citation{WNA2020}
|
|
\citation{hogberg_root_2013}
|
|
\citation{zhang_analysis_2025}
|
|
\citation{Kiniry2024}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ This is the key insight — the hybrid nature is already there, just not formally verified.}{4}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid116}{29333260}{45891583}
|
|
\pgfsyspdfmark {pgfid119}{33755687}{45865847}
|
|
\pgfsyspdfmark {pgfid120}{36070152}{45626163}
|
|
\@writefile{toc}{\contentsline {subsection}{\numberline {2.2}Human Factors in Nuclear Accidents}{4}{}\protected@file@percent }
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Strong thesis for this subsection.}{4}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid121}{27354523}{35711657}
|
|
\pgfsyspdfmark {pgfid124}{33755687}{35685921}
|
|
\pgfsyspdfmark {pgfid125}{36070152}{35446237}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ ``the person responsible for reactor safety is often the root cause of failures'' — devastating summary. Very effective.}{4}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid126}{24580098}{26208937}
|
|
\pgfsyspdfmark {pgfid129}{33755687}{26183201}
|
|
\pgfsyspdfmark {pgfid130}{36070152}{25943517}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Strong empirical grounding. The Chinese plant data is a nice addition — shows this isn't just a Western regulatory perspective.}{4}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid131}{11564802}{17656489}
|
|
\pgfsyspdfmark {pgfid134}{33755687}{16604393}
|
|
\pgfsyspdfmark {pgfid135}{36070152}{16364709}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Well-stated. The ``four decades'' point drives it home.}{4}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid136}{24906501}{13855401}
|
|
\pgfsyspdfmark {pgfid139}{33755687}{5097685}
|
|
\pgfsyspdfmark {pgfid140}{36070152}{4858001}
|
|
\@writefile{toc}{\contentsline {subsection}{\numberline {2.3}Formal Methods}{4}{}\protected@file@percent }
|
|
\@writefile{toc}{\contentsline {subsubsection}{\numberline {2.3.1}HARDENS}{4}{}\protected@file@percent }
|
|
\citation{Kiniry2024}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Good technical depth on HARDENS toolchain.}{5}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid141}{22013224}{31637503}
|
|
\pgfsyspdfmark {pgfid144}{33755687}{31611767}
|
|
\pgfsyspdfmark {pgfid145}{36070152}{31372083}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Clear articulation of the gap your work fills.}{5}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid146}{23378487}{22134783}
|
|
\pgfsyspdfmark {pgfid149}{33755687}{22109047}
|
|
\pgfsyspdfmark {pgfid150}{36070152}{21869363}
|
|
\@writefile{toc}{\contentsline {subsubsection}{\numberline {2.3.2}Sequent Calculus and Differential Dynamic Logic}{6}{}\protected@file@percent }
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{red!40}{\textcolor {red!40}{o}}\ Typo: ``ivariant'' should be ``invariant''}{6}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid151}{19651738}{35711657}
|
|
\pgfsyspdfmark {pgfid154}{33755687}{35685921}
|
|
\pgfsyspdfmark {pgfid155}{36070152}{35446237}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{yellow!60}{\textcolor {yellow!60}{o}}\ Consider adding a concrete example here — ``For instance, a system with N modes and M continuous state variables...'' to give readers a sense of the scaling problem.}{6}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid156}{11704839}{28109481}
|
|
\pgfsyspdfmark {pgfid159}{33755687}{28083745}
|
|
\pgfsyspdfmark {pgfid160}{36070152}{27844061}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{orange!50}{\textcolor {orange!50}{o}}\ ``but are far from a complete methodology to design systems with'' — awkward ending preposition. Try: ``but remain far from a complete design methodology'' or ``but do not yet constitute a complete design methodology.''}{6}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid161}{22592676}{26208937}
|
|
\pgfsyspdfmark {pgfid164}{33755687}{13903167}
|
|
\pgfsyspdfmark {pgfid165}{36070152}{13663483}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Your comment here is spot-on. You should add a LIMITATION box: \textit {Differential dynamic logic has been used for post-hoc analysis of existing systems, not for the constructive design of autonomous controllers.} This is exactly the gap you're filling — you're doing synthesis, not just verification.}{6}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid166}{17744690}{21847466}
|
|
\citation{HANDBOOK ON HYBRID SYSTEMS}
|
|
\@writefile{toc}{\contentsline {section}{\numberline {3}Research Approach}{7}{}\protected@file@percent }
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{orange!50}{\textcolor {orange!50}{o}}\ Missing space before ``Our}{7}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid167}{10825988}{33160126}
|
|
\pgfsyspdfmark {pgfid170}{33755687}{33134390}
|
|
\pgfsyspdfmark {pgfid171}{36070152}{32894706}
|
|
\@writefile{lof}{\contentsline {figure}{\numberline {1}{\ignorespaces Simplified hybrid automaton for reactor startup. Each discrete state $q_i$ has associated continuous dynamics $f_i$. Guard conditions on transitions (e.g., $T_{avg} > T_{min}$) are predicates over continuous state. Invariant violations ($\neg Inv_i$) trigger transitions to the SCRAM state. The operational level manages discrete transitions; the tactical level executes continuous control within each mode.}}{8}{}\protected@file@percent }
|
|
\newlabel{fig:hybrid_automaton}{{1}{8}{Research Approach}{figure.1}{}}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ This is your key insight — the novelty is compositional, not component-level.}{8}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid172}{21716682}{23775512}
|
|
\pgfsyspdfmark {pgfid175}{33755687}{23749776}
|
|
\pgfsyspdfmark {pgfid176}{36070152}{23510092}
|
|
\@writefile{toc}{\contentsline {subsection}{\numberline {3.1}System Requirements, Specifications, and Discrete Controllers}{8}{}\protected@file@percent }
|
|
\@writefile{lof}{\contentsline {figure}{\numberline {2}{\ignorespaces Control scope hierarchy in nuclear power operations. Strategic control (long-term planning) remains with human management. HAHACS addresses the operational level (discrete mode switching) and tactical level (continuous control within modes), which together form a hybrid control system.}}{9}{}\protected@file@percent }
|
|
\newlabel{fig:strat_op_tact}{{2}{9}{System Requirements, Specifications, and Discrete Controllers}{figure.2}{}}
|
|
\@writefile{toc}{\contentsline {subsection}{\numberline {3.2}Continuous Control Modes}{11}{}\protected@file@percent }
|
|
\citation{MANYUS THESIS}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ This three-mode taxonomy is elegant — maps verification tools to control objectives cleanly.}{12}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid179}{16597916}{12329325}
|
|
\pgfsyspdfmark {pgfid182}{33755687}{12303589}
|
|
\pgfsyspdfmark {pgfid183}{36070152}{12063905}
|
|
\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.2.1}Transitory Modes}{12}{}\protected@file@percent }
|
|
\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.2.2}Stabilizing Modes}{13}{}\protected@file@percent }
|
|
\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.2.3}Expulsory Modes}{14}{}\protected@file@percent }
|
|
\@writefile{toc}{\contentsline {subsection}{\numberline {3.3}Industrial Implementation}{15}{}\protected@file@percent }
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{red!40}{\textcolor {red!40}{o}}\ Typo: ``excess should be ``access}{15}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid184}{16922734}{5204649}
|
|
\pgfsyspdfmark {pgfid187}{33755687}{5178913}
|
|
\pgfsyspdfmark {pgfid188}{36070152}{4939229}
|
|
\@writefile{toc}{\contentsline {section}{\numberline {4}Metrics for Success}{17}{}\protected@file@percent }
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ TRL as primary metric is smart — speaks industry language.}{17}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid189}{26292290}{42662846}
|
|
\pgfsyspdfmark {pgfid192}{33755687}{42637110}
|
|
\pgfsyspdfmark {pgfid193}{36070152}{42397426}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Good framing — explains why other metrics are insufficient.}{17}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid194}{20090191}{35060670}
|
|
\pgfsyspdfmark {pgfid197}{33755687}{35034934}
|
|
\pgfsyspdfmark {pgfid198}{36070152}{34795250}
|
|
\@writefile{toc}{\contentsline {paragraph}{TRL 3 \textit {Critical Function and Proof of Concept}}{17}{}\protected@file@percent }
|
|
\@writefile{toc}{\contentsline {paragraph}{TRL 4 \textit {Laboratory Testing of Integrated Components}}{17}{}\protected@file@percent }
|
|
\@writefile{toc}{\contentsline {paragraph}{TRL 5 \textit {Laboratory Testing in Relevant Environment}}{18}{}\protected@file@percent }
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{yellow!60}{\textcolor {yellow!60}{o}}\ Consider noting why graded responses are out of scope — is it time, complexity, or scope creep? Brief justification helps.}{18}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid199}{9102038}{33199444}
|
|
\pgfsyspdfmark {pgfid202}{33755687}{33173708}
|
|
\pgfsyspdfmark {pgfid203}{36070152}{32934024}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Clear success criteria. Committee will know exactly what ``done'' looks like.}{18}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid204}{12395286}{18945364}
|
|
\pgfsyspdfmark {pgfid207}{33755687}{18919628}
|
|
\pgfsyspdfmark {pgfid208}{36070152}{18679944}
|
|
\@writefile{toc}{\contentsline {section}{\numberline {5}Risks and Contingencies}{19}{}\protected@file@percent }
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Honest acknowledgment of risks with clear contingencies — committee will appreciate this.}{19}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid209}{20770641}{44563390}
|
|
\pgfsyspdfmark {pgfid212}{33755687}{44537654}
|
|
\pgfsyspdfmark {pgfid213}{36070152}{44297970}
|
|
\@writefile{toc}{\contentsline {subsection}{\numberline {5.1}Computational Tractability of Synthesis}{19}{}\protected@file@percent }
|
|
\@writefile{toc}{\contentsline {subsection}{\numberline {5.2}Discrete-Continuous Interface Formalization}{19}{}\protected@file@percent }
|
|
\@writefile{toc}{\contentsline {subsection}{\numberline {5.3}Procedure Formalization Completeness}{21}{}\protected@file@percent }
|
|
\citation{eia_lcoe_2022}
|
|
\citation{eesi_datacenter_2024}
|
|
\citation{eia_lcoe_2022}
|
|
\@writefile{toc}{\contentsline {section}{\numberline {6}Broader Impacts}{23}{}\protected@file@percent }
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ ``If it works here, it works anywhere — strong closing argument.}{24}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid214}{24213455}{31637503}
|
|
\pgfsyspdfmark {pgfid217}{33755687}{31611767}
|
|
\pgfsyspdfmark {pgfid218}{36070152}{31372083}
|
|
\bibstyle{ieeetr}
|
|
\bibdata{references}
|
|
\@writefile{toc}{\contentsline {section}{\numberline {7}Schedule, Milestones, and Deliverables}{25}{}\protected@file@percent }
|
|
\gtt@chartextrasize{0}{164.1287pt}
|
|
\@writefile{lof}{\contentsline {figure}{\numberline {3}{\ignorespaces Project schedule showing major research thrusts, milestones (orange row), and publications (green row). Red diamonds indicate completion points. Overlapping bars indicate parallel work where appropriate.}}{25}{}\protected@file@percent }
|
|
\newlabel{fig:gantt}{{3}{25}{Schedule, Milestones, and Deliverables}{figure.3}{}}
|
|
\@writefile{toc}{\contentsline {subsection}{\numberline {7.1}Milestones and Deliverables}{25}{}\protected@file@percent }
|
|
\bibcite{NUREG-0899}{1}
|
|
\bibcite{10CFR50.34}{2}
|
|
\bibcite{10CFR55.59}{3}
|
|
\bibcite{WRPS.Description}{4}
|
|
\bibcite{gentillon_westinghouse_1999}{5}
|
|
\bibcite{operator_statistics}{6}
|
|
\bibcite{10CFR55}{7}
|
|
\bibcite{10CFR50.54}{8}
|
|
\bibcite{Kemeny1979}{9}
|
|
\bibcite{WNA2020}{10}
|
|
\bibcite{hogberg_root_2013}{11}
|
|
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Clear timeline with publication targets — shows you have a plan.}{26}{}\protected@file@percent }
|
|
\pgfsyspdfmark {pgfid220}{15051800}{39239679}
|
|
\pgfsyspdfmark {pgfid223}{33755687}{39213943}
|
|
\pgfsyspdfmark {pgfid224}{36070152}{38974259}
|
|
\@writefile{toc}{\contentsline {section}{References}{26}{}\protected@file@percent }
|
|
\bibcite{zhang_analysis_2025}{12}
|
|
\bibcite{Kiniry2024}{13}
|
|
\bibcite{eia_lcoe_2022}{14}
|
|
\bibcite{eesi_datacenter_2024}{15}
|
|
\gdef \@abspage@last{31}
|