BBP Release Steps

From SCECpedia
Revision as of 17:25, 4 June 2019 by Fsilva (talk | contribs) (Created page with "= Steps For Releasing Broadband Platform = These are the steps needed for making a Broadband Platform release. === Code Freeze === The first step for a BBP release is to co...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

Steps For Releasing Broadband Platform

These are the steps needed for making a Broadband Platform release.

Code Freeze

The first step for a BBP release is to collect the latest codes from all science teams. Ideally, each science team will have reviewed their results and signed off on their method before the code freeze. This will avoid surprises and delays later in the release process.

  • Announce code freeze date
  • Collect code and parameter changes
  • Run simulations as needed
    • Single realizations
      • Useful to make sure codes work
    • Cluster testing
      • Useful to explore different realizations, create validation sets
  • Share results with science teams
  • Obtain approval from each science team

Science Review

These are the steps for a science review of the BBP:

  • Make sure cluster has latest versions of everything, use 'diff -r' to make sure source distribution, bbp_gf, and bbp_val are in sync
  • rsync needed packages in bbp_gf to /staging
  • Run Part-A and Part-B full validations for each method
    • Can use XXXX_a.sh and XXXX_b.sh scripts (where XXXX is each method)
      • Create and submits to cluster all validation events for that method
  • Plot results
    • plot_XXX_a.sh and plot_XXX_b.sh scripts will generate the needed plots automatically