240 likes | 259 Vues
Discover the evolution of CMAS from its establishment by an EPA grant to its role in technology transfer and community growth. Explore its move to UNC, outreach efforts, research goals, and software development achievements. Learn about valuable CMAS services including data clearinghouse, application support, and enhanced consultation. Engage with the CMAS community through workshops, training, and site maintenance. Stay informed about challenges and future objectives outlined by the External Advisory Committee. Join us in advancing air quality modeling technology!
E N D
Status of the CMAS Center Bob Imhoff, CMAS Director
The CMAS • Established by a Grant from EPA Offices • OAQPS • ORD • Period of performance • November 1, 2001 – October 31, 2005
CMAS Purpose • Perform technology transfer and support of Models-3 to the air quality community • Serve to connect the community • Foster growth of developer and user communities • Serve as information clearinghouse • Become a hub for education about modeling • Develop and market CMAS value to become self-sufficient • Provide resources to the community in a cost-sharing manner
The CMAS has moved...From MCNC to the University of North Carolina UNC MCNC
Director- Bob Imhoff • Responsibilities • Coordinate activities • Make sure milestones are met • Convene External Advisory Committee
CMAS Roles • Outreach • Research • Software Development • Support
Outreach Coordinators – Bob Imhoff & Adel Hanna • Develop contact database • Identify state, public, and private industry needs • Promote Value • Market CMAS benefits • Website, listserv • Newsletter • Conference participation
Specialty Workshops • Hold 1 or 2 workshops on special issues: • PM Modeling • Summarize results to date • Share experiences – good & bad • Develop consensus on best practices • Toxics Modeling • Intercontinental Transport • Toxics emissions modeling • We’d like to hear from you
Research Coordinator-Rohit Mathur • Verify scientific review of Models-3 changes • Report results of testing, evaluation, and review to EAC. • Coordinate Models-3 Research Activities
Research Objectives • Working Toward the Future • PM modeling. • Air Quality Forecasting • Toxics Modeling • Long-range transport and seasonal simulations • Improvements in emissions modeling • Improved representation of free troposphere and exchange with PBL
Software Development CoordinatorsSarav Arunachalum & Uma Shankar • Significant Accomplishments • Partial Implementation of Software Development Protocol in newest Models-3 release • Now fully implementing the Software Development Protocol • Developing a Consensus for Coding Guidelines • Goal – full implementation of protocol for 2004 Models-3 release.
Applications Support CoordinatorZac Adelman • Help Desk • About 8 user support requests per week
Applications Support • List Serve • 220 members • Adding at a rate of > 20 per month • Training Class develop & deliver • CMAQ • SMOKE • MIMS • New Mobile Training Lab • Can offer same training at your site
CMAS Services in Use • Shared-data clearinghouse • Model testing and integration • Application consulting • Integration of new, alternative modules • Port and benchmark alternative modeling platforms • Provision of Computing resources
CMAS Value-added Services • Enhanced and Expedited support • Requests for data • Requests for assistance • Email and telephone support • Site specific issues addressed • Consultation on modeling issues • Coordination of work between staffs
Site Maintenance and testing • Developed site • Completed transition from EPA website to CMAS site
External Advisory Committee • Guide CMAS Center. • Define needs and priorities • Advise on changing requirements • Set research and development agendas • Review activity progress • Make recommendations for the advancement of Models-3 science and software improvements. • Assist in developing a network of contacts by identifying users and other air quality programs.
CMAS Year 3 Challenges • Protection and acknowledgment of intellectual property • Coordination of Community Model Development • Taking PAVE to open source • Obtaining sufficient external revenue