<!DOCTYPE html
     PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<!-- EPA Template version 3.2.1, 28 June 2006 -->
<head>
	<!-- #BeginEditable "doctitle" -->
	<title>Minutes of the January 24, 2006 Exposure Modeling Public Meeting | Pesticides | US EPA</title>
	<meta name="DC.description" content="pesticide, pesticides,Access to and information regarding simulation models to predict pesticide concentrations in surface and ground water for use in both human health and aquatic ecological exposure assessments.  Exposure modeling public meeting products." />
	<meta name="keywords" content="EPA,Environmental Protection Agency, OPP, pesticides, pesticide, office of pesticide programs, scigrow, geneec, first, water models, exposure modeling public meeting" />
  <!-- #EndEditable -->
	<!-- #BeginEditable "metaElements" -->
	<meta name="DC.title" content="Minutes of the January 24, 2006 Exposure Modeling Public Meeting | Pesticides | US EPA" />
	<meta name="DC.subject" content="EPA,Environmental Protection Agency, OPP, pesticides, pesticide, office of pesticide programs, scigrow, geneec, first, water models, exposure modeling public meeting" />
	<meta name="DC.type" content="" />
	<!-- For date metadata, use the format YYYY-MM-DD -->
	<meta name="DC.date.modified" content="2007-06-07" />
	<meta name="DC.date.created" content="" />
	<meta name="DC.date.reviewed" content="" />
  <!-- #EndEditable -->

	<meta name="DC.language" content="en" />
	<meta name="DC.Creator" content="US EPA, Office of Pesticide Programs" />
	<meta http-equiv="Content-Style-Type" content="text/css" />
	<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
	<link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" />
	<link rel="meta" href="http://www.epa.gov/labels.rdf" type="application/rdf+xml" title="ICRA labels" />
	
	<style type="text/css" media="screen">@import 'http://www.epa.gov/epafiles/s/epa.css';</style>
	<style type="text/css" media="screen">@import 'http://www.epa.gov/opp00001/styles/opp_styles.css';</style>
	<!--[if lt IE 7]>
	<link rel="stylesheet" type="text/css" href="http://www.epa.gov/epafiles/s/ie.css" />
	<link rel="stylesheet" type="text/css" href="http://www.epa.gov/opp00001/styles/opp_ie_styles.css" />
<![endif]-->
	<link rel="stylesheet" type="text/css" media="print" href="http://www.epa.gov/epafiles/s/print.css" />
	<script type="text/javascript" src="http://www.epa.gov/epafiles/js/epa-core.js"></script>
	<script type="text/javascript" src="http://www.epa.gov/epafiles/js/extra.js"></script>
</head> 

<body>
<p class="skip"><a id="skiptop" href="#content" title="Jump to main content.">Jump to main content.</a></p>

