Difference between revisions of "Broadband Platform 15 3 0"

From SCECpedia
Jump to navigationJump to search
Line 14: Line 14:
  
 
* Integrate updated method from UCSB (#289)
 
* Integrate updated method from UCSB (#289)
 +
* Use real station distances (#207)
 
* Match module works with user-provided seismograms (#265)
 
* Match module works with user-provided seismograms (#265)
  
Line 28: Line 29:
 
==== Week 2/16 ====
 
==== Week 2/16 ====
  
 +
* Run test simulations for modelers
 
* Update cluster scripts (#268)
 
* Update cluster scripts (#268)
 
* Improve BBP command-line interface (#291)
 
* Improve BBP command-line interface (#291)
 
* Review test coverage (#128)
 
* Review test coverage (#128)
* Code Freeze (2/20)
 
  
 
==== Week 2/23 ====
 
==== Week 2/23 ====
Line 37: Line 38:
 
* BBP First simulations (#269)
 
* BBP First simulations (#269)
 
* Documentation
 
* Documentation
 +
* Code Freeze (2/26)
 +
* Start West Part A & B validation suite for all methods 2/27
  
 
==== Week 3/2 ====
 
==== Week 3/2 ====

Revision as of 22:14, 30 January 2015

Release Plan for BBP 15.3.0

Week 1/26

  • Finalize Intel compiler dependency removal (#227, #228)
  • Run BBP on Mac OS X (#44)
  • SRC/STL files on outdata (#277)
  • SEED on outdata html file (#276)
  • XML parsing problem (#285)
  • Division by zero issue (#284)

Week 2/2

  • Integrate updated method from UCSB (#289)
  • Use real station distances (#207)
  • Match module works with user-provided seismograms (#265)

Week 2/9

  • Version number on XML file (#200)
  • Modify validation packages directory structure (#283)
  • Fix Header in RD50 files (#270)
  • Always use BBP_DATA_DIR (#158)
  • Remove unused codes and data files (#287)
  • Better handle errors/ctrl-C (#113)
  • Update BBP distribution directory structure (#290)

Week 2/16

  • Run test simulations for modelers
  • Update cluster scripts (#268)
  • Improve BBP command-line interface (#291)
  • Review test coverage (#128)

Week 2/23

  • BBP First simulations (#269)
  • Documentation
  • Code Freeze (2/26)
  • Start West Part A & B validation suite for all methods 2/27

Week 3/2

  • Make RC1 available to group for testing
  • Collect feedback

Week 3/9

  • Code Review 3/9
  • Make RC2 available to group

Week 3/16

  • Collect feedback from group
  • Fix eventual issues

Week 3/23

  • Generate Virtual Image
  • Generate Tar files
  • Update online documentation

Week 3/30

  • Post Distribution on Hypocenter
  • Update Release Notes
  • Write Release Announcement
  • Email Release Announcement