Difference between revisions of "CSEP Minutes 07-25-2018"

From SCECpedia
Jump to navigationJump to search
 
(5 intermediate revisions by the same user not shown)
Line 3: Line 3:
 
'''Participants''': M. Werner, D. Rhoades, W. Savran, P. Maechling, J. Vidale, A. Michael, and D. Jackson
 
'''Participants''': M. Werner, D. Rhoades, W. Savran, P. Maechling, J. Vidale, A. Michael, and D. Jackson
  
# CSEP Workshop SCEC Annual Meeting
+
<h1> CSEP Workshop SCEC Annual Meeting </h1>
  
 
Planned CSEP workshop the Saturday before SCEC AM (09/08/18)
 
Planned CSEP workshop the Saturday before SCEC AM (09/08/18)
  
## Participants
+
<h2> Participants </h2>
  
 
Who should we invite?
 
Who should we invite?
Line 33: Line 33:
 
*** Keith R.
 
*** Keith R.
  
## Workshop Topic Ideas
+
<h2> Workshop Topic Ideas </h2>
  
 
1) Planning CSEP2.0 (>= 50%)
 
1) Planning CSEP2.0 (>= 50%)
Line 70: Line 70:
 
*** Need to agree on the basis of the software development.
 
*** Need to agree on the basis of the software development.
  
# Action items:
 
  
1) Bill
+
 
 +
<h1> Action items: </h1>
 +
 
 +
<h2> Bill </h2>
 
* Put questionnaire responses on the wiki, if people agree to share their responses.
 
* Put questionnaire responses on the wiki, if people agree to share their responses.
 
* Write proposal for technical software developments to collaborate disucssions amongst groups.
 
* Write proposal for technical software developments to collaborate disucssions amongst groups.
 +
** Model outputs should contain hypocenters, origin time, and moment magnitudes.
  
2) Bill & Max
+
<h2> Bill & Max </h2>
 
* Scientific proposal for call next week involving modelers.
 
* Scientific proposal for call next week involving modelers.

Latest revision as of 20:21, 25 July 2018

CSEP Working Group Home Page

Participants: M. Werner, D. Rhoades, W. Savran, P. Maechling, J. Vidale, A. Michael, and D. Jackson

CSEP Workshop SCEC Annual Meeting

Planned CSEP workshop the Saturday before SCEC AM (09/08/18)

Participants

Who should we invite?

  • Conveners
    • Andy Michael
    • Max Werner
    • David Rhoades
    • Toroka (sp?)
    • Tom Jordan
  • Participants
    • USGS
      • Jeanne
      • Kevin
      • Ned
      • Nicholas
      • Andrea
    • New Zealand
      • Matt
    • SCEC
      • Fabio
      • John Y.
      • John V.
      • Bruce S.
      • Jacqui G.
      • Keith R.

Workshop Topic Ideas

1) Planning CSEP2.0 (>= 50%)

  • USGS Modelers
  • International Representatives
    • New Zealand
    • Italy
    • Potsdam
    • Japan
  • Need to account for software development across Potsdam and SCEC.
  • Technical discussion at workshop.

2) CSEP1.0 Legacy issues

  • Present curated CSEP1.0 data along with data set
  • Data availability
  • Publication Plans for CA data set

3) [DJ] Trying to integrate short-term (aftershock) forecasts between forecasting models.

  • How can we answer questions across tectonic settings?
  • Share questionnaires between people doing short-term forecasts.

4) [PM] Testing UCERF3-ETAS against other ETAS varities

  • USGS typically forecasts 1 year.

European RISE proposal

  • Several EU members planning proposal led by Stefan W.
  • Proposal has the goal of advancing operational earthquake forecasting within Europe.
    • Core mission is not necessarily basic science, but also not implementating OEF for Europe.
    • Dozens of EU institutions, spanning seismologists to statisticians to risk communications.
    • Estimating dynamic seismic risk.
    • Key aspect is around earthquake forecasting.
    • Another aspect is model evaluations.
  • Max is the lisason between SCEC and EU Testing Centers.
  • Questions:
    • How do we make sure that we have a flexible system where people can design their own bespoke experiements?
    • How do we internationally make sure the developments are accesssible between testing centers?
      • Communication between groups.
      • Need to agree on the basis of the software development.


Action items:

Bill

  • Put questionnaire responses on the wiki, if people agree to share their responses.
  • Write proposal for technical software developments to collaborate disucssions amongst groups.
    • Model outputs should contain hypocenters, origin time, and moment magnitudes.

Bill & Max

  • Scientific proposal for call next week involving modelers.