Bruce Campbell

Members
  • Content count

    100
  • Joined

  • Last visited

Community Reputation

-2 Poor

About Bruce Campbell

  • Rank
    Senior Member

Contact Methods

  • ICQ
    0
  1. Hi Michael -- Thanks for the quick response. How about the name of a well or observation point - I have some long names from our database. As much as 30-50 characters with punctuation such as parentheses, pound signs, and periods. Could these long names be a problem? I can replace them with simple consecutive numbers.
  2. Hi -- How many significant figures does GMS use when assigning coordinate locations for groundwater level observations? I've got a little over 400,000 groundwater level observations in a GMS 10.1.4 model and having trouble using PEST outside of GMS. I think what's happening is GMS is creating duplicate locations for the wells. I have 8 significant figures on the X and Y coordinates and there are no duplicates. However, if GMS is only using the first 2 or 3 of these significant figures in the coordinates, I'll have lots of duplicates.
  3. Hi -- I'm using GMS 10.1.4 and having trouble with how GMS is assigning the elevations to SFR2 segments. 1) I have all of the SFR2 arcs in the top layer. 2) Created the top elevation of the top layer and the SFR2 "Elevup" and "Elevdn" from the same raster. 3) Interpolated the raster to a 2D Grid and imported that into the Top Elevations for Layer 1 4) Used same raster for the "Elevup" and Elevdn" fields in the SFR2 attribute table in the Map Module. Mapped the coverage to MODFLOW The problem I'm having seems to center on how the SFR2 elevations are produced when the "Map to MODFLOW" comand is run. I'm getting thousands of errors - "the stream elevation is below the cell bottom" When I check the raster (the same one is used to produce the top elevation of the upper layer and the SFR2 "Elevup" and Elevdn") the top elevation honors the raster. However, the elevations produced from the raster by the SFR2 process (Map to MODFLOW) are, in many cases lower or much lower than the raster. Ideally, I would think that the two different elevations 1) the top of the top layer and 2) the SFR2 segment elevations would match closely, since they were derived from the same raster. Any insights would be appreciated.
  4. Hi -- There's a new version of MODFLOW-NWT that was posted on the USGS Office of Groundwater web page this month: http://water.usgs.gov/ogw/modflow-nwt/ This is version 1.1.2 I noticed the H5 version in GMS is 1.0.9
  5. Got a solution using the Multi-Node Well1 (MNW!) package. Set the MNW1 package coverage up using the top and bottom of the well screen(s) and map the coverage to MODFLOW. Switch to the IJK view mode in the MODFLOW MNW1 package and there are the layer assignments (K). I J K Name 475 513 3 AK- 28 396 536 3 AK- 30 478 62 3 AK- 31 476 59 3 AK- 32 292 261 5 AK- 36 274 298 5 AK- 37 384 198 3 AK- 38 243 291 3 AK- 41
  6. I've got several thousand wells with single or multiple groundwater levels that I want to use for model calibration purposes. The problem is assigning the wells to the 5 aquifers in the model. I have coordinates and the altitude of the top of the top screen and the altitude of the bottom of the bottom screen. We constructed the framework for the model in ARCHydro so I don't have solids in GMS. Is there an automated way to assign the wells to the aquifers or is it one-by-one by hand? But maybe there's a way to do it ARCHydro?
  7. Hi -- I've got an existing GMS MODFLOW model with a lot (hundreds) of wells that have associated transient pumping data. The model is about 8 years out of date and I need to add new water-use data to the existing wells in the GMS files. Was thinking I could export the data from the Map coverages and maybe pull the old data into an Access database and put the new data together with the old data. However, when I export the coverage with the old data from GMS and take a look at the *.dbf file, all of the flow rates are 0.0. Any ideas?
  8. Thanks Bill, this worked very well. I didn't notice it in the Global Options menu. Probably lot's of things in there I'm missing!
  9. Hi Alan -- That would be great!
  10. Hi -- Have a suggestion for assigning the altitudes for the various MODFLOW surface-water packages such as SFR2, STR, DRN, or RIV. In simple models this is usually not a problem but in more complex models with topography that varies across the model, it's a challenge. Using TIN's to assign the altitudes works well usually but I've had it lead to problems with hundreds to thousands of model cells when the process assigns the surface water feature to a altitude below the bottom of the cell. I suspect this is caused by the various interpolation steps required to get the cell altitudes into a TIN and then into a MODFLOW input file. I've got a Python script that goes through the discretization file and pulls the top of each cell that has a surface water feature (streams or rivers) and uses the top of the cell altitude directly to build the MODFLOW input without any interpolation. Of course doing this means it's an extra chore to get these data back into GMS and use the functionality of the program. Just an idea, but seems like a better way to assign the altitudes without multiple interpretation steps.
  11. Hi -- I've got something that looks like a bug when I run the "Export Native Text" command. The problem is in the file that's output for the STR package. The STR inputs for Discharge, Conductance and the Top and Bottom altitudes for the individual stream reaches are pushed together without spaces. Here's an example from the beginning of the file: 70883 14353 3 0 0 128390.4 740 0 70883 0 0 8 8 76 1 1 0.0313.580463 7448.3589313.579456313.580463 8 7 76 1 2 0.0344.32457613513.4918344.323569344.324576 8 7 75 1 3 0.0316.22881841210.9933 316.22781316.228818 8 7 74 1 4 0.0292.13801741757.7071 292.13701292.138017 8 7 73 1 5 0.0272.52672941382.5175272.525722272.526729 This gives an error when I attempt to run the model outside of GMS.
  12. Hi Alan -- Worked on it some more today, simplifying the model to see if the layer errors showed up when the "Solids to MODFLOW" command was run. Here's what we found: 1) rebuilt the solids and grid using only two layers (Rock and Coastal Plane). The errors around the windows do not occur. 2) Errors do occur when using Aquifers but no Confining Units. 3) tried 3 layers. Rock, Cretaceous, and Tertiary - with no errors 4) the errors appear to occur when the model gets to 4 layers and get worse as more layers area added. It doesn’t seem to matter which 4 layers.
  13. Hi - Am having a problem with the solids to MODFLOW process. The model a number of "windows" where the aquifer and confining unit material has been eroded away. When we go through the solids building process, the solids appear to be "correct" overall and at the edges of the windows. However, when we run the "Solids to MODFLOW" process, the aquifer, confining unit and basal unit altitudes at the edges of the windows are much too low. We've tried a number a ways to construct the solids and run the "Solids to MODFLOW" process but keep getting the errors. Would appreciate any input. We've uploaded the files to your FTP site: @ Aiken.Zip
  14. Hi -- I'm looking at new computers and wanted to see if the Developers had any recommendations on processors, RAM, video cards, etc.
  15. Hi -- Would it be possible to include some of the UZF Package inputs as PEST parameters? Was thinking about the infiltration and ET rates specifically.