Difference between revisions of "Broadband Platform 15 3 0"

From SCECpedia
Jump to navigationJump to search
Line 26: Line 26:
 
* Better handle errors/ctrl-C (#113) - 1 day
 
* Better handle errors/ctrl-C (#113) - 1 day
 
* Update BBP distribution directory structure (#290) - <strike>2 days</strike> 1 day
 
* Update BBP distribution directory structure (#290) - <strike>2 days</strike> 1 day
* Show missing velocity models when selecting validation event (#275)
+
* <strike>Show missing velocity models when selecting validation event (#275)</strike>
  
 
==== Week 2/20 ====
 
==== Week 2/20 ====

Revision as of 22:20, 17 February 2015

Release Plan for BBP 15.3.0

Week 1/30

  • Finalize Intel compiler dependency removal (#227, #228)
  • SRC/STL files on outdata (#277)
  • SEED on outdata html file (#276)
  • XML parsing problem (#285)

Week 2/6

  • Run BBP on Mac OS X (#44) - 2 days1 day
  • Integrate updated method from UCSB (#289) - 3 day 1 day
  • Modify validation packages directory structure (#283) - 1 day
  • Always use BBP_DATA_DIR (#158) - 1 day

Week 2/13

  • Use real station distances (#207) - 1 day
  • Division by zero issue (#284) - 1 day
  • Match module works with user-provided seismograms (#265) - 1 day
  • Version number on XML file (#200) - 1 day
  • Fix Header in RD50 files (#270) - 1 day
  • Remove unused codes and data files (#287) - 1 day
  • Better handle errors/ctrl-C (#113) - 1 day
  • Update BBP distribution directory structure (#290) - 2 days 1 day
  • Show missing velocity models when selecting validation event (#275)

Week 2/20

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

Week 2/27

  • Code Freeze for Modelers (2/23)
  • BBP First simulations (#269) - 2 days
  • Documentation - 2 days
    • BBP 15.3.0 wiki page
    • Release Notes
    • Mac OS X installation Guide
    • BBP 15.3.0 Users' Guide
  • Code Freeze for SCEC (2/26)
  • Start West Part A & B validation suite for all methods 2/27

Week 3/6

  • Make RC1 available to group for testing
  • Collect feedback

Week 3/13

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

Week 3/20

  • Collect feedback from group
  • Fix eventual issues

Week 3/27

  • Rerun Part-A and Part-B West Validation
  • Organize both public and private wiki
  • Clean-up hypocenter
  • Generate Virtual Image
  • Generate Tar files
  • Update online documentation

Week 3/31

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