-
Hi Bjorn,
Using windows 10 and FEFLOW6.2/64 bits.
I'm having problems with the pointers from the MNW functions. The plugin have been using the pointer info before it is populated in my plugin, which makes me think that the compiler optimization has somehow changed the sequence of commands. As a result, lots of NaN's, negative node indexes and strange numbers appears throughout the model run. When I use it with the debug version, it works perfectly without any problem.
-
Hi All,
I've made a plugin that is presenting different behaviors between the debug and release profiles.
I suspect that this may be due to compiler optimization settings.
Would you know whether these settings are different between profiles? What else is different?
Thanks
Eduardo
-
Hi All,
I tried to compile a simple plugin using Intel Compilers and, without messing around with the template, I was not successful.
Can this actually be done? (i.e. can a plugin compiled using Intel work on feflow?)
If yes, what changes to the template do I need to perform.
If no, could I use Intel MKL libraries without the Intel Compiler?
Regards,
Eduardo
-
Hi All,
Do you guys know whether the FEFLOW IFM templates are ready for Visual Studio 2017?
If yes, are they installed automatically when we install FEFLOW 7.1?
Thanks for the help,
Eduardo
-
Hi All,
there is a bug with IfmFindNodeAtXYZ on FEFLOW 7.1p2, 64bit
Everytime I run a plugin with this function(using obviously the same coordinates), it gives me a different node.
Currently using 100000 for search distance, I wonder if it would improve with smaller value.
-
Hi guys,
Can anyone tell me where I can find the documentation for the 7.1 ASCII file formats? (Assuming it exists)
Regards,
Eduardo
-
Hi Bjorn,
I have FEFLOW 7.1, update 1 (according to the online update it is the latest one).
I'm trying to use the 64 bit, but couldn't go that far as the plugin was not compiling
There has been problems with the IFM templates since version 7.0, and now it seems worse.
Cheers,
Eduardo
-
Hi all,
I've been trying to create an IFM plugin (MSVC2015 c++) using the templates from FEFLOW 7.1, and every time I try to compile I got this error:
1>LINK : fatal error LNK1181: cannot open input file 'C:\Users\Public\Documents\DHI FEFLOW 7.1\sdk\ifm\lib\vc14\Win32\Debug\ifm.lib'
I'm trying to compile in 64 bits, and obviously the project is pointing to the 32-bit version (which is in correct).
In the past I've manage to go around these bugs (by the way, the 7.1 templates are pointing to 7.0 folders) by messing around with the .vcxproj file, but no luck this far.
Has anyone experienced same problem?
Regards,
Eduardo
-
Hi Bjorn,
I'm using 6.2. In the end I've found a rather unellegant way around, by setting the conductivity as the discrete element index, exporting as a text file to retrieve the indexes.
Cheers,
Eduardo
-
Hi All,
I'm trying to adjust the conductivities of different discrete features using IfmSetFracFlowConductivity.
However I'm having trouble figuring out the discrete feature ID (nFracElement).
I've tried to export all discrete features as a table, but neither the columns ID or DF match the nFracElement
How do I figure out which discrete feature elements compose one discrete feature group?
Regards,
Eduardo