• Re: Horizontally moving shoreline

    There might be even an option without a plug-in: If the river bottom is implemented as a minimum-head constraint for the transfer BC, in the lastest FEFLOW versions (from patch 8 for FEFLOW 7.0), the transfer BC is internally turned off in case that the BC value (river water level) is below the minimum-head constraint (river bed elevation). With this, you can simulate a varying shoreline by simply using time-varying conditions for the water level in connection with a constraint representing the river bottom.
  • Re: Feflow 7 - Set up 2D rectangular grid of exact measurements, then make it 3D?

    For the supermesh, digitize a rectangular box of 1000x100 m. You can do this by activating the polygon option, hitting F2 and typing the coordinates for each corner node. Then switch to 'Quadrilateral mode' in the Supermesh menu and use the 'Transport Mapping' mesh generation algorithm in the Meshing panel with a number of 100000 elements. This will give you the first grid. For later refinement to half-meter elements, select all elements and click 'refine' in the Mesh Geometry toolbar.

    In FEFLOW which is primarily focused on flexible-mesh modelling, the generation of a rectangular grid is a rarely used 'special case' - thus the procedure might be less obvious thanin VM or GV where rectangular grids are (still) the standard.
  • Re: problems importing Observation Points

    The error bars to be drawn in the view require that a confidence interval is defined. Maybe during importing, you import the values, but forget to set or import values for the confidence interval.
  • Re: Node fixing

    Yes, smoothing only affects the selected nodes when a node selection is active.
  • Re: Getting Time step length during PreTimeStep callback

    Hi Eduardo,

    I think the reason is the following (without testing or looking at the actual FEFLOW code):
    OnTimeStepConstraint is called whenever a new time step length is determined. With the predictor-corrector scheme, it may happen that a step is calculated, but the result rejected due to a too large deviation from the previous one. In this case, a new time step length will be set, and OnTimeStepConstraint will be called again. I assume that at this time, the values you get via IfmGetResultsFlowHeadValue are the results of the previous rejected step.

  • Re: Finding time step length on PreTimeStep call back

    Hi Eduardo,

    The actual time step length can only be determined in the OnTimeStepConstraint callback, which might be called several times in a time step. FEFLOW itself cannot know what the final length of a time step will be before it is calculated as - using the predictor-corrector scheme - the simulation may be carried out several times with different time step sizes before actually accepting the result. PreTimeStep will only be called once, so it will not be useful for you. OnTimeStepConstraint, however, is called before the time step is actually simulated, so this should be where you actually put your code. Keep in mind, though, that it may be called several times before FEFLOW proceeds to the next step.


    PS: Merged your two topics.
  • MOVED: Getting Time step length during PreTimeStep callback

    This topic has been moved to [url=http://forum.mikepoweredbydhi.com/index.php?board=12.0]Plug-in/Script Development[/url].

  • Re: obj files from Sketchup 2016 causes Feflow 7 to crash ?


    We haven't used sketchup for a couple of years now, and thus do not have experience with obj files created with it. I personally recently used Blender quite a bit, and I think I also did some tests with obj files produced with it. As Björn says, however, it would be best if you could share the file with support so that we can check what's going wrong.

  • Re: Assigning recharge in time series

    I recommend to consult the help system of the Classic interface in FEFLOW 6.0.
  • Re: Unstructured meshing for tunnels/Elements selections problems...

    Indeed it is tricky to access the elements/nodes when you use points to constrain the meshing process. There are basically two options: Either you create many points in 3D within you zone of interest and use the point map to select the elements, or you use surfaces rather than points for the mesh generation, so that FEFLOW can set up groups of elements etc. However, for the second option you'd have to have CLEAN surfaces for the tunnels, without any intersections or self-intersections, which is sometimes hard to achieve, even with 3D design software.