XANSYS Message: 40977 [Go back to message list]
Average Rating: 5 (1 votes)
Rate item:

Subject: Re: [APDL] - Question on *CFWRITE and *VPLOT
Author: Sheldon Imaoka
Date: 2002-08-21 11:25:00

Hi Terry,

Something which may (sorta) work is to plot tables with curves turned
off and markers turned on. Multiple sets cannot (easily) be
differentiated by color by can be differentiated by marker type (up
to 4 sets).

The thing is that table indices should be increasing (documented),
but dummy tables with non-increasing indices actually *VPLOT fine. A
snippet is below.

Sheldon
ANSYS, Inc.

http://www.ansys.com/ (Official Site)
http://ansys.net/ansys/ (Cheap imitation)
"This email is not being provided in my capacity as an
ANSYS employee. I am solely responsible for the content."

*DIM,what,TABLE,5
*SET,WHAT(1,0,1) , 2
*SET,WHAT(1,1,1) , 2
*SET,WHAT(2,0,1) , 3
*SET,WHAT(2,1,1) , 1
*SET,WHAT(3,0,1) , 2
*SET,WHAT(3,1,1) , 2
*SET,WHAT(4,0,1) , 3
*SET,WHAT(4,1,1) , 4
*SET,WHAT(5,0,1) , 4
*SET,WHAT(5,1,1) , 3

*DIM,where,TABLE,4
*SET,where(1,0,1) , 1
*SET,where(1,1,1) , 4
*SET,where(2,0,1) , 3
*SET,where(2,1,1) , 2
*SET,where(3,0,1) , 5
*SET,where(3,1,1) , 4
*SET,where(4,0,1) , 2
*SET,where(4,1,1) , 3

/axlab,x,my values
/axlab,y,your values
/GTHK,CURVE,-1
/GROPT,FILL,OFF
/GROPT,CURL,1
/GCOLUMN,1,
/xrange,0,6
/yrange,0,5
/gropt,divx,6
/gropt,divy,5

/GMARKER,1,1,1
*VPLOT,what(1,0),what(1,1)
/noerase
/GMARKER,1,4,1
*VPLOT,where(1,0),where(1,1)
/erase

--- In xansys@y..., "Terence Frankland" wrote:

> Either *vwrite or *mwrite appear to be what you want. They both
require format
> statements (C or Fortran descriptors) on the next line of input.
If you're
> working interactively, I think you may have to enter both the write
command and
> the format statement from an input file.

> I would also be interested in a way to get Ansys to plot a set of
points
> (scatter diagram), preferably multiple sets on the same graph.
Currently, you
> may have to paste your data into Excel to get the type of plot you
are looking
> for.

> Terry Frankland
> Elliott Company

> "Edgar Y. Lobachevskiy" on 08/21/2002 05:22:27 AM

> Please respond to xansys@y...

> To: xansys@y...
> cc: (bcc: Terence Frankland/elliott)
> Subject: [xansys] [APDL] - Question on *CFWRITE and *VPLOT

> Hi:

> I have an array that I would like to write into a file. I am using
the
> following command *CFWRITE,b(1,1), where b is the name of the array
and
> (1,1) is the location of a data point. But unfortunately it does
not work.
> I looked at the verification manual and they use similar command
> *vwrite,value(1,1) . So I tried also *vwrite but it does not work
either.
> for *vwrite command nothing is happening and for *CFWRITE command 'b
(1,1)'
> is written to a file. But I do not want that to be written I want
the value
> at b(1,1) to be written to a file. ANY SUGGESTIONS?

> Also, when I use *vplot I get a bar graph, is there a way to
produce a plot
> of just a set of points?

> thank you,

> Edgar Lobachevskiy
> University of Hawaii
> USA
> ----- Original Message -----
> From: "Joe Woodward"
> To:
> Sent: Tuesday, August 20, 2002 10:59 AM
> Subject: RE: [xansys] Re: CDWRIT,CM

> > Mark, Dan, John,
> > If you want to save time on large models, removing the *do loop
makes a
> > world of difference. I tried John's macro on 26746 nodes and it
took ~30
> > seconds. The vector command's below took 4 seconds. It also took
only 6
> > seconds to run on all 378372 nodes with a maximum node number of
892191.

