-
PS. In Python, the function returns a list with the node number and the distance to the point provided.
-
Hi Javier,
I have double checked the function. It properly returns a node number. I think your problem is the coordinate system. FEFLOW works with the local coordinate system, thus you will need to subtract the origin (X,Y) to the coordinates before you pass these values to the IfmFindNodeAtXY function.
node = IfmFindNodeAtXY(m_pDoc, 352, 1715, pointer1);
IfmInfo(m_pDoc, "Node: %i", node);
The second statement will print the number on the Log panel. After FEFLOW 6.2 (p12), we introduced two more functions for searching nodes or elements:
int (*findElementAtXYZ) (IfmHandle, double x, double y, double z);
int (*findNodeAtXYZ) (IfmHandle, double x, double y, double z, double* dist);
If you need just to know the number of the node and/or element, you can simply create a nodal/elemental expression distribution in FEFLOW GUI. Remember to decrease one unit to the number you get (to be in concordance with C++ counts from zero).
Cheers,
Carlos
-
Dear all,
This bug is already fixed in the new update # 3 of FEFLOW 7.0. The correct link associated is ensured in the MS template.
Best,
Carlos
-
Dear Heermann,
I am reactivating this post since we have the similar questions from other users. You can use any python script during the FePEST run for the parameter estimation. Once you create all your PEST files within FePEST, you will see a set of several batch files are also created. There is one in specific named "run_model.bat", where you can place your script line, e.g. python _MyScript.py. The script can run either before or after the FEFLOW run. It is mandatory the script is named with "_" at the beginning to avoid PEST/FePEST deleting the file in between consecutive iterations.
Best,
Carlos
-
Dear Rapheul,
Indeed, there has been a big progress in this topic. We have released last year the official plug-in to couple FEFLOW and PHREEQC. You can find the information under the Groundwater and Porous Media tool section in our website: http://www.mikepoweredbydhi.com/download/mike-by-dhi-tools
Best regards,
Carlos
-
Hi,
In addition, you can always get the list of complete functions from the documentp.h, which is included automatically in each IFM project. You can also see when each function was implemented.
Carlos
-
Hi,
Unfortunately, this is a bug in FEFLOW 7.0. You can easily continue your work with the following steps:
1) Open the properties of the plug-in project.
2) Go to COMMON Properties
3) You will see that there is a link still related to FEFLOW 6.2. Remove this link.
4) Add the new link now with FEFLOW 7.0. Typically this is located under "C:\Users\Public\Documents\DHI FEFLOW 7.0\sdk\ifm\lib". You just need to take the right version of your Microsoft Visual Studio and include file "ifm.vcxproj".
5) Clean solution and rebuild everything again.
Carlos
-
Hi,
This is a bug in FEFLOW 7.0. Please download patch 1, which already includes this correction.
Carlos
-
Hi Karanka,
This feature is not a plug-in. You will find it directly in the Parameter Estimation software (FePEST interface). If you attach a FEFLOW FEM file to FePEST, where the option "Budget Charting Mode" is active for a a nodal selection, you would be able to create an observation definition for the calibration based on the Rate/Period budget information. Here also you can import a POW file with the times and budget information.
Regards,
Carlos
-
Hi Karanka,
I would like to re-open this forum post. [u][i][b]Correction[/b][/i][/u]: Since FEFLOW 6.2 (p8), you have access to the full budget (rate or period). In FePEST we have shortly implemented a new feature, where you can provide a time series (*.pow file) to be used directly for the model calibration.
Regards,
Carlos