Staff Priorities - Patrick: Difference between revisions

From SCECpedia
Jump to navigationJump to search
Maechlin (talk | contribs)
11,776 edits
Created page with 'UCVM-CyberShake UCVM Framework CVM-H Broadband use on OSG Glide-in for Kraken with Mats File fix for Po’s calculation so Po can run on ALCF: Rupture generator capability in wor…'
 
Maechlin (talk | contribs)
11,776 edits
No edit summary
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
UCVM-CyberShake
== Broadband Platform ==
UCVM Framework
# Random Seed in High Frequency
CVM-H
## Determine where UCSB random number generation
Broadband use on OSG
## Simplify two scattering.dat files used in Broadband toolbox code
Glide-in for Kraken with Mats
## Give user a way to set random seed without editing file
File fix for Po’s calculation so Po can run on ALCF:
# Two distributions of Broadband hanging wall inputs and results (Graves and Kottke)
Rupture generator capability in workflow based on ucerf 2.0:
# Minimal software installation distribution for clusters
# Modification to use gnu build tools
# Single acceptance tests can be run easily
# Broadband batch tools tested, distributed, documented
# Optional Patch collection
# Distribution tracking
## Check for updates capability
## Download counter for software
## Optional registration announcement
 
== UCVM ==
# Check for update capabilities
# Download counter
# optional registration tool
# Release announcement
 
== Areas of Responsibility ==
*UCVM-CyberShake
*UCVM Framework
*CVM-H
*Broadband use on OSG
*Glide-in for Kraken with Mats
*File fix for Po’s calculation so Po can run on ALCF:
*Rupture generator capability in workflow based on ucerf 2.0:

Latest revision as of 20:31, 10 February 2012

Broadband Platform

  1. Random Seed in High Frequency
    1. Determine where UCSB random number generation
    2. Simplify two scattering.dat files used in Broadband toolbox code
    3. Give user a way to set random seed without editing file
  2. Two distributions of Broadband hanging wall inputs and results (Graves and Kottke)
  3. Minimal software installation distribution for clusters
  4. Modification to use gnu build tools
  5. Single acceptance tests can be run easily
  6. Broadband batch tools tested, distributed, documented
  7. Optional Patch collection
  8. Distribution tracking
    1. Check for updates capability
    2. Download counter for software
    3. Optional registration announcement

UCVM

  1. Check for update capabilities
  2. Download counter
  3. optional registration tool
  4. Release announcement

Areas of Responsibility

  • UCVM-CyberShake
  • UCVM Framework
  • CVM-H
  • Broadband use on OSG
  • Glide-in for Kraken with Mats
  • File fix for Po’s calculation so Po can run on ALCF:
  • Rupture generator capability in workflow based on ucerf 2.0:
Retrieved from "https://strike.scec.org/index.php?title=Staff_Priorities_-_Patrick&oldid=4217"