adacovsk

To expand upon this idea, try manually entering observation points then exporting them as a dat file, to understand how the data is represented in that file and edit them accordingly in text editor or spreadsheet software. The biggest issue with the dat file format is that you must maintain a specific number of characters for each column. I have a macro in Excel to export dat files properly so FEFLOW can use them, allowing me to adjust labels, confidence intervals, slice number, node, etc. to 600+ observation points easily.

If you have software to open shape files, this works too, as shape contain more than just X Y and your observation, unlike the rest of the available formats for importing/exporting.

I'm assuming this problem with importing multiple properties of observation points will be resolved with 6.2.

It does not update the GUI based on the highlighted information (which I believe it should). You can read the ASCII .fem file in notepad under MULTILAYERWELL to check to see if anything has been assigned, but it takes some guesswork to figure out what's what and this method for checking if it has been assigned properly isn't supported.

However, with that said, since the last time I checked, the specific storage (compressibility) within the well radius does not appear to set properly.

This is also very simple to do through an IFM plug-in, assuming you know C++.

Wow, 8 hours. I thought my models that take weeks to run on overclocked CPUs were long. :-).

Anyway, to improve performance, consider using multiple computers if you're doing multiple simulations (that would mean more licenses = $$$); overclock your computer; reduce the amount of elements (or at least maintain the resolution closer to your important areas) whereby using triangle.dll for mesh generation is the best option usually; reduce the size of your domain (reduces the amount of elements); and take larger timesteps (pay attention to your Peclet number); avoid unsaturated problems if you can (these tend to take far longer than fully saturated problems); and potentially use the 'SAMG' solver for the solver type, if you have a multi-core processor and cooling it isn't a problem and you're running a steady state.

One important thing to note is that the more time you spend designing your supermesh, the better resolution you'll get around your areas of interest and the less resolution will be necessary in far-field areas. I typically try to minimize the amount of elements to the maximum while using Triangle.dll while minimizing delaunay triangle violations and the number obtuse triangles (which can typically be fixed after you generate your mesh if it isn't too refined around your areas of interest).

Adam

Even easier way, thanks to my coworker (from an e-mail from Julia Mayer):

Go to "User Data" in the data window and add a "Nodal Expression". Next, right click and go to "Edit Parameter Expression". Assuming you want the drawdown from the initial time, type "Current = Head@(0) - Head" for the drawdown.

Adam

Hello,

I am wondering if GPU computing is supported by FEFLOW. While I understand that parallel processing is not possible for all calculations, what sort of benchmarks are available against single core PCG solving and multithreaded SAMG solving (CPU or GPU)? Would parallel processing even be effective with higher levels of parallelization using SAMG?

Thanks,

Adam

You can't intersect slices. You can instead put the slices a distance of 0.1m away from each other at your proposed intersection then change the properties of the slices, so they don't continue along for the rest of the "intersection".

Hello,

Given three nodes on a given slice, how would I go about finding all the elements within the area enclosed by those three nodes? How would the element numbers correspond to the node numbers? I plan on changing the properties of those elements within these bounds. See here:

[img width=200 height=178]http://i.imgur.com/T8jsfgK.png[/img]

The elements in orange are the ones being bounded by the area of the triangle (outlined in red) with the nodes (yellow vertices).

Thanks,

Adam