-
Hi,
I am looking for a way to use IfmGetRelativePath, IfmioGetPath or IfmioRelativePath to open a file using ifstream associated with the model. The file will be in the local directory. They need to be in a string format but I have no idea how to work with what these functions provide... Perhaps you can detail how they work?
Thank you,
Adam
-
I've previously used PreEnterSimulator, which is a good callback for the IFM to know when the model has been called by FePEST. Regarding the directory, I've been looking into IfmioGetPath and IfmioRelativePath... However, I have no idea how to use these to open files located with the model file. I'm looking for answers too.
However, if it's a static path, a simple ifstream could work, but probably not what you're looking for.
-
Hi,
I have UTM coordinates in a FEFLOW 6.2 model that are correct. They are also correct in FEFLOW 7.1. However, in FEFLOW 7.0 the coordinates are way off and I don't know why. I am opening the same file in each version. How can I fix this?
Thanks,
Adam
-
Hi,
I know that in FEFLOW 6.2 there is a Cs (max concentration) value that you can assign in the settings along with C0 (initial concentration). However, in versions 7.0 and 7.1, I can't seem to assign a value for this, but it remains in the 7.1 documentation here http://www.feflow.info/html/help71/feflow/mainpage.htm#t=08_ProblemSettings%2FMass%2Ftransport_settings.html%3Frhhlterm%3Dtransport%2520settings%26rhsyns%3D%2520
Does it still exist? If so, how do I access it? Is it even necessary if we just have boundary conditions assigned to the maximum value?
Thanks,
Adam
-
I think I have a similar issue, but when I open a model with observation points, it crashes 7.1 instantly
-
Try Select Edges, that works for me, at least in version 7.0 update 10. It's a bit nitpicky when trying to select an edge in plan view because it often picks the top slice edge instead of the vertex of the element.
I have a question myself (sorry for hijacking):
Regarding saturated-unsaturated flow conditions, how do I go about constraining the multi-layer well to prevent it from oscillating when dewatering? Seems like the only option is to use seepage face boundary conditions instead.
Thanks,
Adam
-
Hehe, I don't think it's quite what I was looking for (maybe I'm wrong), but this is interesting nonetheless and I will likely use it in the future, thank you! I'm actually developing a plug-in that modifies a bunch of different time-dependent parameters that include loading (the big bump in the picture) and consolidation.
Regards,
Adam
-
Hi Björn,
Attached is some barebones code that hopefully shows you the issue when you debug. I have model I test within FEFLOW with two distributions with the default names "Elemental Distribution 1" and "Elemental Distribution 2". Please remove the .txt extension for the files (couldn't attach otherwise).
Thanks!
Adam
-
Hi again,
Thanks again for the PreTimeStep callback issue! However, I'm now having problems with IfmGetElementalRefDistrName :'(
My code block is:
[quote]char *myStr = NULL;
IfmGetElementalRefDistrName(pDoc, 0,myStr);[/quote]
Results in:
[quote]Unhandled exception at 0x0000000180026193 (feflow7010k.dll) in feflow70q.exe: 0xC0000005: Access violation writing location 0x0000000180027e3e.[/quote]
I'm not sure what's wrong here. I've attached the debugger stuff.
Regards,
Adam
-
I see, makes sense. No need for a hotfix.
I was just curious if I could call an update myself to keep overhead low: I would be concerned if it updated the geometry after every IfmSetZ since I am making lots of geometry changes each PreTimeStep.
If I am understanding correctly, I should call PostTimeStep and it will automatically update the geometry? If so, this solves my issue. Obviously, updating during both Pre and PostTimeStep would not be ideal
Thanks,
Adam