Denim Umeshkumar Anajwala

Hello there,

This is my first time using MIKE21 and I'm using it to model flooding in a section of the Fraser River (BC). I haven't ran into any problems yet until the very last step: defining the output file. I get the error of wrong dimension of output file and spent several hours trying to figure out why this is happening. I'll do my best to explain what I've done up until now.

I obtained a .gdb surface model and extracted the xyz coordinates on a 10mx10m using ArcGIS. Using this data I defined the bathymetry on a 35mx35m grid with 194 grid cells in the X-direction and 419 grid cells in the Y-direction. Any cells in the bathymetry data that had no elevation data were filled with "land values". After modifying the bathymetry to my satisfaction I saved the file and began a .m21 file to begin defining the simulation parameters.

Everything went well until I got to the last tab "Results" where I defined a type 2 output file. The program automatically detected the size of my generated grid (194 cells by 419 cells) and number of time steps (72). For some reason I get the error of wrong dimension of output file. I've tried changing the range of the cells for the output but nothing seems to work. I still get the same error for a type 1 output file (line series).

Any suggestions would be appreciated.

Steven

Hi Lamm,
There's a detailed description of the workflows for the different options in the FEFLOW help system: In the tree on the left-hand side, go to Workflows -> Model Setup -> Assignment of Time-Varying Material Properties.

I hope this can help!
Peter

Hi Lamm,

There's an overview of all the different options for assigning time-varying material data in chapter 10.10 in the User Manual (also available from http://feflow.com/manuals.html).

Peter

In the typical case, the bottom elevation is estimated based on borehole logs showing the stratigraphy. From this, the hydrogeological system can be conceputalized, and the model can follow this concept. There will be no general rule whether the bottom elevation follows the shape of the top or not. This highly depends on the geological setting you're working in.

Hi Quinn,

You're right that this point is not perfectly clear in the help system. I've now added the following paragraph (for the upcoming version 6.2):

[color=green]In 2D axisymmetric models, the flux boundary condition has the unit [L/T] as well. In contrast to the cross-sectional case, L2 represents the circumference, i.e. the local horizontal coordinate x multiplied with 2 and Pi. [/color]

I hope this will help to clarify the question.

Peter

I'm not sure if I got this right, but if the right-hand side of the outer boundary is inclined instead of vertical then you'd have a section of a truncated cone. No problem with this.

This actually seems to be the best idea. If you plan for particle tracking and/or transport simultions, make sure the low k zone is at least two elements wide. To be able to test further hypotheses, you might also want to include enough small elements to be able to do three layers - permeable on the sides, impermeable in the core of the fault.

You're right - I apologize. I had read your message to quickly, thinking that you'd be asking for nodes -> elements... but it's the other way round. There's currently no workaround for this.

The editor will always work on ALL selected locations. If you would like to edit a single multi-layer well only, make sure you select only the corresponding edges.

If you really want to use quads in such a case, you'd have to first subdivide your model area into quadrilateral supermesh polygons. Then FEFLOW will be able to generate a quad mesh.