Staff Priorities - Scott: Difference between revisions

From SCECpedia
Jump to navigationJump to search
Scottcal (talk | contribs)
No edit summary
Scottcal (talk | contribs)
No edit summary
Line 1: Line 1:
== Yesterday ==
== Current Items ==
*Respond to Mats's questionnaire about data integrity for Pegasus
*CyberShake training
*Review 2017 IHPCSS proposal
*Update CyberShake_Site_Ruptures entries on focal to remove NULL distance values
*Produce writeup on 2017 IHPCSS mentoring activities
*Modify CyberShake to work on RSQSim ruptures
*Create and email link to images of Vp, Vs, Rho without cutoffs
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Register and use ALCF token
**Modify DirectSynth code to operate on RSQSim SRFs


== Today ==
== Project Backlog ==
*Database migration
*Produce candidate site list for Bay Area CyberShake
 
*Synthesize seismograms using sample RSQSim SRFs
*Work on CyberShake data training guide
 
*Add SRF-based synthesis to DirectSynth if not already supported
 
*Work on regenerating b-maps for GMPEs with new (2nd crossing) Z2.5 map.
 
*Reproduce Feng's results using ABF
 
*Run tests with SBSM, USC, PAS with v5.2.3.  Checked on BBP and found v5.2.2; try to determine difference.
 
== Blocked ==
*No
 
== Follow-ups ==
*No
 
== Areas of Responsibilities ==
* CyberShake
* Broadband CyberShake
* Code migration

Revision as of 23:21, 23 January 2018

Current Items

  • CyberShake training
  • Update CyberShake_Site_Ruptures entries on focal to remove NULL distance values
  • Modify CyberShake to work on RSQSim ruptures
    • Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
    • Modify DirectSynth code to operate on RSQSim SRFs

Project Backlog

  • Produce candidate site list for Bay Area CyberShake
  • Synthesize seismograms using sample RSQSim SRFs