An odd behavior in the recorder command

[hugo_esquivel]

Hi Frank. I would like to know why the recorder command does not get expanded when a list of nodes is introduced as variable in it to record a set of nodes... for example,
--------------------------
set nodesPerAxis "101 107 113 119 125 131 137 143 149 155 161 167 173"
recorder Node -file Data/$recorderFile -time -node $nodesPerAxis -dof 1 disp
--------------------------


That definition will produce an error:
--------------------------
NodeRecorder::NodeRecorder - dataToStore 101 107 113 119 125 131 137 143 149 155 161 167 173not recognized (disp, vel, accel, incrDisp, incrDeltaDisp)
--------------------------


However, to overcome the problem, I am employing the eval command as follows to expand the command so it can be properly evaluated...
--------------------------
set nodesPerAxis 101 107 113 119 125 131 137 143 149 155 161 167 173
eval "recorder Node -file Data/$recorderFile -time -node $nodesPerAxis -dof 1 disp"
--------------------------

which will not produce any error.


The funny thing is that the same workaround is not needed in the forceBeamColumn element... so I wonder why such behavior in the recorder command.

-------------------------
set sectionTag "201 201 202 201 201"
element forceBeamColumn $beamTag $nodeITag $nodeJTag [llength $sectionTag] -sections $sectionTag 1 -iter 20 1.e-08
------------------------- (works as expected!)

Any comment regarding this issue will be greatly appreciated!

Many thanks in advance...

PS: I am using OpenSees 2.2.1 (mac version)... the one downloaded from the download page.

[silvia]

it's a problem with the recorder command.

put in eval in front:

eval "recorder Node -file Data/$recorderFile -time -node $nodesPerAxis -dof 1 disp"

that way it puts in the numbers into the command and then evaluates the command.

[hugo_esquivel]

Silvia, thanks for the answer. Some time ago, you suggest me to do the same thing... that is, the same workaround I am mentioning above. However, since as of version 2.2.1 the use of eval to expand and evaluate the forceBeamColumn command is not been needed anymore, I was wondering why the same thing cannot be implemented in the recorder command. If the problem is more complex than just adding a few lines in the source code, please just ignore my request.

[silvia]

talk to Frank about it!!!!

[hugo_esquivel]

In such a case, I will stay tuned awaiting his comments . Thanks.

[silvia]

he'll tell you it's an element thing!