1 / 18

Updating and Converting COHYST Central Model from MODFLOW-96 to MODFLOW-2000

Learn the step-by-step process to update and convert a MODFLOW model from version 96 to 2000 using GMS software, including package comparison and troubleshooting tips.

mullenix
Download Presentation

Updating and Converting COHYST Central Model from MODFLOW-96 to MODFLOW-2000

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. COHYST Update Converting the COHYST Central Model Unit from MODFLOW-96 to MODFLOW-2000 Doug Hallum Nebraska Department of Natural Resources COHYST Modelers Workshop July 18-20, 2007

  2. Outline of Procedure • Gather MODFLOW files • Read “CMUhm_DevPeriod_sim.mfs” into GMS 6.0 • Save project as “TempName.gpr” • Manually update necessary packages with Textpad • Open “TempName.mfs” • Verify the presence and format of each package in GMS • Save “RealFilename.gpr” • Develop well package • Verify output against model documentation • Go to town analyzing everything under the sun

  3. MODFLOW Files

  4. Read into GMS 6.0 • Hit ok regarding .wel file error • Hit yes when prompted to “Convert BCF flow package into the LPF flow package.” • The model should open and look something like this:

  5. Save The New Project File • We may expect GMS to crash and tell us that our information may be lost forever, which may, of course, look something like…

  6. Save The New Project File

  7. Save The New Project File • However, GMS will write many of the necessary packages in the MODFLOW 2000 format, including the “super” (.mfs) file.

  8. Update Packages • Comparing to what we started with, some files have different sizes

  9. Update Packages • The recharge files are different sizes, but both are 653,377 lines long. Are they different?

  10. Update Packages • The stream files are different sizes. Are they different?

  11. Update Packages • What about the ET package?

  12. Update Packages • Note all differences from original packages • Compare format, syntax, etc… • Look at MF2K packages in other models to quantify any differences • Read MODFLOW 88 documentation to find the meaning behind the format • Use Textpad or develop your own macros/scripts to automate updates

  13. Read Updated File into GMS • Open GMS again and read in the “super” file associated with the updated version • Note error specifics when opening and return to Textpad to troubleshoot • Iterate, iterate, iterate…

  14. Save project as “Real FileName.gpr”

  15. Develop Well Package • Get the development period well file from Clint and include in the “RealFilename_MODFLOW” directory • Change name file to recognize development period well file

  16. Verify Model Output • Run model and adjust parameters and/or packages until the model runs and converges • Iterate some more…

  17. Congratulations • Now you have the privilege of analyzing everything under the sun

More Related