Jump to content
GMS, SMS, and WMS User Forum


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About khaled_haider

  • Rank
    Senior Member

Profile Information

  • Gender
  • Location
    Syria (Damascus)

Recent Profile Visitors

460 profile views
  1. Event is over due to flow below cutoff value

    Thank you Calberts for answering my question. You helped me a lot. I was a little confused with the shortcut of the Unit of Discharge in Cubic meter per second “CMS”. I am used to the abbreviation m3/s.
  2. Hello, Does anyone know the cause or the meaning of this message” Event … is over due to flow below cutoff value” which appears in WMS Model Wrapper?
  3. The time step must be an integer divisible into 60

    Thanks Chris, I did not notice any significant change in my results when using a Time step = 300 seconds, except for a significant shortcut in the time necessary to complete the simulation. This encouraged me to try even greater values of time steps (for example 600 seconds) to see how this increase can affect the results. Nevertheless, one must be very careful when implementing this increase and must monitor all types of outputs and not focus on a specific output.
  4. Hello, I was trying to run a long-term simulation (for a period of 10 years) in GSSHA. The Precipitation file and the hydrometrological (HMET) file are relatively large. Because I do not want to wait a lot of time and because my meteorological data are hourly, I have chosen the Time step to be 300 seconds. However, the GSSHA Model Checker gave me an Error Message: The time step must be an integer divisible into 60. According to the GSSHA- User’s Manual (Version 1.43 for WMS 6.1), It is possible to choose Time steps which are multiple of 60 sec. Here is a Citation from 2.2 Time Steps and Process Updates: In GSSHA the user specifies the overall model time step, in seconds, that the model uses to loop through he processes, check update times, and update processes. To avoid missing updates of processes, such as rainfall, that may be specified at 1 minute interals, the overall model time step should be integer divisible into 60 seconds or an integer multiple of 60 s (i.e. 5, 10, 15, 20, 30, 60, 120, 180, 300). The model time step also must not be greater than the finest resolution of inputs, such as rainfall (which in my case is hourly). Typical time steps for GSSHA range from 10 to 300 seconds. Smaller time steps may be required for particularly difficult problems. Thanks.
  5. Porosity in MODFLOW and MT3D

    I'm sorry, my last sentence was not correct . the truth is that small values of porosity result in large values of Velocity vectors magnitude.The equation for calculating ground water velocity is: V= KI/n. (Darcy’s law). V stands for "groundwater velocity," K equals the "horizontal hydraulic conductivity," I is the "horizontal hydraulic gradient," and n is the "effective porosity."
  6. Porosity in MODFLOW and MT3D

    Regarding the porosity in MODFLOW, I have noticed that the values of Velocity vectors_Mag (which is produced using the option CCF-> Velocity vectors) are proportional to porosity. Small values of porosity result in small values of Velocity vectors magnitude.
  7. Fonts and Icons in 10.3

    Sean, I believe you can not change the fonts and icon sizes in 10.3, because it is default depending on your display resolution. GMS 10.3 detects your display resolution and appropriately sizes icon bitmaps and fonts. see this link https://www.aquaveo.com/software/gms-whatsnew
  8. How to create complex model including some faults

  9. Input boundary condition

    Junya, if you have several layer and want to define different boundary head for each layer, you can simply use CHD package. You can create new conceptual model with a number of coverages equal to the number of layers. You will define the boundary head for layer one in the first coverage, and the boundary head for layer two in the second coverage, etc… Then you can use layer range –Auto assign Layer (Use layer range) to assign each coverage with its corresponding layer. Finally, you convert the conceptual model (with all applicable coverages) from Map to MODFLOW. I hope, this will help you.
  10. unreadable values of Z-axis

    excuse me, the unreadable values on Z-axis occur when the thickness of the layers is small relative to their horizontal extent.
  11. unreadable values of Z-axis

    Thank you Michael Kennard for your reply on my requests. I would also like to ask if there is a possibility to address the unreadable values of Z-axis when displaying the Cross Sections, especially when the thickness of the layers is large.
  12. Model Checker with SFR2 Package

    Thank you Sean Czarniecki for guiding me to where I can find the errors related to streambed altitude in MODFLOW output file. I have also noticed that not all versions of MODFLOW write down this information in the output file. For example MODFLOW 2000 and MODFLOW LGR do not record such errors in the output file, while MODFLOW 2005, NWT, and USG write down this information under the section / STREAMBED PROPERTIES AND STREAM DIMENSIONS/ REACHES WITH ALTITUDE ERRORS.
  13. Model Checker with SFR2 Package

    Hello Alan Lemon, Thank you for your reply on my messages and my requests. I would like also to ask if it is possible to add another issue to the Model Checker in order to recognize an error that related to the SFR2 Package. I have noticed that the Model Checker does not compare the streambed-elevation (ELEVUP or ELEVDN) with the cell bottom elevation in a similar way as it works with the River Package (RIV1). This means that even if the elevation of the streambed is below the cell bottom elevation, which may cause many problems in some models, the Model Checker still give the green message that there is “No Errors or Warnings found in model inputs”. In order to clarify this issue, I sent you a very simple example as Attachment. Thanks Model_Chekcer_SFR2_versus_River.rar
  14. Mark flooded cells

    Hello, Do anyone know how to make the “Mark flooded cells” appear on my Quadtree Ugrid MODFLOW-USG model when choosing the Contour method to be “Color Fill and Linear”. It does not work . It works only when choosing the “Linear” Contour Method. Thanks
  15. Index is out of range update

    Hello Jack Grayson, Excuse me that I did not send you the model with the issue. However, I can give you a very simple example attached in this message. First, please open the project named “index_is_out_of_range_test.gpr” which is a transient state with 50 stress periods. When you will try to convert the conceptual model Map -> MODFLOW, you will get the error message Index is out of range. Now open the other project named “Index_is_out_of_range_solution” which is also a transient state but with only 5 stress periods. Here you can map the conceptual model to grid mudflow without any problem. Thank you for your replay. Test_index_is_out_of_range.rar solution_index is out of range.rar