b

i think i figured it out. 'Top' and 'Bottom' refer to the portion of conflicted slices; and 'Down' and 'Up' are directions how the elevations of conflicted slices are to be modified or repaired.

b 

hello,
can anybody help explain what 'Top/Down' and 'Bottom/Up' (with a specified minimal thichness) mean when a new slice is inserted between two existing slices and it would conflict with either one or both of them. in another word, which slice does 'Top/Down' or 'Bottom/Up' refer to? for a special case (e.g. one layer/2 slices), if the 2nd slice elevation conflicts with the 1st slice elevation, what does 'Top/down' or 'Bottom/Up' mean?

thank you!

b

hello,
for a groundwater flow model with time-constant boundary conditions, is that right the accumulated imbalance is supposed to approach towards a 'constant' value if it is run under transient mode for a relatively long time period? if it is does not, what does that indicate? something wrong with the boundary conditions? or are there any other reasons that may cause that?

thank you very much in advance

b

Thanks Peter!  Feflow 6.0 (standard) with latest patch has been downloaded and installed.  The problem was resolved!

Regards,

b

hi,
i used feflow 6.0 (standard) to open a model that was originally built using feflow 6.0 (classic).  the model crashed when i tried to refine elements (triangle mesh) locally.  however, if i use feflow 6.0 (classic) to refine elements, the model would not crash. 

i have done mesh refinements for several other models that were originally built using feflow (classic) as well without getting any problems.  i do not know why it happened to this model.  does anybody can give me some help to let me know what might casue this knid of problem?

thanks! 

rolling mouse wheel (with "Shift" kept pressed) will change the size of inspector magnifier.  that will make it easier to local a node.

b 

hi,

how to set up snap distance in feflow 6.0 standard in pixel (e.g. 2 pixels in feflow 6.0 classic), so that inspector magnifier can easily snap a node whenever the model area is zoomed in or zoomed out.

Thanks in advance

b 

i reviewed the previous forum in 2006.  it seems that difference between 'Budget analysis' and 'Content analysis' can give a rough estimation of numerical error.

b 

hi,

a balance for a transient flow model represents the change in storage as well as the residual numerical error.  in feflow 6.0, where can i separate this balance, i.e. how much of the balance comes from the change in storage and how much from the numerical error?

thanks in advance

b

hi,
is that possible that the non-pumping wells, i.e., 0 m3/day assigned in the feflow model at the same nodes across several layers, may cause hydraulic head flucturation in some nearby observation wells or in those pumping wells themself.

thanks

b