Staff Priorities - Scott: Difference between revisions

Latest revision as of 17:56, 1 February 2018

Modify CyberShake to work on RSQSim ruptures
- Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
CyberShake training
Update CyberShake study wiki pages to point to SQLite files
Create wiki page for CyberShake RSQSim, and upload sample seismograms

@@ Line 1: / Line 1: @@
-== Yesterday ==
+== Current Items ==
-*Resolved proxy issue on Blue Waters
+*Modify CyberShake to work on RSQSim ruptures
-*Issue with Blue Waters GridFTP alias; using workaround for now
+**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
-*CyberShake calls
+*CyberShake training
-*HighF call
+*Update CyberShake study wiki pages to point to SQLite files
-*Submitted 1 Hz post-processing workflow on Blue Waters
+*Create wiki page for CyberShake RSQSim, and upload sample seismograms
-*0.5 Hz 200m GPU code running very slowly on BW; emailed Efecan
-*Replied to Omar and Nicole (NCSA science author)
-*Downloaded PEER data, ran through RotD100 code, doesn't match reference results
-== Today ==
+== Project Backlog ==
-*Finish up workflow on Titan
+*Run CyberShake post-processing on RSQSim events, once DB is populated
-*Pick a few CyberShake sites to calculate 300 km cutoff for
+*Produce candidate site list for Bay Area CyberShake
-*Monitor 1 Hz post-processing on BW
+*Investigate improved load-balancing for DirectSynth SGT handlers
-*Make recommended changes from Efecan
+*Experiment with OMP parallelization for post-processing
-*Try to get alternative RotD100 code
-== Blocked ==
-*No
-== Follow-ups ==
-*No
-== Areas of Responsibilities ==
-* CyberShake
-* Broadband CyberShake
-* Code migration