https://strike.scec.org/scecwiki/index.php?action=history&feed=atom&title=Production_Run_Readiness_ReviewProduction Run Readiness Review - Revision history2026-04-24T21:17:35ZRevision history for this page on the wikiMediaWiki 1.34.2https://strike.scec.org/scecwiki/index.php?title=Production_Run_Readiness_Review&diff=5951&oldid=prevMaechlin: Created page with 'Prior to production research simulations, we conduct scientific and computational readiness reviews. Outlines of the material we cover during each review is shown below Each pro…'2012-10-01T19:59:21Z<p>Created page with 'Prior to production research simulations, we conduct scientific and computational readiness reviews. Outlines of the material we cover during each review is shown below Each pro…'</p>
<p><b>New page</b></p><div>Prior to production research simulations, we conduct scientific and computational readiness reviews. Outlines of the material we cover during each review is shown below<br />
<br />
Each production run should be defined as [[Study]] meaning that we have sufficient detail to identify total output files. When we think we are ready to start study, we conduct two reviews:<br />
<br />
== Scientific Readiness Review ==<br />
#Goal of study:<br />
*Expected outcome<br />
*Statement of why this is a priority<br />
#Problem statements Inputs:<br />
*ERF<br />
*CVM<br />
*Rupture variations (rupture generator)<br />
*Frequencies of simulation<br />
*SGT codes<br />
*Sites to be calculated<br />
#Outputs:<br />
*Identification of expect outputs<br />
*Types of outputs files and results<br />
*Number of each<br />
*Size of expected<br />
*Existing partial results<br />
#Verification/Validation Work:<br />
*Evidence the computational system produces correct answer<br />
5. Reproducibly of results:<br />
• What we have done to implement reproducibility of results<br />
• What is required to re-run this study 1 year from now?<br />
<br />
6. Expected analysis:<br />
• What analysis will be conducted with results. <br />
• Who will help with scientific analysis<br />
<br />
7. Metrics Review<br />
• What metrics will be calculated?<br />
<br />
8. Open Issues/Risks Analysis<br />
<br />
== Computational Readiness Review ==<br />
<br />
1. Computational goal for study<br />
• Description deliverable outputs.<br />
<br />
2. Total Input files and parameters<br />
• Input files and sizes<br />
<br />
3. Total output files:<br />
• Expect output files in number and size<br />
• Identification of files that will be archived<br />
<br />
4. Study archives both files and database:<br />
• Where will file-based archives be located. How much storage is needed. Confirm we have storage?<br />
• Where will database-based archives be located. What current storage. What is expected new storage needed.<br />
• How long will they be saved?<br />
<br />
5. User Access To Results<br />
• How will users access database archives<br />
• How will users access file-based archives<br />
<br />
5. Description of expected computing environment. <br />
• What system<br />
• What version of Pegasus<br />
• Description of codes to be used<br />
• Description of workflow environment<br />
• What versions of PMC<br />
• What tagged version of CyberShake codebase<br />
<br />
6. Estimated computational requirements for study<br />
• Do we have computing time available?<br />
• Comparison of available computing time to estimated computing needed<br />
<br />
7. Study start and duration estimates<br />
<br />
8. Personnel involved in running study.<br />
<br />
9. Reproducibility of results<br />
<br />
10. Metrics Review<br />
<br />
• Computational metrics that will be collected<br />
<br />
11. Open Issues/Risk Analysis</div>Maechlin