Marcelo Lago Vice-President

There is a software tool that can do this seasonal type of average at

http://www.lago-consulting.com/hydroperiod_from_microtopography.html

It looks like an application for MIKESHE/MIKE11 instead of one for MIKE11 stand alone.

If you need to define the most likely MIKE11 flow paths inside the floodplain from the DEM, you may want to try Fill Sinks Plus at http://www.lago-consulting.com/fill_sinks_plus.html

Just FYI, we have been getting similar errors and there is not dots in the file names.

The errors looks always like

[b]ERROR  : OPEN OF UNFORMATTED OUTPUT FILE FAILED:

          Cannot open the file (invalid path or read/write-protected directory[/b]

and it happens for files with extensions fif, frf, and hot.

Curiously, it happens only at a dedicated xeon-processor workstation (see hardware details at http://www.passmark.com/baselines/V8/display.php?id=35220142111) with Windows 7 Pro. Other I7 PCs have not shown this error so far.

I am aware of the following differences:

1) MIKESHE grid is squared as in MIKE21 classic, so, it can not be a flexible mesh as in MIKEFLOOD.
2) MIKEFLOOD do not have groundwater component as MIKE SHE
3) MIKESHE Overland Flow Component uses a Diffusive wave type of approach mean while MIKE21 in MIKE FLOOD uses a more dynamic approach.
4) MIKESHE uses a more detail approach to consider Evapotranspiration. This together with the groundwater, unsaturated, and demand-based irrigation components make it more suitable for long term simulations.

I hope this helps!

Regardless the running time of both methods, I am trying to stay away from the SOR method. This method may not converge, and you may have mass balance errors when this happens.

I hope this helps.

In the MIKEZERO Toolbox, you can compute time-averaged maps from the MIKE SHE output. The steps to do this are:

1) File -> New -> File
2) MIKE Zero ->  MIKE Zero Toolbox
3) Statistics -> TxStat and select further options from there

Alternatively, we developed a tool that allows you to do other types of statistics. You could also choose to have a higher resolution topo map for the processing. You can learn more about this tool at

http://www.lago-consulting.com/hydroperiod_from_microtopography.html
 

I have solved this issue before by increasing the depth of the UZ layer. In our models in Florida, USA, this depth goes 30 meter below the ground in order to avoid this error message. I imagine that in other areas with steep topography you may need to go deeper.

I hope this helps.

Since MIKE SHE only have UZ conditions on top of the SZ, I would try to look at the UZ results for perched conditions. I recall seen in the UZ results an intermediate clay soil layer almost fully saturated as a consequence of having a higher capillary pressure. You may see something similar if you have a soil layer of high conductivity (potential perched aquifer) on top of a low conductivity soil layer.

Another thing to consider is that the UZ flow in MIKE SHE is only in the vertical direction. So, there is no lateral movement of the UZ perched water between neighbor grid cells.

I hope this helps.

You could try to understand better the source of the error by producing Map Outputs from the Water Balance Calculation Tool. The water balance type "Map Output: Total error" with type "Accumulated" would give you an idea of the area with biggest errors. If you have several Irrigation command areas, you would know where to take a closer look. Other types of Map Outputs can tell you if the error is mostly produced in the OL, UZ or SZ component, and in the latest case, in what SZ layer.

If you are using single or shallow well as your source type, you may want to avoid that your SZ cells become dry.  So, the "Max. rate" can not be to high, the screening interval need to include aquifers (and not be inside a confining unit), and you can set the Max depth to water enough above the bottom.

I hope this helps. 

The conversion from dfs2 to dfs0 can be conducted by using the MIKE ZERO toolbox.

Open MIKE ZERO>new file>MIKE ZERO>MIKE ZERO Toolbox (.mzt)> Ok

Extraction>Timeseries from 2D files> ...

You would need to specify the grid cell indexes (x,y) of the points in form of a table.

Alternatively, you can try a tool that give you the dfs0 files after specifying a point shape file and a dfs2/dfs3 file at

[url=http://www.lago-consulting.com/shape_plus_dfs23_to_dfs0.html]http://www.lago-consulting.com/shape_plus_dfs23_to_dfs0.html[/url]