Staff Priorities - Scott: Difference between revisions

From SCECpedia
Jump to navigationJump to search
← Older editNewer edit →
Scottcal (talk | contribs)
8,097 edits
No edit summary
Scottcal (talk | contribs)
8,097 edits
No edit summary
Line 7: Line 7:


== Today ==
== Today ==
*Run USC site on Blue Waters and Titan with Study 15.4 parameters, compare hazard curves and a few time series
*Check on USC Study 15.4 verification run on Titan
*Verify smoothing in workflow produces correct results
*Check on s001 run on Titan
*Something funky with cleanup jobs - shouldn't be running as gridftp jobs.  Turned off cleanup on Titan for now.
*Change legend on seismogram plots
*Pull northern seismogram to make sure NT is large enough
*Put new study ID in db


*Check cleanup test
*Make spreadsheet comparing models, with identifiers, inputs, and relevant motivations
*Run same site on Titan as BW
*Make spreadsheet with computational stats, metrics to compare size and performance
*Consider running all PP on BW
*Create GP07/GP10/GP14 comparison plots
*Compare seismograms with BW vs Study 15.4 test
*Create hazard maps with same basemap and same color scale
*Start on computational section


*Check software stack on Cori
*Check on CyberShake on Cori after Wed
*Review UCVM paper
*Propose experiments on Google doc
*Create outline for meeting with Tom
 
*Get blurb added to website with timeframe for mentoring call
*Pull out into doc the questions we asked on last year's application, email to group


== Blocked ==
== Blocked ==

Revision as of 22:38, 10 February 2017

Yesterday

  • Respond to Mats's questionnaire about data integrity for Pegasus
  • Review 2017 IHPCSS proposal
  • Produce writeup on 2017 IHPCSS mentoring activities
  • Create and email link to images of Vp, Vs, Rho without cutoffs
  • Register and use ALCF token

Today

  • Check on USC Study 15.4 verification run on Titan
  • Check on s001 run on Titan
  • Change legend on seismogram plots
  • Pull northern seismogram to make sure NT is large enough
  • Put new study ID in db
  • Make spreadsheet comparing models, with identifiers, inputs, and relevant motivations
  • Make spreadsheet with computational stats, metrics to compare size and performance
  • Create GP07/GP10/GP14 comparison plots
  • Create hazard maps with same basemap and same color scale
  • Start on computational section
  • Check on CyberShake on Cori after Wed
  • Propose experiments on Google doc
  • Get blurb added to website with timeframe for mentoring call
  • Pull out into doc the questions we asked on last year's application, email to group

Blocked

  • No

Follow-ups

  • No

Areas of Responsibilities

  • CyberShake
  • Broadband CyberShake
  • Code migration
Retrieved from "https://strike.scec.org/index.php?title=Staff_Priorities_-_Scott&oldid=18165"