> > ! MACRO
> > *if,ndinqr(0,13),gt,0,then
> > fname=
> > *ask,fname,Enter File Name,'ndgrp1'
> > nnb=
> > *dim,nnb,array,ndinqr(0,14),2
> > *vfil,nnb(1,1),ramp,1,1
> > *vget,nnb(1,2),node,1,nsel
> > *cfopen,fname,mac
> > *vwrite
> > ('/nopr')
> > *vwrite
> > ('nsel,none')
> > *vmask,nnb(1,2)
> > *vwrite,nnb(1,1)
> > ('nsel,a,,,',F12.0)
> > *vwrite
> > ('/gopr')
> > *cfclose
> > *endif

> > ! END MACRO

> > Just my 2 cents. I'm always looking to speed things up.

> > Joe Woodward
> > Analysis and Simulation Engineer
> > Phoenix Analysis & Design Technologies
> > www.padtinc.com

> > -----Original Message-----
> > From: mark.hommel@u... [mailto:mark.hommel@u...]
> > Sent: Tuesday, August 20, 2002 1:00 PM
> > To: xansys@y...
> > Subject: RE: [xansys] Re: CDWRIT,CM

> > Thank you to John Crawford! I managed to get your ndgroup.mac to
work
> > (after struggling with using/not using *use permuted with
using/not
> > using .mac extender etc.) and all I can say is that I've needed
that for
> > years. Ever since the GUI came out and ANSYS started writing all
those
> > cryptic "FITEM's" to the log file, I have needed the capability of
> > creating some crisp select logic suitable for my input files. In
such
> > cases, I usually do my selecting with the graphical picker,
writing down
> > the node numbers on a piece of paper and then I go back and type
in the
> > select commands in the input file (Should I be embarrassed to
admit
> > that?). Anyway, thank you!

> > Mark Hommel, P.E., Ph.D.
> > Senior Engineer
> > ABB Offshore Systems Inc.
> > Houston, TX

> > |(Embedded |
> > |image moved |
> > |to file: |
> > |pic30156.pcx)|

> > |"Crawford, John" |
> > |08/20/2002 01:54
PM |

> > Please respond to xansys@y...

> > To: "'xansys@y...'"
> > cc: (bcc: Mark Hommel/USOFS/ABB)
> > Subject: RE: [xansys] Re: CDWRIT,CM

> > Dan,

> > As of this morning I have 414 macros in my macro directory.
Removing
> > two of
> > them would not be significant, but it would be a step in the right
> > direction.

> > Ah, the good old days in Cincinnati. La Rosa's pizza, Burbank's
BBQ,
> > riding
> > bikes on the trail in Loveland, and working on the world's most
powerful
> > commercial aircraft engine with some talented and seriously warped
> > people.
> > Great fun at the time.

> > John Crawford
> > Honeywell Engines and Systems
> > Tempe, AZ

> > -----Original Message-----
> > From: Bohlen, Dan (GEAE) [mailto:dan.bohlen@a...]
> > Sent: Tuesday, August 20, 2002 11:29 AM
> > To: 'xansys@y...'
> > Subject: RE: [xansys] Re: CDWRIT,CM

> > Hi John,

> > Thanks. You gave me these same macros many years ago when you
were here
> > and
> > we
> > were discussing "Woody". Not only would a CMWRIT reduce your
macro
> > inventory (
> > how many it would be interesting general use macros you found the
need
> > to
> > generate ) but it would be MUCH faster, if I remember correctly
how long
> > the
> > NSEL,A,... for each node goes.

> > Dan

> > > -----Original Message-----
> > > From: Crawford, John [mailto:john.crawford@h...]
> > > Sent: Tuesday, August 20, 2002 2:17 PM
> > > To: 'xansys@y...'
> > > Subject: RE: [xansys] Re: CDWRIT,CM

> > > Dan,

> > > Many moons ago when components did not exist I needed the
> > > ability to store
> > > groups of nodes and elements. I called my ASD at the time
> > > and either Mike
> > > Yaksh or Gerry Jones sent me two macros that did something
> > > like this. Some
> > > years later I wrote my own versions of these macros and added
> > > a few bells
> > > and whistles. They're handy for transferring component
> > > definitions from one
> > > model to another and assorted other things.

> > > I have attached at the bottom of this email the text for two
macros,
> > > ndgroup.mac and elgroup.mac that may be useful. Using them
> > > as a template
> > > you could write similar macros for keypoints, lines, areas,
> > > and volumes.
> > > The basic scheme of things is that these macros generate
> > > another macro that
> > > contains a series of select commands. You then run the
> > > second macro by
> > > entering it's name at the command line to select the entities
> > > of interest.

