• Re: trouble with mesh generation

    I'm not 100% sure about the reason for your problems. You should avoid, however, line add-ins whose endpoints are extremely close to an edge of the superelement polygon. If you need these conditions, you should place a vertex at the polygon edge and make sure that the end point of the line is exactly in the same location. Add-ins crossing the polygon edges in reasonable angles should not cause problems. Hope this helps.
  • Re: feflow is not a really 3D-model? but a integration of 2D-models?

    FEFLOW is a full 3D model, i.e., all basic equations are solved in three dimensions. The discretization in 3D, however, is based on a layer concept. This makes the data input much easier.
  • Re: Reverse flow field

    Just to clarify: Zebra's answer was related to the corresponding settings for FEFLOW. Unfortunately I do not know whether MODFLOW or one of the MODFLOW user interfaces is capable of doing backward transport simlulation.
  • Re: about modeling geothermal system

    Generally speaking, the answer to your first question is 'yes'. For discussing details, we'd need some more information.
  • Re: about horizonal well

    You can easily use the discrete feature elements in FEFLOW for this purpose. Just put 1D elements for the bores of the horizontal well (or 'Ranney' well), and put the total abstraction as a well boundary condition to the central shaft.

    Please note that the FEFLOW Web Forum is a user community, and all the forum members provide answers to your questions voluntarily. Therefore it can easily be the case that you do not get an answer in an instant. The more specific your question is, and the more the others have the impression that you are also willing to share your knowledge, the higher the probability that someone helps you soon.

    Before starting a new thread, please use the search function. Looking for 'horizontal well', you can easily find the following thread: http://feflow.info/forum/index.php/topic,64.0.html
  • Re: IFM callback that enables capture of non convergence

    I normally log my batch runs (use option "-log fileName.err"). If the model doesn't converge, a note will be written to that file. You can manually inspect those log files or write a little code that reads and checks them (depending on the number of runs your dealing with) after your batch run.

    As far as I know, that's the only way to check for convergence. It would be nice if the Error Norm History was saved in the DAC file, since that would provide more information.

    Hope that helps, Chris
  • Re: Feflow manuals and whitepapers - download

    We had completely revised our websites. Therefore the download pages were down for a while. You find the manuals on http://www.feflow.info/index.php?id=28 now.

    Cheers,
    Peter
  • Re: 3rd type boundary conditions

    I am having the same issue as above.

    Cauchy boundary inflow rates are large and do not change with in-transfer rate.  Even when it is set to zero.  How do I scale the stream conductivity (in this direction)?? I used the constraint method.. but this is undesirable. I still want to have inflow from streams, but just need to scale the magnitude somehow.

    Thanks in advance for your reply.

    Blair.
  • Re: shp to trp

    Thank you Gianmarco for your useful tip. It worked very well and I could finish my work yesterday.
    Best regards,
    Vlad
  • shp to trp

    Could please anyone help me with the transformation of SHP-point-files into trp-files for PEST-observations? I managed to import SHP-points as normal observation points into Feflow an than export them as trp-files, but the third column remains 0.00000. Thanks in advance, Vlad