<div id="header"> <!-- START EPA HEADER -->

	<div id="logo"><a href="http://www.epa.gov/" title="US EPA home page"><img src="http://www.epa.gov/epafiles/images/logo_epaseal.gif" alt="[logo] US EPA" width="100" height="110" /></a></div>

	<div id="areaname"> <!-- START AREA NAME -->
		<p><span class="epaAreaName">Pesticides: Science and Policy </span></p>
  </div> <!-- END AREA NAME -->

	<!-- START SEARCH CONTROLS -->
	<form id="EPAsearch" method="get" action="http://nlquery.epa.gov/epasearch/epasearch">
		<!-- START AREA SPECIFIC LINKS AND SEARCH BOX  -->
		<!-- CHANGE links to point to your own recent additions and contact pages -->
		<!-- REMOVE recent additions link if your area doesn't have one -->
		<p><a href="http://cfpub.epa.gov/pesticides/recentadditions.cfm">Recent Additions</a> | <a href="http://www.epa.gov/pesticides/regulating/contacts.htm">Contact Us</a> 
			<span class="search"><strong>Search:</strong> 
			<input type="hidden" name="fld" value="gov/pesticides/science,oppfead1/trac/science,oppfead1/carat,oppfead1/cb/ppdc/,gov/scipoly/sap,oppad001,pesticides/antimicrobials,oppbppd1/biopesticides/regtools/guidelines,oppbead1/methods,oppbead1/labs,oppefed1/models,opptsfrs/home,gov/scipoly/oscpendo,gov/PR_Notices" />
			<input type="hidden" name="areaname" value="Pesticides: Science and Policy" />
			<input type="hidden" name="areacontacts" value="http://www.epa.gov/pesticides/science/contacts.htm" />
			<!-- AREA ADVANCED SEARCH URL HERE (OPTIONAL) -->
			<input type="hidden" name="areasearchurl" value="http://www.epa.gov/pesticides/search.htm" />
			<!-- THE REMAINING HIDDEN INPUTS ARE USED BY THE SEARCH ENGINE - DO NOT EDIT -->
			<input type="hidden" name="result_template" value="epafiles_default.xsl" />
 			<input type="hidden" name="filter" value="sample2filt.hts" />
			<input name="typeofsearch" id="EPAall" type="radio" value="epa"/><label for="EPAall">All EPA</label> 
			<input name="typeofsearch" id="Areaall" type="radio" value="area" checked="checked" /><label for="Areaall">This Area</label> 
			<input name="querytext" id="searchbox" value="" /> 
		  <input name="submit" id="searchbutton" type="submit" value="Go" /></span>
	  </p>
	</form> <!-- END SEARCH CONTROLS -->
		
	<ul> <!-- BEGIN BREADCRUMBS -->
		<li class="first">You are here: <a href="http://www.epa.gov/">EPA Home</a></li>
		<li><a href="http://www.epa.gov/pesticides/index.htm">Pesticides</a></li>		
		<!-- START AREA BREADCRUMBS -->
		<!-- #BeginEditable "breadcrumbs" -->		
		<li><a href="http://www.epa.gov/pesticides/science/index.htm">Science & Policy</a></li>
		<li><a href="http://www.epa.gov/pesticides/science/models_db.htm">Models 
            and Databases</a> </li>
		<li><a href="http://www.epa.gov/oppefed1/models/water/index.htm">Water Models		</a></li>
		<li><a href="http://www.epa.gov/oppefed1/models/water/emwg_top.htm">Exposure 		Modeling Public Meeting (EMPM) Information and Products</a></li>
		<li>Minutes of the January 24, 2006 Exposure Modeling Public Meeting</li>
    <!-- #EndEditable -->
		<!-- END AREA BREADCRUMBS -->
	</ul> <!-- END BREADCRUMBS -->

</div> <!-- END EPA HEADER -->

<hr class="skip" />

<p class="skip"><a id="pagecontents"></a><a id="pagetop"></a></p>
<div id="content"> <!-- BEGIN PAGE CONTENTS -->	<!-- EPA SITE-WIDE ANNOUNCEMENTS -->
	<!-- DO NOT REMOVE - this code is used for emergency messages -->
<!-- If this page is a Program Office or a Topics home page, CHANGE "sitewidec" TO "sitewideb" -->
	<p id="sitewidec"></p>

	<!-- BEGIN PAGE NAME -->
	<h1><!-- #BeginEditable "PageName" -->Minutes of the January 24, 2006 Exposure Modeling Public Meeting<!-- #EndEditable --></h1>
	<!-- END PAGE NAME -->

			<!-- BEGIN CONTENT AREA -->

			<!-- #BeginEditable "content" -->

<p>Office of Pesticide Programs (OPP) Conference Room 1126<br />
1801 S. Bell St. - Crystal Mall 2<br />
Arlington, VA  22202</p>

<p><strong>On this Page</strong></p>

<ul>
<li><a href="#attendees">Attendees</a></li>
<li><a href="#welcome">Welcome and Introductions</a></li>
<li><a href="#brief">Brief Updates</a></li>
<li><a href="#presentations">Major Presentations</a></li>
<li><a href="#wrap">Wrap up</a></li>
</ul>

<hr />

<h2 id="attendees">Attendees</h2>

