• Re: Time Series Batch Conversion fail

    Hi Jake,

    It seems something in the tool setup or the excel file is not liked by the tool but it's difficult to say what exactly.

    I managed to reproduce your issue by activating the "Date/time format" option (1st option: 'Date and time values in one column or across multiple columns') in the 'Time Description' dialog. After I deactivated that option I was able to proceed to the 'Data Description' dialog and eventually run the tool (I used the Help example data).

    But I guess it could also be related to other issues e.g. the way the date/time column(s) has been defined, or strange symbols in your data,..
    if the problem persists can you share an attachment of your setup files to have a look and try to reproduce?

    Best regards
  • Re: invalid file name error when using Grd2MIke

    I think it is related to read access issue if the .asc file is opened in ArcGIS simultaneously.
    If you close ArcGIS (or any other s/w accessing the file) you should be able to proceed to the next dialog of the tool. I just reproduced and it is working as expected.

    1. Unfortunately this is a code issue for 'water content in unsaturated zone' gridded results (only the first cell along the profile line is actually used). I've reported to our development team so I expect it will be fixed in a future release/update. Meanwhile the workaround is to use the MIKE Zero Extraction tool 'Profileseries from 3D file' (you need to define the start-end profile points coordinates (for one ore more profiles) and an appropriate spacing, probably similar to your model domain cell size to make sure you get all the detail along the profile).
    2. You can use the MIKE Zero Extraction tool '2D Grid from 3D file'. One of the dialogs of this tool allows to specify a desired slice/plane (XZ, YZ or ZY) from the 3D dfs3 file. The output of this would be a time varying dfs2 grid file which could then be loaded in Result Viewer or Plot Composer to create a video (using the 'Video Forward' button at the "Result Viewer Tools" toolbar).
    3. Postprocessing can normally be done using the Grid Editor tools: if you open the dfs2/dfs3 files, the Grid Editor has various postprocessing tools (e.g. select cells by polygon, set/add/subtract/multiply/divide cell values by a user-defined value, apply expression/equation calculations using multiple functions, calculate statistics, copy/add/multiply different grid dfs2 files, ..).
    For visualization we would normally use Result Viewer (e.g. for creating videos of a certain output parameter) or Plot Composer (e.g. for creating videos of scenarios comparison or simultaneous animation of different types of outputs).
    If you still want to modify/visualize the dfs2/dfs3 files outside MIKE, since these are binary files, you would need to convert them to other formats. E.g. you could use the 'GIS' tools in the MIKE Zero toolbox or some conversion tools in the MIKE Tools webpage (e.g. MIKE2Shape): https://www.mikepoweredbydhi.com/download/mike-by-dhi-tools.
    Hope this helps.
  • Re: Boundary flow

    Hi Diana,
    I don't know if you refer to overland or groundwater boundary but if you would like not to get boundary flow, you would first need to check the definition of your model boundary conditions to make sure they are reasonable, e.g. closed where appropriate. Then there may be different approaches in MIKE SHE to constrain flows.
    E.g. for overland boundary flow you could apply the 'Separated overland flow areas' option to make sure no overland flow occurs from/to these areas.
    If you refer to groundwater boundary flow you could apply a closed boundary condition or an impermeable lense.
    Hope this helps.
  • Re: soil conditions

    Hi Diana,
    Don't know which UZ method you are applying (2-Layer/Gravity/Richards) but maybe the UZ Saturated hydraulic conductivity has high values resulting in quick response to groundwater recharge/river discharge. You could try reducing it (and maybe the SZ hydraulic conductivity too) in order to reduce the infiltration/recharge and get a slower discharge response.
    Hope this helps.
  • Re: How to View Layers?

    I believe you would need the Geoscene 3D extension (i.e. a Geoscene 3D license running on the same pc) in order to view the SZ computational layers in 3D, which is not provided for free with MIKE SHE. Therefore you would need to contact I-GIS regarding Geoscene 3D students license.
    A partial workaround may be to define dummy supervision wells at desired parts of your model domain. This can be done in the .WEL file at the MIKE SHE Pumping Wells option. After you define the Well locations coordinates then at the upper right graph, a view of the SZ layers structure should appear.

    MIKE SHE is a flexible modelling framework that can model each hydrological process as well as combine the hydrological processes and numerical methods depending on the requirements of your application and data availability.
    Thus there may be different approaches to get hydrograph results somewhere in your river basin (or the outlet) depending on each case study.
    For instance you could couple MIKE SHE and MIKE HYDRO River to assess in more detail the dynamic interaction between the river model and MIKE SHE Overland/Groundwater components. Alternatively you could rely entirely in MIKE SHE, particularly the Overland flow component by applying either a Finite Difference or Subcatchment-based solution method and then use the MIKE SHE Water Balance Analysis tool to get hydrograph results for a sub-basin or the whole basin.

    The minimum data requirements would probably include rainfall/reference evapotranspiration parameters, the DEM and a shapefile of your model domain. You could of course add as much data you have available (e.g. land uses, distributed soil/geology, irrigation, drainage network, abstractions, ..).

    Hope this answers your question ( ? )
  • Re: Error in creating a dfs2 from using dfs2+dfs0 -> dfs2

    You would need to convert the 5-digit IDs to consecutive positive integer values (so 1, 2, 3, .. up to 178) for the grid cells/timeseries, otherwise this error is triggered.
  • Re: Standard boundaries

    Hi Medria,
    This may come a bit late but it may also be relevant to other users. The error says there is no open boundary defined for the upstream end. A discharge (or water level) inflow boundary condition is required for the upstream end while a Q-H or water level boundary condition is required for the downstream end. The distributed source boundaries are considered as lateral inflow (or outflow) boundaries and so is rainfall. Normally rainfall is fed in a Rainfall Runoff model like NAM (is that what you wanted to do?) and subsequently linked with or fed into the 1D river model.
    Hope this helps.

    I've never tried this in Autocal but it should be possible. I guess you need to run both extraction and postprocessing executables in a sequence, either directly or via a bat file e.g:
    MSHE_Wbl_Ex.exe //apv My_WB_areas.WBL
    MSHE_Wbl_Post.exe //apv My_WB_areas.WBL 1
    MSHE_Wbl_Post.exe //apv My_WB_areas.WBL 1
    MSHE_Wbl_Post.exe //apv My_WB_areas.WBL 2
    In the above, the first command runs the Extraction phase of the water balance utility, while the subsequent commands run the Post-processing items in the water balance file. The number after the water balance file name indicates which Post-processing item to run. This is discussed in MIKE SHE User Guide, Section 3.5 (Using Batch Files) and more in-depth in Section 6.2 (Calculating Water Balances in Batch Mode).
    Otherwise it is better to build up the autocal arguments step-by-step so that you ensure each argument is working as expected.
    Hope this helps.