Help with Analyst coding Answered

In my analyst script I have defined the location of my elements around the edges of my domain defined by coordinates and have a few questions about this.

symb px1 = 1.000000e-03
symb py1 = 1.000000e-03
symb #get { i_el1 j_el1 kdum } clsnode $px1 $py1
symb px2 = 1.000000e-03
symb py2 = 2.000000e-03
symb #get { i_el2 j_el2 kdum } clsnode $px2 $py2
symb px3 = 1.000000e-03
symb py3 = 3.000000e-03
symb #get { i_el3 j_el3 kdum } clsnode $px3 $py3
symb px4 = 1.000000e-03
symb py4 = 4.000000e-03
symb #get { i_el4 j_el4 kdum } clsnode $px4 $py4
symb px5 = 1.000000e-03
symb py5 = 5.000000e-03
symb #get { i_el5 j_el5 kdum } clsnode $px5 $py5
symb px6 = 1.000000e-03
symb py6 = 6.000000e-03
symb #get { i_el6 j_el6 kdum } clsnode $px6 $py6
symb px7 = 1.000000e-03
symb py7 = 7.000000e-03
symb #get { i_el7 j_el7 kdum } clsnode $px7 $py7
symb px8 = 1.000000e-03
symb py8 = 8.000000e-03
symb #get { i_el8 j_el8 kdum } clsnode $px8 $py8
symb px9 = 1.000000e-03
symb py9 = 9.000000e-03
symb #get { i_el9 j_el9 kdum } clsnode $px9 $py9

symb px19 = 1.096000e-02
symb py19 = 9.000000e-03
symb #get { i_el19 j_el19 kdum } clsnode $px19 $py19
symb px20 = 1.096000e-02
symb py20 = 8.000000e-03
symb #get { i_el20 j_el20 kdum } clsnode $px20 $py20
symb px21 = 1.096000e-02
symb py21 = 7.000000e-03
symb #get { i_el21 j_el21 kdum } clsnode $px21 $py21
symb px22 = 1.096000e-02
symb py22 = 6.000000e-03
symb #get { i_el22 j_el22 kdum } clsnode $px22 $py22
symb px23 = 1.096000e-02
symb py23 = 5.000000e-03
symb #get { i_el23 j_el23 kdum } clsnode $px23 $py23
symb px24 = 1.096000e-02
symb py24 = 4.000000e-03
symb #get { i_el24 j_el24 kdum } clsnode $px24 $py24
symb px25 = 1.096000e-02
symb py25 = 3.000000e-03
symb #get { i_el25 j_el25 kdum } clsnode $px25 $py25
symb px26 = 1.096000e-02
symb py26 = 2.000000e-03
symb #get { i_el26 j_el26 kdum } clsnode $px26 $py26
symb px27 = 1.096000e-02
symb py27 = 1.000000e-03
symb #get { i_el27 j_el27 kdum } clsnode $px27 $py27

1)  What does the expression kdum represent?

2) Is there a way of plotting the element locations so I can see them?  The  model I am reading in is from a flxtbl file and I am not 100% confident the positions of the elements are in the correct locations. I am not sure how I would implement the coding for this or what to write.


Dave :) 


  • Hi David,

    1) You are simulating a 2D model the line:

    symb #get { i_el1 j_el1 kdum } clsnode $px1 $py1

    can be used to pull out the nodal location for 2D and 3D models if you were working in 3D kdum would store the location of the node on the z axis. Because you are working in 2D this value will either be 0 or 1 (I can't remember but it isn't important here). You can actually remove this if you want I don't think it will break anything in the code.

    2) I don't think there is you would probably need to get creative and assign a copy of a material to that element in order to visualize it. This isn't recommended purely because it can be quite tedious to code.

    I know you are using a table file but surely you know the dimensions of the model you have created? If you are you can just remove the symb #get commands....

    The pout command would then look something like this:

    hist xyz arrayname $px1 $px1 * $py1 $py1 *

    If all of the px and py variables are correct then the time histories should be in the positions you expect.

    Best regards,


    Comment actions Permalink
  • Hi Oliver

    The table file I am reading in runs from  0.001000    up to   0.011050 in the x direction

    Elements 1 to 9 have an x-coordinate of 0.001000 so the elements on the other side of my domain should have x-coordinates of 0.011050 so my elements are on the edge of my Titanium block.

    Using 0.011050 for the elements x- locations  on the RHS seems to give A-scan signals that suggest its wrong.

    But If I use 0.010960 the A-scan signals seem to be true. I don't understand how this is the case.


    Dave :) 

    Comment actions Permalink
  • Well your probe locations should lie somewhere in the range of 0.001 of 0.01105 similar with the y coordinates whatever the range is the probe locations need to lie somewhere in this range.

    if it started from the origin then your probe locations would probably be valid 

    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post