<table class="table zebra" summary="Attendees">
<thead>
<tr><th scope="col">Name</th><th scope="col">Association</th></tr>
</thead>
<tbody>
<tr><td>Marietta Echeverria</td><td>	OPP/EFED</td></tr>
<tr><td>Mark Corbin</td><td>	OPP/EFED</td></tr>
<tr><td>Dirk Young</td><td>	OPP/EFED</td></tr>
<tr><td>Betsy  Behl</td><td>	OPP/EFED</td></tr>
<tr><td>Mohamed Ruhman</td><td>	OPP/EFED</td></tr>
<tr><td>Lucy Shanaman</td><td>			OPP/EFED</td></tr>
<tr><td>Norm Birchfield</td><td>		OPP/EFED</td></tr>
<tr><td>Keara Moore	</td><td>		OPP/EFED</td></tr>
<tr><td>Subijoy Dutta</td><td>			OPP/EFED</td></tr>
<tr><td>Richard Lee</td><td>			OPP/EFED</td></tr>
<tr><td>Kathy Carr</td><td>	Monsanto</td></tr>
<tr><td>Russell Jones </td><td>	BayerCropScience</td></tr>
<tr><td>T.S. Ramanarayanan</td><td>	BayerCropScience</td></tr>
<tr><td>Jonathan Angier</td><td>	OPP/EFED</td></tr>
<tr><td>Pat Havens</td><td>	Dow</td></tr>
<tr><td>Nasser Assaff</td><td>	Valent</td></tr>
<tr><td>Al Barefoot</td><td>	DuPont</td></tr>
<tr><td>Paul Hendley </td><td>	Syngenta</td></tr>
<tr><td>Scott Jackson </td><td>	BASF</td></tr>
<tr><td>Uwe Wanner</td><td>	Crompton</td></tr>
<tr><td>Mark Cheplick </td><td>	Waterborne Environmental</td></tr>
<tr><td>Adrian Wadley</td><td>	Stone Environmental inc</td></tr>
<tr><td>Tom Nolan</td><td>	USGS</td></tr>
<tr><td>Lajan Barnes</td><td>			Environmental Turf Services</td></tr>
<tr><td>Michelle Thomson</td><td>		Dupont</td></tr>
<tr><td>Mary Nett</td><td>			Water Quality Consulting</td></tr>
<tr><td>Ken Rojas</td><td>			USDA-NRCS - Fort Collins</td></tr>
<tr><td>Frank Stancil</td><td>			USEPA ORD Athens</td></tr>
<tr><td>Russell G Kreis</td><td>			USEPA ORD NHEEL Gross Ile MI</td></tr>
<tr><td>David Loshke 	</td><td>		APVMA</td></tr>
<tr><td>Nasser Assaf	</td><td>		Valent</td></tr>
<tr><td>Lisa Eisenhauer</td><td>			EPA EFED</td></tr>
<tr><td>Rob Everich	</td><td>		MANA</td></tr>
<tr><td>Noha Gaber</td><td>			EPA/ORD/NCER</td></tr>
</tbody>
</table>

<table class="table zebra">
<caption><strong>Dial In Participants </strong></caption>
<thead>
<tr><th scope="col">Name</th><th scope="col">Association</th></tr>
</thead>
<tbody>
<tr><td>Laj Ahuja</td><td>			USDA</td></tr>
<tr><td>Jim Ascough	</td><td>		USDA</td></tr>
<tr><td>Lizanne Avon</td><td>			PMRA</td></tr>
<tr><td>Ian Kennedy	</td><td>		PMRA</td></tr>
<tr><td>Ted Kuchnicki	</td><td>		PMRA</td></tr>
<tr><td>James Cooper</td><td>			FL Dept of Ag</td></tr>
<tr><td>John Troiano	</td><td>		CDPR</td></tr>
<tr><td>Frank Spurlock	</td><td>		CDPR</td></tr>
<tr><td>Joseph Bagdon	</td><td>		USDA</td></tr>
<tr><td>Tammy Estes	</td><td>		Stone</td></tr>
<tr><td>John Langstaff	</td><td>		EPA RTP</td></tr>
<tr><td>Don Wauchope	</td><td>		USDA</td></tr>
<tr><td>Ken Schere	</td><td>		EPA- ORD</td></tr>
<tr><td>Shawn Roselle	</td><td>		EPA - ORD</td></tr>
<tr><td>Elise McCoy	</td><td>		FMC</td></tr>
<tr><td>Natalia Peranginangin</td><td>		Syngenta</td></tr>
</tbody>
</table>

