-
No, FEFLOW does not change the file. If you save the fem file after the simulation, however, you will obtain a model with the last results as the new initial conditions.
-
If the model is run with the (default) convective form of the transport equation, water is injected at the temperature of the injection node, i.e., a zero-gradient boundary condition is applied.
-
No, this is possible for sure. It only means that you cannot save a dac and dar file for the same simulation.
-
Actually the IFM does not really care what kind of user interface you use. Motif/Athena support was in the dialogs, but we have - for example - widely used MFC (e.g., for IfmMIKE11) and Qt. For Qt, however, you would have to make sure that the plug-in uses the same Qt version that is used for FEFLOW - this makes modules with Qt user interfaces somewhat more difficult to maintain over longer time periods.
-
I'm not sure this is a reply but on a similar topic .......
Will IFM support calls to Qt rather than OSF/Motif in the future for widget creation? Or is the documentation lagging and I can do this already? I apologize if this is somewhere in the documentation ......
RTFM used to be my favorite response to this kind of query when I was supporting software, I'm not sure what the German equivalent of the acronym is?
-
Is there any way to suppress the generation of diagrams for simulations? I can change their size, location and appearance and I can close them during the simulation but I can't stop them from appearing.
I've looked through the xml code at the end of the .fem file and I can't find anything that helps.
Am I missing something?
-
This looks as if the dac file for some reason is not OK. The dac file contains all the model information (like the fem file) at the beginning - and FEFLOW cannot read these. If the file is not too large, you can send it by email (up to 10 MB) to support@dhi-wasy.de for checking. Otherwise the support team can give you an upload address.
-
Martin,
please go to the FEFLOW help system, and search for "batch" (6.0 Standard), or go to the top level and click on "Batch Mode" (5.x and 6.0 Classic). You will find a description of how to start FEFLOW in batch mode and how to specify the results file to write out.
Peter
-
Hi Martin,
unfortunately this is not possible - at least not in the way you plan it. You cannot start a simulation from within the IFM easily.
So if you would do it with IFM, you would have to loop through the different scenarios by modifying the parameters via IFM, and then from PostSimulation set back the initial conditions, tell FEFLOW to start over again with the simulation, and change the parameters. This is what the PEST interface does. You cannot write separate dac files for each loop in this case.
So if you wish to get dac files for each simulation, I would rather recommend to use a batch command to start FEFLOW and some code that modifies an ASCII fem file. Or you use a mixture where you use a batch command to start the simulation with a specified output file, but within the fem file an IFM module modifies the parameters before actually running the simulation.
The limitation of IFM visible here (the plug-in is part of the model and cannot execute the model from "outside") will be overcome by a future Python interface. As discussed in http://www.feflow.biz/forum/index.php/topic,426.msg1582.html#msg1582, however, we cannot specify even roughly the release time of this.
Peter
-
For all boundary conditions, fluxes into the model are negative. For a mass source as a second kind boundary condition, you have to be careful with the form of the transport equation used: The default 'convective' form will only be OK if you do not have a flow boundary condition on the same nodes!