• Re: Issue in defining multilayer using IfmSetMultiLayerWellAttrValue Function


    You can use the following script to understand the syntaxis with MLW.

        ## Define Boundary Conditions for Flow
        # NoBC = 0
        # Dirichlet (1st kind) =1
        # Neumann (2nd kind) = 2
        # Cauchy (3rd kind) = 3
        # Single well (4th kind) = 4
        # Gradient-type (only for unsaturated problems) = 5
        BcFlowType = 4

        #Load documents

        #Print all Multilayer Well attributes
        for nNode in range(0,doc.getNumberOfNodes()):

            if doc.getBcFlowType(nNode) == BcFlowType:
                if doc.queryMultiLayerWellInfo(nNode) == None:
                    print(Normal Well BC found")
                    # Print MLW ID, Name, Top Elevation, Bottom Elevation, Top Node, Bottom Node
                    print(MLWInfo.getId(), MLWInfo.getName(), MLWInfo.getTopElevation(),
                        MLWInfo.getBottomElevation(), MLWInfo.getTopNode(), MLWInfo.getBottomNode())
  • Re: Import error in FEFLOW Pluging

    Hi Jimmy,

    The FEFLOW IFM package (both C++ and Python) comes together with the FEFLOW installation. Also FEFLOW should create environmental variables, which makes easy to load the IFM module in your Python script.
    You should simply need to write "import ifm" in your script to load the FEFLOW Python package.

  • Re: Elevation from smesh files ?

    Hi Christian,

    Unfortunately, the workflow is unsupported. The workaround is to copy the X,Y,Z information (typically starting after the second row from the file) to a *.dat file.

  • Re: How to find elements which nearest slice-1?

    The latest FEFLOW 7.4 includes a nodal parameter (Auxiliary data) named "Nodal depth". Such as parameter uses as reference the elevation of Slice 1 to compute the depth. You can easily use the information in any expression as commented above.
  • Re: ifmLake plugin


    IfmLake plug-in uses a nodal distribution named "IfmTransfer" with units [1e-4 1/d] to define the transfer coefficients for the lakes. If you can read more details about this implementation in the user manual (page 2).

    Carlos Rivera
  • Re: FePEST bug: simulated mass concentrations at observation points

    Thanks for reporting!
    Regarding to Bug #1, this somehow happens in the following situation: 1) a new param. definition is created as "one layer adjustable and other tied" and 2) a second param. def. is created and tied to the first group. PEST tool complains that you cannot tied parameter to another existing tied param, which is correct! FePEST manages to create the parameters and groups properly at the beginning. But if you edit any parameter, the groups are somehow recreated not fully correct.
    Solution: You correct manually the tied parameter(s) (from group 2) by tidying up to another parameter, which is not being "adjustable" / "calibrable" (from group 1).

    If you need more details, support team (mike.de@dhigroup.com) is aware of the problematic and has some workarounds.

    Apologizes for the inconvenience. We are planning a correction in the next update.

    Happy new year!
    Carlos Rivera
  • Re: Defining In/outflow on top/bottom layer transient values

    Hi Samia,

    Allowing the creation of the material time-stages through the IFM interface is one of the prioritizes for the future release. There are some workaround, but they require few more extra code lines.

  • Re: Introduce gaps in time series via ifm

    Maybe it is worthy for other users: you can work with value = float("nan") and pass this to the API function in order to create the power value. I think a numpy NAN definition should also work.

  • Re: Generating 3D Pilot Points


    did you figure out a solution to the mentioned problem? Otherwise let us talk in detail through the official support channel (mike@dhigroup.com).

    Cheers, Carlos
  • Re: python scripts and spatial head-difference observations

    Hi Stephen,

    Actually FePEST does not use obs2obs.exe, since we have our own implementation. The easiest workflow is to connect the time series of head measurements to an existing observation point in the FEM file. Later in FePEST, you can create an Observation Definition, which depends on head differences (TIME1 - TIME2). By default the head differences are defined based on consecutive temporal records. HOWEVER, you can manipulate later the table, e.g. in Excel, and edit the time column (e.g. TIME - TIME INITIALS or anything else).