<p class="pagetop"><a href="#content">Top of page</a></p>
<hr />

<h2 id="welcome">Welcome and Introductions</h2>

<p>The Exposure Modeling Work Group hosts quarterly meetings that are open to the public and provide a forum for cooperative exchange of facts and technical information on technical issues related to pesticide exposure modeling between EFED and stakeholders with similar technical expertise.  Mark Corbin (OPP/EFED) chaired the meeting in the capacity of co-chair of the EFED Water Quality Tech Team (WQTT). </p>

<p>This meeting includes presentations which focused on incorporation of geospatial tools and data in pesticide risk assessments.  All FIFRA EMWG agendas, minutes and presentations and be found at: <a href="http://www.epa.gov/oppefed1/models/water/emwg_top.htm">http://www.epa.gov/oppefed1/models/water/emwg_top.htm</a></p>

<p class="pagetop"><a href="#content">Top of page</a></p>
<hr />

<h2 id="brief">Brief Updates</h2>

<ol>
<li><p><strong>PRZM3.12.2 Evaluation (M. Corbin)</strong></p>

<p>QA/QC report is done but is going through EFED management review.  Currently addressing minor edits and additional documentation to improve clarity of document.  Will only address curve number and emergence dates presently.  A separate QA/QC review and report will be done later on volatility/temperature.</p>

<p>On EFED shell (current version PE4v01.pl) there is ongoing QA/QC of a new version of (PE5.pl).  PE5.pl will be needed to run the new version of PRZM (3.12.2).  </p>

<p>A process has been established for QA/Q of the EXPRESS Shell.  Future updates will be provided. </p>

<p>Currently approved EFED PRZM Scenarios have been updated on the website.  This was required in order to clarify the distinction between EFED standard scenarios and OP scenarios.  Also, new scenarios which have been created since the last website update have been added.  EFED contractor is working on revisions to scenarios to respond to internal and external comments regarding inconsistencies between scenarios and to update the compatibility of the scenarios to the new EFED Shell (PE5.pl) and new version of PRZM (3.12.2).</p>
</li>
<li><p><strong>Terrestrial Dissipation studies (M. Corbin)</strong></p>
<p>The document is going through one final round of edits and French translation within PMRA (only on those edited portions of the document).  EFED/PMRA anticipate release of the document in spring 2006.</p>
</li>
<li><p><strong>Drift reduction technology update (N. Birchfield)</strong></p>

<p>EPA's Environmental Technology verification program is working with the team on this.  Open meeting has been arranged in late January to look at protocols already available for Measuring the impact of drift reduction technologies.  EFED are looking at getting a "reduction factor" that can be applied within standard risk assessment measures.  There will be a meeting in late January on drift reduction estimation.  Contact Norm Birchfield for further information.  RegDISP has been looked at but no code refinement has been done since last time.</p>
</li>
</ol>

<p class="pagetop"><a href="#content">Top of page</a></p>
<hr />

<h2 id="presentations">Major Presentations</h2>

<p><strong>FOCUS Model Version Control Experiences (Russell Jones, Bayer CropScience)</strong></p>

<p>Russell Jones presented the version control process used by the Forum for the Co-ordination of Pesticide Fate Models and their Use (FOCUS), an EU organization representing regulatory agencies, industry, and academia.  FOCUS provides guidance documents and software tools for performing exposure assessments and faces a version control challenge because they work with many organizations from different countries using different software packages.  FOCUS has a permanent workgroup that manages software changes and provides user support.  Model distribution is handled through their website, which includes all current and previous model versions.  When model bugs are identified, usually by users, the model developer corrects the problem and runs a standard set of test cases.  The updated model is made available to workgroup members who have two weeks to make a response.  An outside modeler then checks for possible interferences with other FOCUS models.  When finalized, the version number is updated, the model is posted to the website along with the test cases and supporting documentation, and users are notified.  The FOCUS group has found that this process is an effective way of managing version control with a minimum of effort.  The presentation included a walk-through of the FOCUS website,
<a href="http://www.epa.gov/epahome/exitepa.htm" title="EPA's External Link Disclaimer"><img src="http://www.epa.gov/epafiles/images/epafiles_misc_exitepadisc.gif" width="87" height="13" alt="Exit EPA Disclaimer" /></a>
 <a href="http://viso.ei.jrc.it/focus">http://viso.ei.jrc.it/focus</a>.</p>

