• Re: About simulation

    A solution for the freezing simulation toolbar has been implemented in an earlier bugfix, can you check if you have the latest patch (current patch is p6 - May 25th 2011)?

    A tool for searching a node number is not yet implemented. Workaround: Use the classic FEFLOW and reproduce the error message. Here, a red arrow will point at the corresponding node.
  • Re: 'extra' flux resulted from the increased 'residual water depth' (RWD)

    Increasing the residual water depth (RWD) leads to higher effective conductivity values of unsaturated elements. In most cases, this will have an influence on the whole flow pattern, influencing the head distribution, velocity field and finally the boundary fluxes.

    To evaluate this influence it is necessary to compare two models with different RWD, e.g. by looking at the delta of the budget results (the difference cannot be derived from the mathematical solution of only one model)
  • Re: Measure tool

    This feature is not available yet but will be added in a future release.
  • Re: Units problems !

    The total influx can be prescribed as a point source using the well-BC (4th kind BC), unit m3/d.
    To assign the total inflow along a line (e.g., a border section), you need to calculate the length-specific inflow in m2/d from the length of the section (m) and the total flux (m3/d).
    In a 2D model, you can assign this value as a depth integrated boundary condition (m2/d) (in case of an unconfined model, you have to choose the integrated option explicetly).
    In a 3D model, you have to calculate the inflowing darcy velocity (m/d) from the length of the section and the depth of the model.
  • Re: Simulation time!

    There are several possible reasons why the dac-file could be incomplete:
    - the simulation was interrupted prematurely (user abortion, software crash,...)
    - this disk space was not sufficient (you would be notified during the simulation)
    - the file got corrupted after the simulation (e.g. network/ftp/email transmisson)

    Before you have opened the dac, did you check if the simulation ran until the last time step was finished?
  • Re: Variation of results in SS and TS

    Instead of setting an upper limit for the time-step size it might be a better approach to reduce the error tolerance of the model. This will lead to smaller time steps and makes the results of the non-linear iteration (the calculation of the result of the individual time step) more accurate at the same time.
    The error criterion is a relative value that relates to the maximum occuring value (initial condition or boundary condition) of the process variable (e.g. hydraulic head for the flow simulation of Temperature for heat transport simulation). If this max value is 100 m, an error criterion of 0.1e-3 would lead to a (probably) acceptable absolute (mean-square) error of 0.1 m. Of course, depending on the model purpose a smaller valuer might be necessary.
  • Re: transient pathline error

    Hi Laura,
    Is your initial simulation time different to zero? We have identified a malfunction that leads prevents the pathline computation in this case, a soultion is currently developed. If you set the intial time to zero the problem should be resolved.
  • Re: 64 bit compilation VC++ 2010 Pro

    Dear Søren,
    Check if the dll has been succesfully created and - if yes - to manually register it in FEFLOW. The automatic registration of the plug-in is only a convenience feature that is run after the actual compiling step.
  • Re: Pathline computations

    I think you have already perfectly understood the principle. If the steady-state option is chosen, the velocity field is assumed to be constant in time. The resulting tracks are the streamlines.
    If the transient option is chosen, the velocity is regarded to be a function of the time. The resulting tracks are the pathlines.
    For a steady-state model, streamlines and pathlines are identical.