adacovsk

void CTmaDevelopmentV2::PreTimeStep (IfmDocument pDoc) with IfmSetZ

While the elevation values are updated (also the continuous, fringe, and isolines), but not the actual 3d graphics

Thanks,

Adam

Thanks Peter. Is there another way of going about updating the display?

Hi,

Just curious how I can use IfmUpdateDisplay in a callback so that I can see updates to the mesh. Currently I have to reload the file in order for the display to update, and I would rather update it during the simulation so the user can see changes to the geometry. I've attached an example of what the plug-in does. Not sure how to pass IfmModule pMod in a callback??

Thanks,

Adam

I've had issues trying to assign multilayer wells in FEFLOW 7.0 too, but works fine in FEFLOW 6.2... Hopefully the developers can offer insight

Timestep size, timestepping growth, mesh refinement, the solver, the predictor-corrector scheme can make a difference with the error... There are lots of different ways to reduce the error! Probably the best thing to fix is the mesh refinement, especially in regions of high elevation gradients from my experience, and the type of boundary condition you use could also impact it.

Hi,

Getting problems with the sample plug-in "ifm_prop" with the constructor, namely m_nInt(5), m_dDouble(3.14), etc. and I'm not sure how to fix it.

Thanks

Adam

Hi,

I thought I read somewhere about some new Timeseries ifm functions but I can't find anything.

Also, through FEFLOW, I'm trying to use Nodal expressions to assign timeseries, but I seem to be doing it wrong. What is the syntax to assign timeseries values via the expressoin editor?

Edit: Okay, so I figured out this: TS.1@(Time) works, but does not update until the expression is applied again to the nodes... Trying to figure out how to automatically update for each timestep.

Thanks,

Adam

With the unstructured meshing, it provides me element selections so I can assign material properties to specific layers via a csv file... But maybe there an easier way through the interface?

Also, recommendation would be to have Layer10 to follow Layer9 rather than follow Layer1.
Currently, this happens: Layer1, Layer10, Layer11, Layer2, etc.

Thanks,

Adam

Another reason why it may be incorrect for you Jegs is that the node index starts at 0 in the IFM, whereas in FEFLOW, it starts at 1, so you could be looking at a completely different node.

This did not work for me. I had to first remove the ifm project from my solution, add it back in from FEFLOW 7.0 path (as mentioned) then modify the configuration properties to make it work, along with adding the common property back as Carlos mentioned...

So remember to change the configuration properties (if it doesn't work):
Debugging command
C/C++ additional include directories
Post-Build Event command line