> > > These macros *ASK for the name of the macro that will contain
> > > the select
> > > commands. I think the syntax for the *ASK command has
> > > changed a bit since I
> > > wrote these macros so check them to make sure they behave in
> > > the manner you
> > > desire. I seem to remember that at one time the text entered
> > > in the *ASK
> > > box had to be in single quotes, and then at a later release
> > > it didn't have
> > > to be in single quotes. Or maybe it was vice-versa. Or
> > > maybe I'm imagining
> > > the whole thing.

> > > You are right about ANSYS needing a CMWRITE command. I've
> > > needed it more
> > > than once. If it were available I could delete these two
> > > macros and make my
> > > macro directory a tiny bit less crowded. That would be a good
thing.

> > > John Crawford
> > > Honeywell Engines and Systems
> > > Tempe, AZ

> > > ************************* node group macro

-snip-

> > > -----Original Message-----
> > > From: Bohlen, Dan (GEAE) [mailto:dan.bohlen@a...]
> > > Sent: Tuesday, August 20, 2002 10:34 AM
> > > To: 'xansys@y...'
> > > Subject: RE: [xansys] Re: CDWRIT,CM

> > > Hmmm.. I always thought "geometry" was keypoints, lines etc.

> > > OK, I concede the documentation is OK. I still think the
> > > functionality
> > > would be
> > > better to just write the components. There are many ways to
> > > write node and
> > > element definitions: other CDWRIT options, NWRIT, EWRIT etc.

> > > Just one example where one would want to write just the
component
> > > definitions:
> > > If I have a 3D model and I want to add pressures I often want
to make
> > > components
> > > of external nodes defining the cavities. One easy way to is
> > > flatten the 3D
> > > model out to the XY plane, create the components, and then
write the
> > > components
> > > out, resume, read the CM.CDB back in. This can be
> > > accomplished other ways
> > > too (
> > > NWRIT ; SHPP,OFF ; MODMSH, NOCH ; flatten, make components,
> > > NREAD , but
> > > that's
> > > real clean.)

> > > We also have external programs that could use component
> > > definitions too.

> > > Just a suggestion, maybe not a good one....

> > > Dan Bohlen Phone: (513) 243-4645
> > > Staff Engineer Fax: (513) 786-4166
> > > GE Aircraft Engines M/D K-105

> > > > -----Original Message-----
> > > > From: sheldonimaoka [mailto:sheldon.imaoka@a...]
> > > > Sent: Tuesday, August 20, 2002 12:37 PM
> > > > To: xansys@y...
> > > > Subject: [xansys] Re: CDWRIT,CM

> > > > Hi Dan,

> > > > At least in 6.0 and 6.1, the Commands Reference for
> > > "CDWRITE" states:

> > > > CM --
> > > > Write only node and element component and geometry data to
> > > Fname.Ext.

> > > > As it mentions "component and geometry data," I believe that
this
> > > > behavior is documented correctly.

> > > > I think that CDWRITE,CM was added as an alternative to
CDWRITE,GEOM
> > > > to give the user more than one way to write out FE data (FE
> > > data with
> > > > or without component info). I think since you are looking
> > > at writing
> > > > component information only, that is where some confusion may
have
> > > > arisen.

> > > > Best regards,
> > > > Sheldon
> > > > ANSYS, Inc.

> > > > http://www.ansys.com/ (Official Site)
> > > > http://ansys.net/ansys/ (Cheap imitation)
> > > > "This email is not being provided in my capacity as an
> > > > ANSYS employee. I am solely responsible for the content."

> > > > --- In xansys@y..., "Bohlen, Dan (GEAE)"
wrote:
> > > > > How is this supposed to work? I assume it would write the
> > > > component definitions
> > > > > - for me ( Ansys 6.0) it writes that plus all the nodes and
> > > > elements. To me
> > > > > that defeats part of the purpose of CDWRIT,CM.

> > > > > Unless there's a good reason I'd request that CDWRIT,CM
does what
> > > > the manual
> > > > > says it should do only write the component definitions.

> > > > > Dan Bohlen Phone: (513) 243-4645
> > > > > Staff Engineer Fax: (513) 786-4166
> > > > > GE Aircraft Engines M/D K-105

Posts possibly associated with message #40977AuthorDateScore
40960[APDL] - Question on *CFWRITE and *VPLOTEdgar Lobachevskiy2002/08/21 
40962Re: [APDL] - Question on *CFWRITE and *VPLOTPeter Frei2002/08/21 
40970Re: [APDL] - Question on *CFWRITE and *VPLOTTerence Frankland2002/08/21 
40971Re: [APDL] - Question on *CFWRITE and *VPLOTJohn Swanson2002/08/21 
40977Re: [APDL] - Question on *CFWRITE and *VPLOTSheldon Imaoka2002/08/215