<p><strong>Model Development and Version using a Collaboration environment (COLAB) - (Ken Rojas - USDA NRCS, Fort Collins)</strong></p>

<p>Ken Rojas of USDA NRCS presented the efforts at the Information Technology Center in Fort Collins, Colorado to develop and implement a model version control system and quality assurance process.  The NRCS has developed CoLab which is a Collaborative Software Development system whose purpose is to facilitate software development.  The system consists of two components, "Codebeamer" and "Subversion".  Codebeamer is a commercial web application at the developer's tool level to help manage collaborative operations.  It is accessible via web browser, file browser (tortoise) or command line.  Data on all users is sharable to facilitate communication.  Codebeamer provides a document review management system with macros to ensure project tracking is efficient and tailored to user needs (e.g. milestones, bug/feature, and document tracker system).   Version control is managed using Subversion.  Subversion is an open source version control system designed to track, compare and undo changes to source code across multiple editing sessions.  It can manage concurrent changes and preserve a consistent code/document state for each version.  The system is designed to encourage documentation of any changes to model code and provide a repository for future changes/upgrades to model code.  The system allows for easy synchronization of multiple users operating at remote locations within a single centralized location.  Currently, NRCS has a total of 63 projects that are currently managed using this system.  Many of these projects are very complex and so subversion is used to track, compare and undo changes to source Code and documents across multiple editing sessions.  </p>

<p>In addition, the presentation discussed NRCS' implementation of an Object Modeling System (OMS).  OMS is an integrated model development and application platform that promotes interaction between model developers and service providers.  The platform supports model component development and testing, managing a component library, integrating components into new and existing models, manages model applications, and analyzes model output.  The benefit of this system is that it supports new model development, facilitates long term maintainability of models by decomposing them into science processes, leads to customized models, and makes implementation easier.  </p>
<p>More information on Colab, Subversion, and OMS can be found at<br />
<a href="http://www.epa.gov/epahome/exitepa.htm" title="EPA's External Link Disclaimer"><img src="http://www.epa.gov/epafiles/images/epafiles_misc_exitepadisc.gif" width="87" height="13" alt="Exit EPA Disclaimer" /></a>
 <a href="https://colab.sc.egov.usda.gov">https://colab.sc.egov.usda.gov</a>.  </p>
 
<p><strong>Version Control for Great Lakes Models on Unix Systems (Russell Kreis, Grosse Isle Duluth - ORD- NHERL)</strong></p>

<p>Russell Kreis of ORD-NHEERL gave a presentation on the modeling efforts associated with atrazine in the Great Lakes and transitioned this discussion into a summary of model QA and version control processes and issues learned.  Russ briefly went over a summary of the many projects completed by the Grosse Ile/Duluth office of ORD.  Specifically, Russ presented the concept behind the Lake Michigan Mass Balance project and walked the audience through the application of the model relative to atrazine.  In the Lake Michigan basin, atrazine is usually applied to corn fields in the spring to control broadleaf and some grassy weeds.  Approximately 850,000 kg are applied annually in the Lake Michigan basin.  The Lake Michigan Mass Balance Modeling framework includes computational transport, mass balance, and bioaccumulation and has 3 levels of spatial resolution (whole lake, 10 surface segments and 41 water segments, and a high- resolution model consisting of 2318 surface segments and 44,042 water segments).  The lake monitoring data showed fluctuating values of atrazine between 30 and 60 ng/l with seasonal loadings (spring to early summer) focused on the southeast and northwest shores.  Modeling predicts that with no increase or decrease in loadings that concentrations in the Lake will increase slightly and level off thereafter.  </p>

