web
You’re offline. This is a read only version of the page.
close
Please wait...
×

Error

  • Re: Input data of FEFOLW 6.1

    Yes, I think you're right - we'll make sure to add a screencast for the next release.
    The procedure for 1D interpolation is the following:
    - Load a point map with the data of the known points (e.g., gauging stations) to the maps panel.
    - Load a line map with the 1D geometry (e.g., river).
    - Use Link to parameter on the point map and link to the corresponding boundary condition.
    - In the link properties, choose the line map as the selection map.
    - Also in the link properties, choose 1D Linear Interpolation as the interpolation method.
  • Re: Input data of FEFOLW 6.1

    Lamm,

    I recommend that you have a look at the User Manual and the corresponding screencasts (on http://www.feflow.com/screencast.html or http://www.youtube.com/playlist?list=PL0C38F6F0D7D36AAE). I think they will answer all your questions.

    Good luck!
    Peter
  • Re: Concerning the time of simulated results

    There's also also 'Initial Time' right below the initial time step length and the final time.
  • Re: Concerning the time of simulated results

    Lamm,
    There are different possibilities for this:
    - You calculate the time based on a calendar.
    - You use Excel, convert your start date to a number (via cell format) and add the simulation time from FEFLOW. Then convert back into a date.
    - You use the number you get in Excel from converting your starting date as start time of the FEFLOW simulation. Same for the end time. Then you can convert any date into a number and it will correspond to your relative simulation time in FEFLOW. This is because Excel internally uses the number of days since Jan 1st, 1900 (1904 on Macintosh) to store dates.
    - You use FEFLOW 6.1 - there you can at least use real dates for display.

    Good luck!
    Peter
  • Re: time varying heat input rate in Feflow 6.0 ?

    To define a time-varying heat-input rate in FEFLOW 6.0 Classic, the corresponding time series has to be selected in the light-blue box BEFORE clicking on the BHE button. Please note that the 'heat input rate' relates to the amount of energy added per time with relation to the chosen reference temperature (in Heat Transport Initials). So it is not - as often thought - the power extracted or injected via the BHE.
  • Re: Inactive elements ?

    Not yet, but we're in the process of developing this option.
  • Re: Continuous and uncontinuous layer

    At the current stage, all layers in FEFLOW have to be continuous. Thus for pinch-outs, numerical layers have to be different from stratigraphic layers. In the most typical case, numerical layers are continued with a minimum thickness outside the areas where their corrsponding stratigraphic layers exist. Material properties etc. are assigned as spatially varying for the different zones.
  • Re: simulated hydraulic heads always too high

    Whenever doing calibration, you will be confronted with some non-uniqueness of the solution. In the simplest case, you might not know whether you need to decrease recharge or increase conductivity. If confindence levels on both sets of input data are equally low and head observations are the only calibration targets, there is no way to do the 'right' thing. So either you manage to come up with additional calibration target or parameter data, or you need to at least qualitatively think about what it would mean for your results (in terms of decision support done with the model, not in terms of resulting hydraulic heads!) if your decision was wrong. Going further, fully-blown uncertainty analysis (e.g., applying PEST) could help to identify parameter correlations and result uncertainty.
  • Re: extremely high calculated time (BHE)

    With respect to BHE simulation, you can think about using the semi-analytical Eskilsson-Claesson approach rather than the fully numerical Al-Khoury method.

    Set the iteration number per time step to 1, but make up for it with a much stricter error criterion (maximum error norm, small value) than the default one to force a short time step. Additional iterations tend to not improve the solution within the BHE, thus shorter time steps with just one iteration are a better approach most of the times.
  • Re: How to export slice-data trace view?

    Hi Héctor,

    Right-click in the data-trace chart and choosing properties should give you the needed export. The curve can be stored as .pow and easily be opened in a spread sheet program.

    Bastian