2) If using the “Computed Source in Standing Surface Water” module and the overland runoff loss option with known discharge to overland (OVL), an error will result when the model is run. The error states that a problem has occurred with reading “stzbulkd”.

3) When using almost any of the “User-Defined” modules, the user-interface (UI) may show strange values in some cells when FRAMES performs unit conversions. This is mainly because the value shown in a cell is larger than the cell width. You can click in a cell and scroll the value to see it in its entirety.

4) FRAMES does not prevent the user from entering a GID filename that does not adhere to the Disk Operating System (DOS) 8.3 naming convention. Note that under some circumstances, especially once the user has created several scenarios where the filename does not adhere to the DOS 8.3 naming convention and where the first 8 characters of the filename are similar, there can be random and misleading error messages that begin to show up. In most cases, this problem can be avoided if the user adheres to the DOS 8.3 naming convention.

5) The FRAMES module status light system can sometimes show downstream modules with green status lights while upstream modules have red or yellow lights. This usually occurs when the user has already created a scenario and then goes back and adds/connects additional modules to/in the scenario. Should this occur, then rerun the constituent database module and proceed with running downstream modules.

6) When using the RAGS viewer, sometimes the status light will be red and at other times it will be yellow after running the viewer. The status light for this viewer rarely turns green after running the module. However, this fact does not mean that the viewer has not successfully run.

7) Several human health impacts viewers (e.g. “HIF by Exposure Pathway, Route, and Age Group”, “HIF by Exposure Pathway and Route”, etc. ) share the same help file that does not provide enough help or information. Separate help files should be developed for the individual viewers that provide more beneficial information.

8) When using one of the “MEPAS Source in…” modules and the user has the cursor in a field and presses the F1 help key, the module will launch 2 instances of the user’s browser to the module’s help file.

9) When viewing human exposure model output in the “EPF Graphical Viewer”, the location always defaults to “(0,0) km” even though there may actually be Northing/Easting coordinates different from (0,0) km.

10) In almost all of the user-defined (known) module descriptions, the PDF file links to PNNL documentation are broken.

11) The help file for the ATO Graphical Viewer needs to provide more useful information. For example, the output coordinates are polar (degrees and radius) where 0.0 degrees is north and 90 degrees is east, and the unit of the radius, or distance, is meters. Additionally, the ATO Graphical Viewer uses Cartesian coordinates, rather than polar coordinates, to output results from the Air Plus Operator. A Cartesian grid resolution of 10,000 m is used for the Y direction, and 7895 m is used for the X direction. Due to the size and differences in grid resolution and the different coordinate systems used for the Air model and the ATO Plus Operator, results from the ATO Plus Operator can differ from summations of output from multiple individual Air models.

12) In instances where the ATO Plus Operator is used and the user selects the ATO GNUPLOT Viewer to view the output of the ATO Plus Operator, the user may receive an error that “Atoconvert” has had an access violation when the “Convert” button is pressed. This error does not occur when using the GNUPLOT Viewer to view air model output for cases that do not use the ATO Plus Operator.

13) The maximum aquifer thickness in the “MEPAS 5.0 Aquifer Module” that can be input by the user is currently 305 meters.

14) On the MEPAS web site (http://mepas.pnl.gov/mepas), there are several links that are broken.

15) When the MEPAS groundwater formulations PDF document (http://mepas.pnl.gov/mepas/formulations/ground_water/groundwater_form.pdf) is viewed on some machines, the equations may not show up correctly.

16) When using the WEAP model with the Fishrand model as an upstream module, WEAP may report a warning that no chemical information was found for a particular constituent and for a given aquatic organism even though the data actually exist.

17) When using two or more MEPAS Air modules linked with ATO Plus Operator, and with the output from Plus Operator linked to the MEPAS Human Exposure module, there is a problem with the wrapper (WrapSpec.exe) and its processing of the exposure module output file. The problem is that the exposure duration changes when the location of either Air module is set greater than 10 km (north or south) away from origin.

18) There are problems with the HQF Aquatic Organism Summary Viewer. For example, when viewing output from the FishRand model, the viewer often shows data that do not exist (especially, when non-organic constituents or organic constituents with low octanol-water partition coefficients are in a simulation where organic constituents with moderate to high octanol-water partition coefficients are used), and it does not show data that do exist at various time periods. Additionally, uncertainty and variability levels are not shown when they should be (e.g. when viewing WEAP output for cases where a FishRand BBF was supplied as input). Also, for tutorial Example 1, the values for fish tissue concentration are incorrectly shown to be 0.0 mg/kg.

19) When using the “Time-varying” option of the RAGS Viewer, the probability percent selection window goes dim when changing the “Measure”, but changing the “Measure” back to the original value does not un-dim the selection window. Additionally, the “Cancel” button does not operate.

20) Sometimes the FRAMES UI will disappear on the user and cannot be brought back up using Windows Task Manager’s “Switch To” button. FRAMES must be killed with Task Manager and then restarted. This will occur when a user creates a scenario and inadvertently leaves a module unconnected while also having a complete chain of connected modules, performs all input on the connected modules, and then clicks the “Go…” button. After clicking the “Ok” button on the “Try connecting this icon to a database icon to acquire applicable models” message and then pressing “Close” on the “Object Info” dialog, FRAMES will disappear and will not come back up. The user will have to kill FRAMES with Windows Task Manager. To avoid this problem, the user should never have an unconnected object while trying to run all modules.

21) Once cannot sample for sensitivity/uncertainty output the total summed (all paths and routes) risk or Hazard Index (HI) for each constituent like could be done in FRAMES 1.6.

22) The graphical viewer help file, “Graphical.htm” is shared by several graphical viewers and is of very little actual help to the user. The help file needs to be updated with content beneficial to the user for each viewer.

23) The “MEPAS Source in…” modules add or subtract source/sink rate at the end of each time-step after solving the mass balance differential equation, rather than as part of the differential equation. This can result in computed concentration and flux errors under certain conditions. There is work underway to correct this error in the near future.

24) The plus operators do not accept appropriate same file-type producing upstream Sync Operator modules as input.

25) The Terrestrial Wildlife Exposure Model (TWEM) does not retrieve all BAFs from the TWEM BAF database.

26) When using the 'TWEM1 Reports' output viewing option of the TWEM model, the values displayed may show zero when there are actually non-zero results. This is believed to be a round-off problem in either TWEM or in CrystalReports.

27) A bug in the ARAMS 1.3/FRAMES 1.6 version of the MEPAS Human Receptor Model pertaining to dermal showering has been fixed in the latest version of ARAMS/FRAMES. The previous version of this model did not account for the effect of large molecular weights in the dermal permeability computation for organic chemicals, but this has been fixed in the current version (i.e. ARAMS 1.4/FRAMES 1.7).