why i can not define the recorder when the material is steel01

HOME FORUM User Discussions why i can not define the recorder when the material is steel01

Viewing 15 posts - 1 through 15 (of 17 total)
  • Author
    Posts
  • #23950
    yuyang
    Participant

    I am a beginner of opensees.When i followed the vedio2 of the following http://openseesnavigator.berkeley.edu/documentation/videos.I always got a problem to define the recorder of beamcolumn element.there will be a recorder eroor as http://pan.baidu.com/s/1i4z3hfZ. But if i change the material from steel01 to concrete .There was no problem at this step

    • This topic was modified 6 years, 7 months ago by yuyang.
    • This topic was modified 6 years, 7 months ago by yuyang.
    #23953
    yuyang
    Participant
    #23955
    kengawk
    Participant

    I suggest that you’d better upload the model that contains the problem.

    #23960
    yuyang
    Participant

    do you mean upload the tcl codes?

    #23961
    kengawk
    Participant

    yeah,mat or tcl files.

    #23968
    yuyang
    Participant

    now i already solved that problem. but there is another one with my case.here i will appendix the tcl codes of my case. so sorry that i do not know how to upload files here.i will copy them respectively

    #23969
    yuyang
    Participant

    here is the main file
    # second example.tcl
    logFile “second example.log”
    set systemTime [clock seconds]

    puts “===============================================================================”
    puts “OpenSees Navigator: Version 2.5.5”
    puts “File sourced: C:/mat/新建文件夹/yy/yyyy/y12/second example/second example.tcl”
    puts “Starting OpenSees analysis: [clock format $systemTime -format “%d-%b-%Y %H:%M:%S”]”
    puts “===============================================================================”

    puts “\n########################”
    puts “# Analysis-Sequence 1 #”
    puts “########################”

    # Start timing of this analysis sequence
    # ————————————–
    set tStart [clock clicks -milliseconds]

    # Start of model generation
    # =========================

    # Create ModelBuilder
    # ——————-
    model BasicBuilder -ndm 2 -ndf 3

    # Define geometry
    # —————
    source NodeCoord.tcl

    # Define Single Point Constraints
    # ——————————-
    source SPConstraint.tcl

    # Define nodal masses
    # ——————-
    source NodeMass.tcl

    # Define Multi Point Constraints
    # ——————————
    source MPConstraint.tcl

    # Define material(s)
    # ——————
    source Materials.tcl

    # Define section(s)
    # —————–
    source Sections.tcl

    # Define geometric transformation(s)
    # ———————————-
    source GeoTran.tcl

    # Define element(s)
    # —————–
    source Elements.tcl

    # Define damping parameters
    # ————————-

    # Define time series
    # ——————
    source TimeSeries.tcl

    # Start of analysis generation
    # ============================

    # Get Initial Stiffness
    # ———————
    initialize

    puts “o Analysis: pushover”
    # ~~~~~~~~~~~~~~~~~~~~~~~~~

    # Define load pattern
    # ——————-
    source LoadPattern_4.tcl

    # Define recorder(s)
    # ——————
    source Recorder_4.tcl

    # Define analysis options
    # ———————–
    source AnalysisOptn_4.tcl

    # Record initial state of model
    # —————————–
    record

    # Analyze model
    # ————-
    analyze 1

    # Stop timing of this analysis sequence
    # ————————————-
    set tStop [clock clicks -milliseconds]
    puts “o Time taken: [expr ($tStop-$tStart)/1000.0] sec”

    # Clean up
    # ——–
    wipe
    set systemTime [clock seconds]
    puts “\n===============================================================================”
    puts “Finished OpenSees analysis: [clock format $systemTime -format “%d-%b-%Y %H:%M:%S”]”
    puts “===============================================================================”
    exit

    #23970
    yuyang
    Participant

    here are node information
    # NodeCoord.tcl

    # Node tag xCrd yCrd ndf
    node 1 +0.000000E+00 +0.000000E+00 -ndf 3
    node 2 +0.000000E+00 +1.560000E+02 -ndf 3
    node 3 +0.000000E+00 +3.120000E+02 -ndf 3
    node 4 +3.600000E+02 +0.000000E+00 -ndf 3
    node 5 +3.600000E+02 +1.560000E+02 -ndf 3
    node 6 +3.600000E+02 +3.120000E+02 -ndf 3

    # SPConstraint.tcl

    # SPC tag Dx Dy Rz
    fix 1 1 1 1
    fix 4 1 1 1

    # MPConstraint.tcl

    # Equal DOF: f1: mNodeTag sNodeTag dof
    equalDOF 2 5 1
    # Equal DOF: f2: mNodeTag sNodeTag dof
    equalDOF 3 6 1

    # NodeMass.tcl

    # Mass tag mx my mIz
    mass 2 +5.000000E-01 +0.000000E+00 +0.000000E+00
    mass 3 +5.000000E-01 +0.000000E+00 +0.000000E+00
    mass 5 +5.000000E-01 +0.000000E+00 +0.000000E+00
    mass 6 +5.000000E-01 +0.000000E+00 +0.000000E+00

    • This reply was modified 6 years, 6 months ago by yuyang.
    #23971
    yuyang
    Participant

    here are element information

    # Materials.tcl

    # Material “Column”: matTag Fy E b a1 a2 a3 a4
    uniaxialMaterial Steel01 1 +5.000000E+01 +2.900000E+04 +1.000000E-02 +0.000000E+00 +1.000000E+00 +0.000000E+00 +1.000000E+00

    # Material “ElasticDefault”: matTag E <eta> <Eneg>
    uniaxialMaterial Elastic 2 +2.900000E+04 +0.000000E+00

    # Material “beam”: matTag Fy E b a1 a2 a3 a4
    uniaxialMaterial Steel01 3 +3.600000E+01 +2.900000E+04 +1.000000E-02 +0.000000E+00 +1.000000E+00 +0.000000E+00 +1.000000E+00

    # Sections.tcl

    # Section “Beam”: secTag
    section Fiber 1 {
    # PatchAISC “beam”: matTag NSIJ NSJK Iy Iz Jy Jz Ky Kz Ly Lz
    patch quad 3 6 1 +1.126000E+01 +3.520000E+00 +1.126000E+01 -3.520000E+00 +1.185000E+01 -3.520000E+00 +1.185000E+01 +3.520000E+00
    patch quad 3 1 6 -1.126000E+01 +2.150000E-01 -1.126000E+01 -2.150000E-01 +1.126000E+01 -2.150000E-01 +1.126000E+01 +2.150000E-01
    patch quad 3 6 1 -1.185000E+01 +3.520000E+00 -1.185000E+01 -3.520000E+00 -1.126000E+01 -3.520000E+00 -1.126000E+01 +3.520000E+00
    }

    # Section “ElasticDefault”: secTag E A Iz <G> <alpha>
    section Elastic 2 +2.900000E+04 +1.800000E+02 +4.860000E+03 +1.115400E+04 +8.333333E-01

    # Section “column”: secTag
    section Fiber 3 {
    # PatchAISC “column”: matTag NSIJ NSJK Iy Iz Jy Jz Ky Kz Ly Lz
    patch quad 1 6 1 +1.270500E+01 +4.995000E+00 +1.270500E+01 -4.995000E+00 +1.345000E+01 -4.995000E+00 +1.345000E+01 +4.995000E+00
    patch quad 1 1 6 -1.270500E+01 +2.450000E-01 -1.270500E+01 -2.450000E-01 +1.270500E+01 -2.450000E-01 +1.270500E+01 +2.450000E-01
    patch quad 1 6 1 -1.345000E+01 +4.995000E+00 -1.345000E+01 -4.995000E+00 -1.270500E+01 -4.995000E+00 -1.270500E+01 +4.995000E+00
    }

    # Elements.tcl

    # Element “column”: eleTag NodeI NodeJ NIP secTag geoTranTag <-mass massDens> <-iter maxIters tol>
    element forceBeamColumn 1 1 2 5 3 2 -mass +0.000000E+00 -iter 10 +1.000000E-12

    # Element “column”: eleTag NodeI NodeJ NIP secTag geoTranTag <-mass massDens> <-iter maxIters tol>
    element forceBeamColumn 2 4 5 5 3 2 -mass +0.000000E+00 -iter 10 +1.000000E-12

    # Element “column”: eleTag NodeI NodeJ NIP secTag geoTranTag <-mass massDens> <-iter maxIters tol>
    element forceBeamColumn 3 2 3 5 3 2 -mass +0.000000E+00 -iter 10 +1.000000E-12

    # Element “column”: eleTag NodeI NodeJ NIP secTag geoTranTag <-mass massDens> <-iter maxIters tol>
    element forceBeamColumn 4 5 6 5 3 2 -mass +0.000000E+00 -iter 10 +1.000000E-12

    # Element “beam”: eleTag NodeI NodeJ NIP secTag geoTranTag <-mass massDens> <-iter maxIters tol>
    element forceBeamColumn 5 2 5 5 1 1 -mass +0.000000E+00 -iter 10 +1.000000E-12

    # Element “beam”: eleTag NodeI NodeJ NIP secTag geoTranTag <-mass massDens> <-iter maxIters tol>
    element forceBeamColumn 6 3 6 5 1 1 -mass +0.000000E+00 -iter 10 +1.000000E-12

    # GeoTran.tcl

    # GeoTran type tag
    geomTransf Corotational 1
    # GeoTran type tag
    geomTransf PDelta 2

    • This reply was modified 6 years, 6 months ago by yuyang.
    #23974
    yuyang
    Participant

    and here are loadpattern and analysis option

    # LoadPattern_4.tcl

    # LoadPattern “pushover”: patternTag tsTag factor
    pattern Plain 1 1 -fact +1.000000E+00 {
    # Load nodeTag LoadValues

    # SP nodeTag dofTag DispValue

    # eleLoad eleTags beamUniform Wy <Wx>

    # eleLoad eleTags beamPoint Py xL <Px>
    }

    # Recorder_4.tcl

    # Node Recorder “DefoShape”: fileName <nodeTag> dof respType
    recorder Node -file pushover_Node_DefoShape_Dsp.out -time -nodeRange 1 6 -dof 1 2 3 disp
    recorder Node -file pushover_Node_DefoShape_Acc.out -time -nodeRange 1 6 -dof 1 2 3 accel

    # BeamColumn Recorder “allbc”: fileName <eleTag> arguments
    recorder Element -file pushover_BeamColumn_allbc_LocForc.out -time -ele 1 2 3 4 5 6 localForce
    recorder Element -file pushover_BeamColumn_allbc_ChordRot.out -time -ele 1 2 3 4 5 6 chordRotation

    # TimeSeries.tcl

    # TimeSeries “LinearDefault”: tsTag cFactor
    timeSeries Linear 1 -factor +1.000000E+00

    # AnalysisOptn_4.tcl

    # AnalysisOptn “pushover”: Type: Static
    # ————————————-
    # Constraint Handler
    constraints Plain
    # DOF Numberer
    numberer RCM
    # System of Equations
    system BandGeneral
    # Convergence Test
    test NormDispIncr +1.000000E-06 25 0 2
    # Solution Algorithm
    algorithm NewtonLineSearch -type InitialInterpolated -tol +8.000000E-01 -maxIter 10 -minEta +1.000000E-01 -maxEta +1.000000E+01 -pFlag 1
    # Integrator
    integrator DisplacementControl 3 1 +1.000000E-02
    # Analysis Type
    analysis Static

    #23975
    yuyang
    Participant

    and here are what the OpenSees feedback to me

    ===============================================================================
    OpenSees Navigator: Version 2.5.5
    File sourced: C:/mat/新建文件夹/yy/yyyy/y12/second example/second example.tcl
    Starting OpenSees analysis: 14-Mar-2016 13:27:08
    ===============================================================================

    ########################
    # Analysis-Sequence 1 #
    ########################
    o Analysis: pushover
    WARNING: CTestNormDispIncr::setEquiSolnAlgo() – no SOE
    WARNING DisplacementControl::domainChanged() – zero reference loadStaticAnalysis::setAlgorithm() – Integrator::domainChanged() failedStaticAnalysis::analyze() – domainChanged failed at step 0 of 1
    OpenSees > analyze failed, returned: -1 error flag
    o Time taken: 0.035 sec

    ===============================================================================
    Finished OpenSees analysis: 14-Mar-2016 13:27:08
    ===============================================================================

    hopefully that you can give me some advice. as it is hardly to find anyguys who know how to use Opensees around me.

    thanks a lot
    best regard

    • This reply was modified 6 years, 6 months ago by yuyang.
    #23977
    yuyang
    Participant

    oh.i know the reason now . the video did not assign pushover load after gravity analyze. so after i assign it . the case is ok now. so sorry to disturb you .
    here i want to know how to create or find the timeseries file for earthquake load . ss the example i download from website was not including EQ timeseries file

    thank you again

    #23979

    If you download the example by clicking on “OSN Model” on the following website http://openseesnavigator.berkeley.edu/documentation/videos/ it will include the ground motion files.

    #23982
    yuyang
    Participant

    is it possible to remove a column or any other element at a specific time through opensees navigator?
    and how to assign gravity first ,then assign nodes load step by step?

    #23989

    Yes, you can remove elements by specifying a “User Defined Analysis Script” in the Analysis Case. With that option you have full control of the OpenSees analysis.
    If you want to look at an example on how to control the analysis I suggest that you study Example 3: http://openseesnavigator.berkeley.edu/wp-content/uploads/2015/09/Example3.zip
    This example does not remove elements, but it shows you how to use “User Defined Analysis Scripts” for both static and transient analyses.

Viewing 15 posts - 1 through 15 (of 17 total)
  • You must be logged in to reply to this topic.