Difference between revisions of "CME Office Hours"

From SCECpedia
Jump to navigationJump to search
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
== 11 November 2011 ==
 
== 11 November 2011 ==
  
 +
*PetaSHA3 Project News Items for 11 Nov 2011:
 +
**Update INCITE 2012 allocation plan
 +
**INCITE 2011 status report due
 +
**SC11 activities and discussions (week of 14 Nov - 18 Nov)
 +
**Geoinformatics Proposal Planning (due 13 Jan 2012)
 +
**SCEC4 Computational Science Milestone development
 +
**Fall AGU 2011 group activities
 +
**TACC SU Transfer
 +
**Migration of Po's kernel codes to USC HPCC
  
PetaSHA3 Project News Items for 11 Nov 2011:
+
*CyberShake 3.0 Development
*Update INCITE 2012 allocation plan
+
**1Hz UCERF2.0 extended ERF
*INCITE 2011 status report due
+
**Update on 1Hz Reciprocity code development
*SC11 activities and discussions (week of 14 Nov - 18 Nov)
 
- Geoinformatics Proposal Planning (due 13 Jan 2012)
 
- SCEC4 Computational Science Milestone development
 
- Fall AGU 2011 group activities
 
- TACC SU Transfer
 
- Migration of Po's kernel codes to USC HPCC
 
  
CyberShake 3.0 Development
+
*Follow-ups
- 1Hz UCERF2.0 extended ERF
+
**Appropriate Use of Challenger
- Update on 1Hz Reciprocity code development
+
**Fault-to-Fault rupture in UCERF3.0 and rupture generators
  
 
== Related Links ==
 
== Related Links ==
 
*[[CyberShake]]
 
*[[CyberShake]]

Latest revision as of 18:31, 11 November 2011

11 November 2011

  • PetaSHA3 Project News Items for 11 Nov 2011:
    • Update INCITE 2012 allocation plan
    • INCITE 2011 status report due
    • SC11 activities and discussions (week of 14 Nov - 18 Nov)
    • Geoinformatics Proposal Planning (due 13 Jan 2012)
    • SCEC4 Computational Science Milestone development
    • Fall AGU 2011 group activities
    • TACC SU Transfer
    • Migration of Po's kernel codes to USC HPCC
  • CyberShake 3.0 Development
    • 1Hz UCERF2.0 extended ERF
    • Update on 1Hz Reciprocity code development
  • Follow-ups
    • Appropriate Use of Challenger
    • Fault-to-Fault rupture in UCERF3.0 and rupture generators

Related Links