1 / 9

McIDAS Advisory Committee (MAC)

The McIDAS Advisory Committee (MAC), led by Matthew Lazzara from the Antarctic Meteorological Research Center, aims to enhance the McIDAS-V development process. This session will outline the committee's history, structure, and charge, as well as highlight opportunities for organized community input. We will discuss essential functions and desired new features for McIDAS-V, as well as facilitate a panel discussion to gather participants' feedback and suggestions. Join us to shape the future of McIDAS and ensure it meets user needs effectively.

kelton
Download Presentation

McIDAS Advisory Committee (MAC)

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. McIDAS Advisory Committee (MAC) Matthew Lazzara McIDAS Advisory Committee Chair Antarctic Meteorological Research Center Space Science and Engineering Center University of Wisconsin-Madison

  2. Outline • History & Opportunity • Charge to the MAC • Membership • Task 1: • Input for McIDAS-V • Task 2: • Panel Discussion • Input from you!

  3. History & Opportunity • History: • Advocating community input & information exchange in the MUG: • MUG Formation and MUG Meetings • Communications Timeout • MUG Bulletin Board (BBS) • McIDAS-XRD (Research & Development) • MDF (MUG Developers’ Forum) • McIDAS Survey • Opportunity: • McIDAS-V development process as a vehicle: • Opportunity for organized community input • McIDAS Users’ Group (MUG) a critical partner • Meet users needs throughout the development process!

  4. Charge to the MAC • Gather input from sites and collaborators! • Provide community input to McIDAS Group at SSEC • Alpha testing and feedback • Provide input/discuss issues as they arise • Two way street: SSEC <==> MAC • 2 year commitment by members • One chair, no secretary - members share duties • One member per site • Virtual meetings monthly • Face to face gathering before MUG Meetings (without McIDAS Group Members)

  5. Membership • Brian Hughes, NOAA ESPC • James Kelly, ABoM • Matthew Lazzara, AMRC (Chair) • Deb Molenar, NOAA/NESDIS RAMMB • Jim Nelson, CIMSS • Louis Nyugen, NASA LaRC • Paul Wahner, NASA CCFC • Tom Yoksas, Unidata UCAR McIDAS Group non-voting members: • Becky Schaffer, SSEC • Dee Wade, SSEC

  6. Task 1: Input for McIDAS-V (part I)(Examples!) • Critical functions to keep: • Large number of frames/loops • Scheduler function • Random loop sequencing • Contour control on point source data (e.g., PTCON with BPAR=, CINT=, LLINC=, etc.) • Be able to keep running current site-developed software • Be able to run unattended (and background processing) • etc.

  7. Task 1: Input for McIDAS-V (part II)(Examples!) • New functions to have: • Ability to work with “new” data formats such as BUFR, HDF5, etc. • Hyperspectral analysis capabilities (multiple display options, statistics, etc.) • Event scheduler • etc. • Extend existing capabilities: • Read and write netCDF files • Improved/updated map outlines files (coastlines, political boundaries, etc.) • etc.

  8. Task 2: Input from you! • Panel Discussion: • What do you like? • What do you not like? • What do you need (and perhaps don’t have now)? • What are your expectations? • What are we forgetting? • Any other comments, questions or suggestions?

  9. Thank You!

More Related