The OpenSees Community

I got it, they are the ratio between the area of the element for shear (y and z in local direction, respectively) to area of the element for axial loading

I don't think the following description about the rigid link command is correct. is there any idea?


http://opensees.berkeley.edu/wiki/index ... nk_command
beam both the translational and rotational degrees of freedom are constrained.

would you please explain more about these parameters and its application?

Should the response of UniformExcitation and MultipleSupport be the same? I understand that UniformExcitation uses Trapezoidal as the only option and MultipleSupport as the default option. I expected their results to be the same. Therefore, I provided an example. According to the acceleration values...

Let me ask you my question in other way. I understand that UniformExcitation uses Trapezoidal as the only option and MultipleSupport as the default option. I expected their results to be the same. Therefore, I provided an example. According to the acceleration values and Trapezoidal method I expecte...

What are the parameters alphaY and alphaZ in the following command?? section Elastic $secTag $E $A $Iz <$G $alphaY> section Elastic $secTag $E $A $Iz $Iy $G $J <$alphaY $alphaZ> http://opensees.berkeley.edu/wiki/index.php/Elastic_Section In the manual it is just stated that they are shape factor. Wo...

Thanks for your consideration.
In this regard, the only option for UniformExcitation and default option for MultipleSupport is Trapezoidal. With this in mind, why the final results, as mentioned earlier (3.35 and 3.33), are not the same?

Thanks, thats right.
actually, when I use disp rather than accel it works. However, if I use accel, I encounter a warning which states that integration is required. I thought it assumed something (Trapezoidal) as default. Would you please let me know what should we add to the mentioned commands?

I am trying to use UniformExcitation command and use displacement record rather than acceleration record. There are two ways for implementing that: 1 timeSeries Path 1 -dt .1 -filePath record/recdis.txt -factor 1 pattern UniformExcitation 1 1 -disp 1 2 set Disp "Series Path 1 -dt .1 -filePath r...

Thanks for your response. In order to sum up for others: The earlier example is analyzed by constraints Transformation. In other words, if one uses constraints Transformation should not define the node A in a command as the master node and in another comment as the slave node. However, we do not enc...

As we can see in the Manual, there are three commands for Multi-Point Constraints. 1 rigidDiaphragm 2 equalDOF 3 rigidLink 3-1 rigidLink bar 3-2 rigidLink beam In this topic I want to shed light on the difference between the second and third ones: if you see this topic: http://opensees.berkeley.edu/...

I modeled 4 cantilever columns. Then, push them with a force in node 5. node 1 0. 0. 0. node 2 4. 0. 0. node 3 0. 4. 0. node 4 4. 4. 0. node 5 0. 0. 5. node 6 4. 0. 5. node 7 0. 4. 5. node 8 4. 4. 5. fix 1 1 1 1 1 1 1 fix 2 1 1 1 1 1 1 fix 3 1 1 1 1 1 1 fix 4 1 1 1 1 1 1 pattern Plain 1 Linear { loa...

proc Isection { secID matID d bf tw tf Nfx Nfy Nwx Nwy} { # ################################################################### # Isection $secID $matID $d $bf $tf $tw $nfdw $nftw $nfbf $nftf # _________________________________________________________________ # # Because the shape may be distorted h...

Would your please let me know why I encounter the followoing error when I run this commands? set a {1 2} recorder Node -file $direction/Reigenvector-Mode$ModeNumber-Node$NodeNumber-x.out -precision 10 -node 1 -dof $a "eigen 1 " NodeRecorder::NodeRecorder - dataToStore 1 2not recognized (di...

I think the problem will be solved if you try the following command:

set accelSeries "Series -dt $dt -filePath $GMfile -factor [expr $Scalefact*$g]";

Actually timeSeries is replaced by Series.