1 / 5

Tutorials/Training readme is too long

Tutorials/Training readme is too long Need specific tutorials – sys admin, new user, how to use variational code, more detail on new features in this release NWS will make LAPS training available to user community. Review format of LAPS forum. Are more categories needed?

tarak
Download Presentation

Tutorials/Training readme is too long

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. Tutorials/Training • readme is too long • Need specific tutorials – sys admin, new user, how to use variational code, more detail on new features in this release • NWS will make LAPS training available to user community. • Review format of LAPS forum. Are more categories needed? • Insure LAPS forum is archived. Email questions need to go into the forum and/or FAQ. Insure forum can be searched. • Need technical writing help to produced good tutorials -- Katy Human / Annie Riesier/ J. Osborn/ W VonD.

  2. Applications/New features • User wants to be able to compare LAPS output with that from other NWPs. • Need to add a land surface package • Need BC adjustment to be automatic. Or at least document the procedure. • Need converters for all types of satellites in the sky to be in the repository. Can those already written by the user community be brought back to ESRL? • Will AWIPSII be available to users outside of NWS? • New observational data sources ’

  3. Verification/automated testing • Make verification package more sophisticated to that can be used to performs ‘ongoing, regression’ testing

  4. Upgrade and life cycle • Users do not have lots of time to upgrade. Upgrades need to be as easy as possible. Maybe an install/upgrade/test wizard would make sense. • Regression testing – now ad-hoc. Some level of automated testing would be good. It can expose bugs that were accidentally injected and it may expose long-lived, hard to find bugs. • Consider 3rd party to do regression testing – maybe through DTC • How does one migrate to vlaps without clobbering what clobbering what they have? Need to know what to watch, what are the pitfalls. • Major releases should carry a version number. Maybe LAPS.year.month (ex LAPS.2012.10) • AWIPSII – Need to insure we are coordinated with NWS for release cycles

  5. User Community and Comms • Direct contact by new user to LAPS developers seems to be a good way to get started. But when this happens how does this information get captured for the next user. Maybe incorporate into tutorials. • Need LAPS champions in NWS – need to identify current users who are willing to be one • Need a LAPS ‘PR brochure • Consider outreach to ‘charter schools’ – seek students with interest in Meteorology • Consider collaboration with UNIDATA for LAPS distribution.

More Related