Possible bug with Record command

[GiuseppeDelGobbo]

Hello,

I am using several recorders during a time history analysis of a multistorey structure. I have found that the "recorder Drift" recorder does not obey the "record" command if a time step is specified for the recorder. I believe that there is a bug with the record command or the recorder Drift command.

For example:

This records a value at time = 0 twice.
recorder Drift -file IDR1.txt -time -iNode 1 6 -jNode 6 11 -dof 1 -perpDirn 2
record
record

These does not record any values at time = 0:
recorder Drift -file IDR2.txt -time -dT 0.001 -iNode 1 6 -jNode 6 11 -dof 1 -perpDirn 2
recorder Drift -file IDR3.txt -time -dT 0.00099 -iNode 1 6 -jNode 6 11 -dof 1 -perpDirn 2
record
record

[fmk]

give the second file a different name .. you have 2 recorders writing to file with same file name .. drivel is going to result.

actually on rereading you don't

[fmk]

it's probably the dT option .. the first time it will record is the first time the time step is greater than .001 or .00099 .. you can check by removing the option.

[GiuseppeDelGobbo]

Yes the dT option prevents the "record" command from recording at t=0, but only for the drift recorder. For other recorders there is no problem and all recorders save the state.

Ex: These record a value at time = 0 twice, then t=0.01, t=0.02, ...

recorder Node -file Vel.txt -dT 0.00999 -time -timeSeries 2 -node 1 6 -dof 1 vel
recorder Node -file Accel.txt -dT 0.00999 -time -timeSeries 2 -node 1 6 -dof 1 accel
recorder Element -file col1.txt -dT 0.00999 -time -ele 65 localForce
record
record

[fmk]

the next release should solve the problem.

[GiuseppeDelGobbo]

Great, thanks for the help.