XANSYS Message: 26687 [Go back to message list]
No rating yet
Rate item:

Subject: Re: MAP operation on *MOPER Command
Author: John Swanson
Date: 2001-08-02 20:43:00

Here is the propose new description of the MAP option on *MOPER. The
changes are:
Ratio will have an automatic default as recommended, based no the number of
points.
kOut is a proposed new option.
Field 8 is the Ration field (field 1 is the *MOPER command).
The kOut setting points outside the field to zero should allow you to
use the absolute value of the
results as a mask vector. (0.0 will be false, non-zero (absolutewill be true.
John Swanson
Swanson Analysis Services, Inc.

c ***** Map option (one set of nodes to another) ****
c *MOPER,ResVal(1,1),ResXYZ(1,1),MAP,InVal(1,1),InXYZ(1,1),
c kDim,Ratio,kOut
c kDim = 2, 2d 3, 3d
c Ratio = MaxElSize/MaxGridDim of input data (auto
default) (was 0.10 default)
c kOut = 0, use closest point values 1, zero if ouside

> -----Original Message-----
> From: Mike McNamee [SMTP:mcnamee@p...]
> Sent: Wednesday, August 01, 2001 1:18 PM
> To: xansys
> Subject: RE: [xansys] MAP operation on *MOPER Command

> John S.,

> Thanks for the information on the default override, but can you shed a
> little light on what field 8 is? For that matter, what is field 7? My
> notes stop at the 2D/3D interpolation flag in field 6...

> Would there be a way to optionally have the command fill a user-provided
> mask vector with a flag whether the point was inside or outside the known
> domain? My simple-minded way of thinking about it would seem that this
> would not require much of a change. I think this might be useful to know
> where extrapolation is taking place and allow the user to quickly select
> and
> plot those nodes that did not match up well with the input geometry, data,
> etc. This would make for a big time savings over manual grep and awk of
> the
> warning messages if there is a need for reviewing extrapolated regions...

> Thanks again,
> Mike McNamee
> PADT

> Michael R. McNamee
> Analytical Engineer
> CFD & Multi-Discipline Simulation
> Phoenix Analysis & Design Technologies
> 1465 N. Fiesta Boulevard, Suite 107
> Gilbert, AZ 85233

> mike.mcnamee@p...
> www.padtinc.com

> Phone: (480) 813-4884
> Fax: (480) 813-4807

> -----Original Message-----
> From: John Swanson [mailto:john.swanson@a...]
> Sent: Tuesday, July 31, 2001 2:10 PM
> To: 'xansys '
> Subject: [xansys] MAP operation on *MOPER Command

> For those of you who are using this command, I have found that the
> default value of 0.10 in field 8 is
> much too high for large problems. I suggest you supply a value in this
> field. A good value is:

> Value = 1.0 / (sqrt(nIn)), where nin is the number of nodes in the
> input (known) set. (for kDim = 2)

> Value = 1.0 / (cuberoot(nin)), where nin is the number of nodes in
> the
> input set (for kDim = 3)

> I am looking at the following corrections to this function:

> 1. Activate the Mask function on the output set (as implied by the
> documentation)
> 2. Speed up the calculations for points which fall outside the
> region,
> and add a bounding box
> option to set the points outside the box to zero with no
> calculation time.
> 3. Use the above Value as the default for field 8, instead of the
> present 0.10 default.

> John Swanson
> Swanson Analysis Services, Inc.

Posts possibly associated with message #26687AuthorDateScore
26579MAP operation on *MOPER CommandJohn Swanson2001/07/31 
26627Re: MAP operation on *MOPER CommandMike McNamee2001/08/01 
26687Re: MAP operation on *MOPER CommandJohn Swanson2001/08/02