<p>For the predictive modeling version control and archiving on UNIX system at EPA in Grosse Ile, MI, the following automated RCS system is being used:</p>

<ul>
<li><p>RCS - <em>R</em>evision <em>C</em>ontrol <em>S</em>ystem - Version 5.7 - utility included with UNIX systems; and it's relatively user friendly</p></li>
</ul>

<p><strong>Other available and related systems include</strong>:</p>

<ul>
<li><p>Parent: SCCS - <em>S</em>ource <em>C</em>ode <em>C</em>ontrol <em>S</em>ystem</p></li>
<li><p>CVS - <em>C</em>oncurrent <em>V</em>ersion System, which is possibly the most widely used; layered on top of RCS, and more robust than RCS.</p></li>
<li><p>PRCS - <em>P</em>roject <em>R</em>evision <em>C</em>ontrol <em>S</em>ystem - new front-end system similar to CVS, but more user-friendly</p></li>
<li><p>RCE - <em>R</em>evision <em>C</em>ontrol <em>E</em>ngine - successor to RCS; revision control with JAVA graphics interface</p></li>
</ul>
 
<p>Some utilities are included as standard software with the UNIX operating system and are - version control - archive, file history, flexibility, and tracking.  Some of the operational utility includes - check in/check out (with limited access); identification/find; compare versions; and merge revisions.  Basic source control operation in RCS involves creating a RCS file whenever an authorized user opens a working file for reading or revision. After the review/revision of the working file is completed, the source control operation compares the working file to the RCS file and prompts the user to save or discard the changes. If the save option is chosen then it changes the RCS file with a new version number. If discarded, no change takes place in the RCS file.  The challenges faced by Grosse Ile include infrastructure support and maintenance for a high volume of data and metadata from Lake Michigan, SOPs and quality assurance documentation, version control, associated files, directories and utilities, archives, operational and user documentation, reports and publications, IT and QA audits.  They are also working towards migration to LINUX systems for better system longevity and availability.</p>

<p><strong>QA for environmental fate data tasks in EFED  (Lisa Eisenhauer, USEPA- EFED)</strong></p>

<p>Lisa Eisenhauer outlined EFED's procedures for quality assurance of tools such as exposure models that use environmental data.  First, the tool developer establishes objectives and puts together a project team.  The team outlines a project plan describing the project goals and assigning responsibilities for individual tasks.  After the tool and supporting documentation are developed, the version is locked down and quality control begins.  Lisa presented an example of a spreadsheet template used to track QC progress.  Before QC begins, for each objective, a series of checks are listed along with a definition of what a success for that check would be.  As QC is performed, the spreadsheet is updated with the status of each check.  The QC should consider the basic functionality of the code and its ability to handle ranges of potential data as well as review all support documents.  The purpose of this QC process is to identify, rather than solve, problems.  After QC is completed, the team determines what changes or fixes need to be made and the QC process is repeated.  The new tool is named according to version control policy and made available in a location that identifies it as the current version and separates it from all archived versions.  One person is designated to provide internal maintenance and the QA officer and webmaster do quarterly overall maintenance on all available tools.</p>

<p><strong>Community Multi-Scale Air Quality <sup>*</sup>(CMAQ) Model - Quality Assurance and Version Control (Ken Schere and Shawn Roselle - Atmospheric Model development Branch NOAA/Atmospheric sciences modeling division - EPA/ORD/NERL)</strong></p>

<p>CMAQ is an air quality model that can simulate many characteristics of air quality in periods of weeks to years and on scales ranging from city to national level.  The modeling system is made up of multiple linked models and processors, all of which require quality assurance.  QA is managed through project plans (QAPP) which direct model development, data acquisition, project management, and oversight.  In addition, guidelines have been established to provide a common format for coding and also for managing code testing, archiving, and version control.  When modifications are needed, model developers start with code from the model archive.  After making revisions, developers perform unit testing which is discussed with a development group, documented, and then passed on to a model code manager who is responsible for another layer of testing prior to integrating the code into the model archive.  A Concurrent Versions System is used to maintain a reproducible history of source files, with separate archives for each model that can only be updated by archive administrators.  Occasionally, codes are incorporated into the model which have been developed by external groups without the same QA guidelines.  These codes have to pass certain criteria before becoming part of the model and when they do, they are compartmentalized so that they are easily identifiable.  A peer review panel of external members meets regularly to provide comments and recommendations.</p>

