1 / 7

Notes from breakout group 2 Session 1 (Wed, 10/24/2012)

Notes from breakout group 2 Session 1 (Wed, 10/24/2012). Notes by Ligia Bernardet. Our group Branch chief 2 FAB LAPS developer 1 Developmental Testbed Center 2 Private sector 1 NCAR scientist 1 Belgrade University 1 Korea M ix of experienced and new users of LAPS.

dyami
Download Presentation

Notes from breakout group 2 Session 1 (Wed, 10/24/2012)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Notes from breakout group 2Session 1 (Wed, 10/24/2012) Notes by Ligia Bernardet Our group Branch chief 2 FAB LAPS developer 1 Developmental Testbed Center 2 Private sector 1 NCAR scientist 1 Belgrade University 1 Korea Mix of experienced and new users of LAPS

  2. Case studies: opportunity for collaborations • Helpful to have test cases available online • Current case: Windsor tornado case • Future proposed cases • Hosted by user or by ESRL (can have link to case) • US and international cases • High-res and low-res • Cases to confirm if LAPS implementation is correct and cases for scientific study • These are just public cases - proprietary cases need to go elsewhere

  3. Open Source • Some users contribute back • they want it integrated in the next release, makes life easier • Some users do not contribute back • Expensive in the short term even if it hurts in the long term • Users need access to the latest code to add development • How many developers? Scale determines choice of solution • Spectrum of options • Post weekly build tarfiles online • Post updates online (diffs from previous tarfile, so it is smaller) • Have LAPS in SVN repository available for check out • Have LAPS in SVN repository available for committing • CRTM: need strategy for maintaining LAPS-specific changes (consider putting in repository)

  4. Documentation • Could be streamlined • More documentation about data formats, esp LSO • Users can contribute 

  5. Testing • Testing protocols setup by FAB developers with help from main developers • Developers need to run some tests before proposing new developments • Should not make it too burdensome for developer • Tests to see if results match conceptual model • Null tests: should not change certain answers • Hierarchy of development: implementation in a way that allows it to be turned off until sufficiently tested

  6. Bottle necks • Gridgen (Perhaps replace gridgen model with WPS-geogrid Baby step: there is now the ability of gridgen to read WPS output) • Processing Doppler radar (but now parallelized!) • LGA (but now runs in parallel with other processes!)

  7. Suggestions • Use LAPS FORUM to ask questions!! • List changes in namelist in README file • Onsite tutorial with practical sessions (forces production of documentation) • README file in PDF format, separate chapters • Facilitate use of lightning data and turbulence measurements • Make LAPS output ready for ingest onto MET

More Related