-
I'm currently modelling the heat interactions between a river and the aquifer in a 3d model. The aquifer thickness is 30m and the model is currently being run for 20 days.
I've noticed a large difference in calculated temperature at certain observational wells between the pump and the river depending on the number of slices used to represent the current nodes. For example when the number of slices is 21 there's a huge difference in temperature change from 41 slices when the observational well is placed 20m inbetween the river and the pumping bore.
Is there a "rule of thumb" or any sort of guidelines in determing the number of slices? Any references to literature would be great!
Thanks in advance!
-
All values of boundary conditions in FeFlow can be exported into an ASCII file format. I've only ever had to export values of head but I'd assume heat values can be exported in a similar way for all the nodes. After you get this file import this information using either excel or mat lab or surfer and then you should be able to visualise the thermal response in one of the many graph functions in Matlab/Surfer. The tutorials on FeFlow are very extensive and should provide you with information on what you want.
-
Some good ideas! I had the same problem months ago, you could calculate the distances using the co-ordinates at the bottom of the screen
-
I'm currently trying to understand the difference between a Phreatic and Free Surface setup.
From what I understand a Free Surface forces the layer to be fully saturated by distorting the mesh so it remains fully saturated through the mode run.
A Phreatic layer however doesn't change it allows for partially saturated and unsaturated elements on the layer.
My question is:
Is it possible in FeFlow that a drawdown cone from pumping bore can cause a river to disconnect? I've attached a image from a matlab script showing the drawdown cone under a river, the river boundary conditions are set to 0 dispite this the head values under the boundary condition in the river are less than zero.
-
I have a similar issue. Is there anyway to export images from FeFlow to get rid of the black background? This would save a lot of ink.
-
I just figure a way around this, In FeFlow classic values in the Flux Anayliser can be copied and pasted into notepad. I can't seem to screen shot it but you can copy the x,y,z values by pressing the middle scroll button, then cnrt+v into note pad.
-
I want some clarity in steady state and transient pathline computations. When selecting pathline computations, there are two options, one for a steady state calculation and the other is a transient pathline computation. The transient pathline computation I'm assuming to be the actual path the particles took while the steady state pathline computation is the path that at that point in time would have taken if these conditions at that time were held constant. Can I get some clarity on this as I can't find much on this in the help file.
Thanks in advance!
-
Thanks,
With the export option in the view components window, I can only seem to export the isolines. But I'll make a request in the FeFlow wishlist part of the forum
-
Also is there a way to export this nodal data as a time series? In FeFlow classic you can graph the data as a time series, but there's no option to export this data to a file.
-
Is there anyway of jsut exporting data for specific nodes? I'm trying to export velocity data for specific nodes but the option isn't showing up. I've attached a picture to illustrate my problem: