Staff Priorities - Fabio: Difference between revisions

From SCECpedia
Jump to navigationJump to search
Fsilva (talk | contribs)
No edit summary
Fsilva (talk | contribs)
No edit summary
Line 2: Line 2:


* Fling Study
* Fling Study
** We are now 36/42
** We are now 37/42
** Scenario 117 (7.8M) finished and was verified, tar file created
** Scenario 137 validated
** Scenario 137 (7.5M) finished, needs to be verified
** Remaining scenarios running on GEOSYS and HPCC
** After filesystem was restored, started Scenario 139, John Yu restarted the remaining cases on GEOSYS
** Updated wiki tables: http://scec.usc.edu/scecpedia/Fling_Study#Codebase_URS.2FURS.2FURS.2FURS
** Updated wiki tables: http://scec.usc.edu/scecpedia/Fling_Study#Codebase_URS.2FURS.2FURS.2FURS
* Meetings with Phil to discuss broadband development, defined milestones for this week
* Talked to John Yu about setting up Cruise Control
* Talked to Kevin, and got his Cruise Control configuration file


== Today: ==
== Today: ==


* Fling Study
* Fling Study
** Validate scenario 137, create tar file
** Monitoring running scenarios
* Meet with John Yu to discuss Broadband services/data and Cruise Control setup
* Make trunk pass Unit tests (almost there)
* Create Cruise Control configuration file, resolve any dependencies
* Make trunk pass Acceptance tests
* Create Cruise Control configuration file (use Kevin's template)


== Blocked: ==
== Blocked: ==
Line 21: Line 20:


== Followups: ==
== Followups: ==
* John Yu: Cruise Control setup, backup status @ TBD
* Broadband development with Phil @ TBD


== Ongoing: ==  
== Ongoing: ==  

Revision as of 16:56, 19 June 2012

Yesterday:

Today:

  • Fling Study
    • Monitoring running scenarios
  • Make trunk pass Unit tests (almost there)
  • Make trunk pass Acceptance tests
  • Create Cruise Control configuration file (use Kevin's template)

Blocked:

  • No

Followups:

  • Broadband development with Phil @ TBD

Ongoing:

  • Look for ways to break up the GF directory layout, some ideas are:
    • Figure out how to separate the validation data from Greens Functions
    • Create separate validation package
    • Separate events and codebases from each other