<p><strong>Evaluation of AGDISP Ground Boom Spray Drift Model (Al Barefoot/ T.S. Ramanarayanan, CLA Spray Drift Issues management team)</strong></p>

<p>Rama gave background and information on using the model and then compared model output with field data and proposed the path forward.  A mechanistic model offers strategic advantages for drift prediction when compared with empirical models.  However, he showed that AGDISP consistently over-predicts drift from Ground boom sprays based on the Tom Wolf field data set.  Rama concluded that the model is not yet ready for regulatory use and proposed a path forward involving checking the performance of the Visual Basic interface, expanding existing data in terms of goodness of fit and sensitivity analysis, summarizing all comparison data for peer review and investigating the effect of droplet velocity</p>

<p class="pagetop"><a href="#content">Top of page</a></p>
<hr />

<h2 id="wrap">Wrap up</h2>
 
<p>Discuss date for the next meeting later - Due to OPP move in late April - early May, the next EMWG scheduled for late April will be postponed.  The next EMWG will likely occur in July.  Updates will be communicated via the list-serve once EFED knows more about timing and meeting space availability.</p>

<p><strong>Continuing Actions</strong>:</p>
 
<p>Current QA effort for PRZM 3.12.2 will not address volatility and temperature routines.  These issues will be addressed in the next round of QA.  Updates to be provided at a future EMWG.</p>

<p><strong>New Actions</strong>:</p>

<p><strong>EFED to address issue of public availability of EFED QA/QC documentation and findings at the next meeting</strong></p>

<p><strong>EFED to check on internal backup frequency and storage of Model code and associated QA/QC files</strong></p>

<p><strong>Next Meeting</strong>:</p>
 
<p>Likely in late July.  Exact date and location to be determined after OPP move in late April - early May.</p>

<p class="pagetop"><a href="#content">Top of page</a></p>
<hr />

      <!-- #EndEditable --> 

</div> <!-- END CONTENT -->

<hr class="skip" />

<div id="area-nav"> <!-- BEGIN LEFT SIDEBAR NAVIGATION -->
	<h3 class="skip">Local Navigation</h3>
	<ul>
		<li><a href="http://www.epa.gov/pesticides/">Pesticides Home</a><hr /></li>
		<li><a href="http://www.epa.gov/pesticides/science/index.htm">Science & Policy Home</a></li>
		<li><a href="http://www.epa.gov/pesticides/science/committees.htm">Advisory Committees</a></li>
		<li><a href="http://www.epa.gov/pesticides/science/policies.htm">Policy & Guidance</a></li>
		<li><a href="http://www.epa.gov/pesticides/science/guidelines.htm">Test Guidelines</a></li>
		<li><a href="http://www.epa.gov/pesticides/science/models_db.htm">Models & Databases</a></li>
		<li><a href="http://www.epa.gov/oppbead1/labs/index.htm">Laboratories</a></li>
		<li><a href="http://www.epa.gov/oppbead1/methods/index.htm">Analytical Methods Procedures</a></li>
	</ul>
</div> <!-- END LEFT SIDEBAR NAVIGATION -->

<hr class="skip" />

<div id="footer"> <!-- BEGIN FOOTER -->
	<ul id="globalfooter">
		<li><a href="http://www.epa.gov/">EPA Home</a></li>
		<li><a href="http://www.epa.gov/epafiles/usenotice.htm">Privacy and Security Notice</a></li> 
		<!-- BEGIN AREA COMMENTS LINK -->
		<!-- CHANGE link to point to your own contact page -->
		<li class="last"><a href="http://www.epa.gov/pesticides/science/contacts.htm">Contact Us</a></li>
		<!-- END AREA COMMENTS LINK -->
	</ul>

</div> <!-- END FOOTER -->

<p class="skip"><a id="skipbot" href="#content" title="Jump to main content.">Jump to main content.</a></p>
</body>
</html>
