Hello,
I am using openseesMP for modeling a large soil medium (partitioned) and noticed a difference in the results compared to sequential analysis. What could be the reason for this deviation of openseemMP results?
Search found 15 matches
- Fri Oct 15, 2021 6:58 pm
- Forum: Parallel Processing
- Topic: Accuracy of OpenSeesMP results
- Replies: 1
- Views: 15353
- Sat May 22, 2021 7:48 am
- Forum: OpenSees.exe Users
- Topic: Soil modelling
- Replies: 0
- Views: 6233
Soil modelling
hi,
I have a soil model. And I am using MultiYieldSurfaceClay material and quad elements for modeling the soil. However, I get this error when running the analysis:
FATAL:MultiYieldSurfaceClay::Can not deal with e2p
what's that mean?
I have a soil model. And I am using MultiYieldSurfaceClay material and quad elements for modeling the soil. However, I get this error when running the analysis:
FATAL:MultiYieldSurfaceClay::Can not deal with e2p
what's that mean?
- Fri Jan 15, 2021 2:03 am
- Forum: Parallel Processing
- Topic: parallel analysis of a nonlinear frame
- Replies: 2
- Views: 10537
parallel analysis of a nonlinear frame
Hi,
I am trying to run a model of a nonlinear frame system with force-based elements using openseesSP. However, the analysis doesn't start at all and i get this error "ForceBeamColumn3d::update() -- could not invert flexibility". Although the analysis of the same model can be done successfully using sequential analysis.
I am trying to run a model of a nonlinear frame system with force-based elements using openseesSP. However, the analysis doesn't start at all and i get this error "ForceBeamColumn3d::update() -- could not invert flexibility". Although the analysis of the same model can be done successfully using sequential analysis.
- Sat Nov 21, 2020 3:55 am
- Forum: OpenSees.exe Users
- Topic: analysis warning
- Replies: 1
- Views: 2034
analysis warning
Hi
I am trying to perform a site response analysis of a 2D soil model. The soil is modeled using quad elements. During the analysis, I get this warning:
WARNING DOF_Group::setID - invalid location 2 in ID of size 2
What does that mean?
I am trying to perform a site response analysis of a 2D soil model. The soil is modeled using quad elements. During the analysis, I get this warning:
WARNING DOF_Group::setID - invalid location 2 in ID of size 2
What does that mean?
- Fri Nov 20, 2020 2:33 am
- Forum: OpenSees.exe Users
- Topic: 2D soil model with plane strain formulation
- Replies: 1
- Views: 2040
2D soil model with plane strain formulation
Hi,
I am trying to model an elastic isotropic soil medium using plane strain formulation. So, do I need to either use only a quad element with a plane strain type or only a PlaneStrain material to impose the plane strain conditions? or should I use both?
Thanks
I am trying to model an elastic isotropic soil medium using plane strain formulation. So, do I need to either use only a quad element with a plane strain type or only a PlaneStrain material to impose the plane strain conditions? or should I use both?
Thanks
- Fri Nov 20, 2020 2:04 am
- Forum: OpenSees.exe Users
- Topic: modeling of an elastic isotropic soil
- Replies: 1
- Views: 2026
modeling of an elastic isotropic soil
Hi,
I am trying to model an elastic isotropic soil and I am wondering about the appropriate material to be used.
for the ElasticIsotropic material:
nDMaterial ElasticIsotropic $matTag $E $v <$rho>
is the soil shear modulus implicitly defined in terms of E and v?
I am trying to model an elastic isotropic soil and I am wondering about the appropriate material to be used.
for the ElasticIsotropic material:
nDMaterial ElasticIsotropic $matTag $E $v <$rho>
is the soil shear modulus implicitly defined in terms of E and v?
- Sat Oct 24, 2020 6:46 am
- Forum: OpenSees.exe Users
- Topic: error with defining a node
- Replies: 2
- Views: 2746
error with defining a node
I defined a node using this command
node 08010 6.00 0.00 -1.00
however, i get this error when running the model:
WARNING invalid nodeTag
Want: node nodeTag? [ndm coordinates?] <-mass [ndf values?]>
expected integer but got "08010"
while executing
"node 08010 6.00 0.00 -1.00"
(file "model5dist.tcl" line 245)
invoked from within
"source model5dist.tcl"
(file "THForceAnalysis.tcl" line
so, why is this node tag not considered an integer?
node 08010 6.00 0.00 -1.00
however, i get this error when running the model:
WARNING invalid nodeTag
Want: node nodeTag? [ndm coordinates?] <-mass [ndf values?]>
expected integer but got "08010"
while executing
"node 08010 6.00 0.00 -1.00"
(file "model5dist.tcl" line 245)
invoked from within
"source model5dist.tcl"
(file "THForceAnalysis.tcl" line
so, why is this node tag not considered an integer?
- Sat Oct 24, 2020 4:59 am
- Forum: OpenSees.exe Users
- Topic: modeling of a spring and a damper in parllel
- Replies: 5
- Views: 5041
modeling of a spring and a damper in parllel
Hi,
I am trying to model a spring-damper system in which the spring and the damper are placed in parallel. I couldn't find any material or element that would simulate that behavior. The available ViscousDamper material simulates a spring and a damper put in series, and the Viscous material isn't allowed be modeled in parallel with a spring.
Any help would be appreciated.
Thanks
I am trying to model a spring-damper system in which the spring and the damper are placed in parallel. I couldn't find any material or element that would simulate that behavior. The available ViscousDamper material simulates a spring and a damper put in series, and the Viscous material isn't allowed be modeled in parallel with a spring.
Any help would be appreciated.
Thanks
- Fri Aug 28, 2020 8:38 am
- Forum: OpenSeesPy
- Topic: Convergence problems with force-based elements
- Replies: 7
- Views: 7690
Re: Convergence problems with force-based elements
I use newmark as the primary integrator. But then I use a convergence approach that incorporates different nonlinear algorithms, integrators, time step sizes and tolerance values. Here it is:
# %%% DYNAMIC ANALYSIS PARAMETERS %%%
constraints Transformation;
numberer Plain;
system BandSPD
set Tol 1.0e-3;
set maxNumIter 30;
set printFlag 0;
set NewmarkGamma 0.5;
set NewmarkBeta 0.25;
set TestType RelativeNormDispIncr;
set algorithmType Newton;
test $TestType $Tol $maxNumIter $printFlag;
algorithm $algorithmType;
integrator Newmark $NewmarkGamma $NewmarkBeta;
analysis Transient;
# %%% DYNAMIC ANALAYSIS %%%
set ok [analyze $Nsteps $dtAnalysis];
if {$ok != 0} {
set ok 0;
set controlTime [getTime];
while {($controlTime<$TmaxAnalysis) && $ok == 0} {
set ok [analyze 1 $dtAnalysis];
set controlTime [getTime];
if {$ok != 0} {
puts "Trying Newton with Initial Tangent ..";
test RelativeNormDispIncr 5.0e-3 20 0;
algorithm Newton -initial;
set ok [analyze 1 $dtAnalysis];
};
if {$ok != 0} {
puts "Relieving Convergence Criteria 1 ..";
test RelativeEnergyIncr 1.0e-3 40 5;
algorithm Newton -initial;
set ok [analyze 1 $dtAnalysis];
};
if {$ok != 0} {
puts "Relieving Convergence Criteria 2 ..";
test RelativeEnergyIncr 5.0e-1 40 5;
algorithm Newton -initial;
set ok [analyze 1 $dtAnalysis];
};
if {$ok != 0} {
puts "Trying Newton ..";
test RelativeNormDispIncr 1.0e-3 20 0;
algorithm Newton;
set ok [analyze 1 $dtAnalysis];
};
if {$ok != 0} {
puts "Trying Bisection ...";
algorithm NewtonLineSearch <-type Bisection>;
set ok [analyze 1 $dtAnalysis]
algorithm $algorithmType;
};
if {$ok != 0} {
puts "Trying Secant ...";
algorithm NewtonLineSearch <-type Secant>;
set ok [analyze 1 $dtAnalysis]
algorithm $algorithmType;
};
if {$ok != 0} {
puts "Trying RegulaFalsi ...";
algorithm NewtonLineSearch <-type RegulaFalsi>;
set ok [analyze 1 $dtAnalysis]
algorithm $algorithmType;
};
# if {$ok != 0} {
# puts "Trying KrylovNewton ...";
# algorithm KrylovNewton;
# set ok [analyze 1 $dtAnalysis]
# algorithm $algorithmType;
# };
# if {$ok != 0} {
# puts "Trying Newton ...";
# algorithm Newton;
# set ok [analyze 1 $dtAnalysis]
# algorithm $algorithmType;
# };
if {$ok != 0} {
puts "Trying BFGS ...";
algorithm BFGS;
set ok [analyze 1 $dtAnalysis]
algorithm $algorithmType;
};
if {$ok != 0} {
puts "Trying Broyden ...";
algorithm Broyden;
set ok [analyze 1 $dtAnalysis]
algorithm $algorithmType;
};
if {$ok != 0} {
puts "Trying HHT 0.9 ...";
integrator HHT 0.9;
set ok [analyze 1 $dtAnalysis]
# integrator TRBDF2;
integrator Newmark $NewmarkGamma $NewmarkBeta;
};
if {$ok != 0} {
puts "Trying OS ...";
integrator AlphaOS 1.00;
algorithm Linear;
set ok [analyze 1 $dtAnalysis]
# integrator TRBDF2;
integrator Newmark $NewmarkGamma $NewmarkBeta;
algorithm $algorithmType;
};
if {$ok != 0} {
puts "Trying OSG ...";
integrator AlphaOSGeneralized 1.00;
algorithm Linear;
set ok [analyze 1 $dtAnalysis]
# integrator TRBDF2;
integrator Newmark $NewmarkGamma $NewmarkBeta;
algorithm $algorithmType;
};
if {$ok != 0} {
puts "Trying more iterations...";
test $TestType $Tol 1000 $printFlag;
set ok [analyze 1 $dtAnalysis]
test $TestType $Tol $maxNumIter $printFlag;
};
if {$ok != 0} {
puts "Trying tolerance 1.0e-3 ...";
test $TestType 1.0e-3 $maxNumIter 0;
set ok [analyze 1 [expr $dtAnalysis/2.0]]
test $TestType $Tol $maxNumIter $printFlag;
};
if {$ok != 0} {
puts "Trying tolerance 1.0e-3 ...";
test $TestType 1.0e-3 $maxNumIter 0;
set ok [analyze 1 [expr $dtAnalysis/4.0]]
test $TestType $Tol $maxNumIter $printFlag;
};
if {$ok != 0} {
puts "Trying tolerance 1.0e-3 ...";
test $TestType 1.0e-3 $maxNumIter 0;
set ok [analyze 1 [expr $dtAnalysis/8.0]]
test $TestType $Tol $maxNumIter $printFlag;
};
if {$ok != 0} {
puts "Trying tolerance 1.0e-3 ...";
test $TestType 1.0e-3 $maxNumIter 0;
set ok [analyze 1 [expr $dtAnalysis/16.0]]
test $TestType $Tol $maxNumIter $printFlag;
};
if {$ok != 0} {
puts "Trying tolerance 1.0e-3 ...";
test $TestType 1.0e-3 $maxNumIter 0;
set ok [analyze 1 [expr $dtAnalysis/32.0]]
test $TestType $Tol $maxNumIter $printFlag;
};
if {$ok != 0} {
puts "Trying tolerance 1.0e-3 ...";
test $TestType 1.0e-3 $maxNumIter 0;
set ok [analyze 1 [expr $dtAnalysis/64.0]]
test $TestType $Tol $maxNumIter $printFlag;
};
if {$ok != 0} {
puts "Trying tolerance 5.0e-3 ...";
test $TestType 5.0e-3 $maxNumIter 0;
set ok [analyze 1 [expr $dtAnalysis/64.0]]
test $TestType $Tol $maxNumIter $printFlag;
};
if {$ok != 0} {
puts "Trying tolerance 1.0e-2 ...";
test $TestType 1.0e-2 $maxNumIter 0;
set ok [analyze 1 [expr $dtAnalysis/64.0]]
test $TestType $Tol $maxNumIter $printFlag;
};
if {$ok != 0} {
puts "Trying tolerance 5.0e-2 ...";
test $TestType 5.0e-2 $maxNumIter 0;
set ok [analyze 1 [expr $dtAnalysis/64.0]]
test $TestType $Tol $maxNumIter $printFlag;
};
if {$ok != 0} {
puts "Trying tolerance 1.0e-1 ...";
test $TestType 1.0e-1 $maxNumIter 0;
set ok [analyze 1 [expr $dtAnalysis/64.0]]
test $TestType $Tol $maxNumIter $printFlag;
};
if {$ok != 0} {
puts "Trying tolerance 5.0e-1 ...";
test $TestType 5.0e-1 $maxNumIter 0;
set ok [analyze 1 [expr $dtAnalysis/64.0]]
test $TestType $Tol $maxNumIter $printFlag;
};
if {$ok != 0} {
puts "Trying tolerance 1.0 ...";
test $TestType 1.0 $maxNumIter 0;
set ok [analyze 1 [expr $dtAnalysis/64.0]]
test $TestType $Tol $maxNumIter $printFlag;
};
if {$ok != 0} {
puts "Trying tolerance 2.0 ...";
test $TestType 2.0 $maxNumIter 0;
set ok [analyze 1 [expr $dtAnalysis/64.0]]
test $TestType $Tol $maxNumIter $printFlag;
};
test $TestType $Tol $maxNumIter $printFlag;
algorithm $algorithmType;
};
};
puts "End of Dynamic analysis"
wipe;
- Fri Aug 28, 2020 8:31 am
- Forum: OpenSeesPy
- Topic: Convergence problems with force-based elements
- Replies: 7
- Views: 7690
Re: Convergence problems with force-based elements
Sorry for posting here.mhscott wrote: ↑Fri Aug 28, 2020 8:24 am This forum is generally for OpenSeesPy (Python) specific questions.
But, perhaps you can make all your uniaxialMaterials Elastic and see if you have convergence problems.
Here are some steps to follow: https://wp.me/pbejzW-1C
It's difficult to say what the problem is based on your post. A screen shot of the output would help.
I already carried out analysis of the model using a dispbeamcolumn element and it was okay. The only change was replacing the dispbeamcolumn element with a forcebeamcolumn element. This is the analysis output ..
WARNING - ForceBeamColumn3d::update - failed to get compatible element forces & deformations for element: 11111(dW: << 1.83431e-009, dW0: 0.0173102)
WARNING - ForceBeamColumn3d::update - failed to get compatible element forces & deformations for element: 11121(dW: << 1.77563e-006, dW0: 0.0141372)
WARNING - ForceBeamColumn3d::update - failed to get compatible element forces & deformations for element: 11211(dW: << 2.54958e-007, dW0: 0.0318291)
WARNING - ForceBeamColumn3d::update - failed to get compatible element forces & deformations for element: 11221(dW: << 2.59173e-005, dW0: 0.315433)
WARNING - ForceBeamColumn3d::update - failed to get compatible element forces & deformations for element: 11321(dW: << 2.65351e-006, dW0: 0.0124833)
WARNING - ForceBeamColumn3d::update - failed to get compatible element forces & deformations for element: 11111(dW: << 1.83431e-009, dW0: 0.000750978)
WARNING - ForceBeamColumn3d::update - failed to get compatible element forces & deformations for element: 11121(dW: << 1.77563e-006, dW0: 0.000139)
WARNING - ForceBeamColumn3d::update - failed to get compatible element forces & deformations for element: 11211(dW: << 2.54958e-007, dW0: 0.00364059)
WARNING - ForceBeamColumn3d::update - failed to get compatible element forces & deformations for element: 11221(dW: << 2.59173e-005, dW0: 0.00767979)
WARNING - ForceBeamColumn3d::update - failed to get compatible element forces & deformations for element: 11321(dW: << 2.65351e-006, dW0: 0.00086629)
Domain::update - domain failed in update
AlphaOS::newStep() - failed to update the domain
DirectIntegrationAnalysis::analyze() - the Integrator failed at time 0.141
OpenSees > analyze failed, returned: -2 error flag
Trying OSG ...
- Fri Aug 28, 2020 8:04 am
- Forum: OpenSeesPy
- Topic: Convergence problems with force-based elements
- Replies: 7
- Views: 7690
Convergence problems with force-based elements
Hi,
I am modelling a 5-story, 2-bay and 1-bay in the horizontal two directions, RC structure. For performing a nonlinear seismic analysis, I once used a dispbeamcolumn element and then forcebeamcolumn element for modeling both beams and columns. In terms of convergence, the dispbeamcolumn element was okay, but the model with the forcebeamcolumn element is not converging no matter how many integration points I used (I used the max allowable no. of integration points) and used an analysis convergence approach that incorporates different nonlinear algorithms, largely reduced analysis time steps and largely increased tolerance values. But non of this worked. What could be the problem? I appreciate any help in advance.
This is the unconfined concrete material for covers:
uniaxialMaterial Concrete02 10 -40000.00 -0.002000 -8000.00 -0.004000 0.1 -4000.00 3000000.00
the confined concrete material for the core:
uniaxialMaterial Concrete02 20 -44720.00 -0.003180 -44720.00 -0.007690 0.1 -4000.00 3000000.00
the steel material:
uniaxialMaterial Steel02 11 400000.00 200000000.00 0.05 20.0 0.925 0.15 0.005 1.0 0.005 1.0
The column cross-section:
section Fiber 10 {
# define the core patch
patch quad 20 20 20 -0.195 -0.195 0.195 -0.195 0.195 0.195 -0.195 0.195
# define the cover patches
patch quad 10 5 20 -0.225 -0.195 -0.195 -0.195 -0.195 0.195 -0.225 0.195
patch quad 10 5 20 0.195 -0.195 0.225 -0.195 0.225 0.195 0.195 0.195
patch quad 10 20 5 -0.225 -0.225 0.225 -0.225 0.225 -0.195 -0.225 -0.195
patch quad 10 20 5 -0.225 0.195 0.225 0.195 0.225 0.225 -0.225 0.225
# Define reinforcing bars
layer straight 11 3 0.000491 -0.195 -0.195 0.195 -0.195
layer straight 11 2 0.000491 -0.195 0.000 0.195 0.000
layer straight 11 3 0.000491 -0.195 0.195 0.195 0.195
};
uniaxialMaterial Elastic 110 85429.69
uniaxialMaterial Elastic 210 2109375.00
section Aggregator 310 210 Vy 210 Vz 110 T -section 10
The dispbeamcolumn element for columns (each column is defined using 3 elements and 3 integration points) :
element dispBeamColumn 11111 0011 11111 3 310 1 -integration Lobatto
the forcebeamcolumn element for columns (each column is defined using 1 element and 10 integration points):
element forceBeamColumn 11111 0011 0111 10 310 1
I am modelling a 5-story, 2-bay and 1-bay in the horizontal two directions, RC structure. For performing a nonlinear seismic analysis, I once used a dispbeamcolumn element and then forcebeamcolumn element for modeling both beams and columns. In terms of convergence, the dispbeamcolumn element was okay, but the model with the forcebeamcolumn element is not converging no matter how many integration points I used (I used the max allowable no. of integration points) and used an analysis convergence approach that incorporates different nonlinear algorithms, largely reduced analysis time steps and largely increased tolerance values. But non of this worked. What could be the problem? I appreciate any help in advance.
This is the unconfined concrete material for covers:
uniaxialMaterial Concrete02 10 -40000.00 -0.002000 -8000.00 -0.004000 0.1 -4000.00 3000000.00
the confined concrete material for the core:
uniaxialMaterial Concrete02 20 -44720.00 -0.003180 -44720.00 -0.007690 0.1 -4000.00 3000000.00
the steel material:
uniaxialMaterial Steel02 11 400000.00 200000000.00 0.05 20.0 0.925 0.15 0.005 1.0 0.005 1.0
The column cross-section:
section Fiber 10 {
# define the core patch
patch quad 20 20 20 -0.195 -0.195 0.195 -0.195 0.195 0.195 -0.195 0.195
# define the cover patches
patch quad 10 5 20 -0.225 -0.195 -0.195 -0.195 -0.195 0.195 -0.225 0.195
patch quad 10 5 20 0.195 -0.195 0.225 -0.195 0.225 0.195 0.195 0.195
patch quad 10 20 5 -0.225 -0.225 0.225 -0.225 0.225 -0.195 -0.225 -0.195
patch quad 10 20 5 -0.225 0.195 0.225 0.195 0.225 0.225 -0.225 0.225
# Define reinforcing bars
layer straight 11 3 0.000491 -0.195 -0.195 0.195 -0.195
layer straight 11 2 0.000491 -0.195 0.000 0.195 0.000
layer straight 11 3 0.000491 -0.195 0.195 0.195 0.195
};
uniaxialMaterial Elastic 110 85429.69
uniaxialMaterial Elastic 210 2109375.00
section Aggregator 310 210 Vy 210 Vz 110 T -section 10
The dispbeamcolumn element for columns (each column is defined using 3 elements and 3 integration points) :
element dispBeamColumn 11111 0011 11111 3 310 1 -integration Lobatto
the forcebeamcolumn element for columns (each column is defined using 1 element and 10 integration points):
element forceBeamColumn 11111 0011 0111 10 310 1
- Sat Aug 22, 2020 1:00 pm
- Forum: OpenSeesPy
- Topic: Dynamic analysis under bidirectional earthquake
- Replies: 4
- Views: 5370
Re: Dynamic analysis under bidirectional earthquake
i figured out the problem. It is because i defined the element recorder like that:
recorder Element -file Results/Force11111.out -time -ele 11111 section 1 force
But once I deleted the "seciton 1" part, the results are reasonable. But I still don't understand what the results at the section mean?! I though the stresses are integrated along the section and the forces are given exactly as when recording the element response without including the section in the recorder!
recorder Element -file Results/Force11111.out -time -ele 11111 section 1 force
But once I deleted the "seciton 1" part, the results are reasonable. But I still don't understand what the results at the section mean?! I though the stresses are integrated along the section and the forces are given exactly as when recording the element response without including the section in the recorder!
- Sat Aug 22, 2020 12:34 pm
- Forum: OpenSeesPy
- Topic: Dynamic analysis under bidirectional earthquake
- Replies: 4
- Views: 5370
Re: Dynamic analysis under bidirectional earthquake
This is the command I used for the boundary conditionsselimgunay wrote: ↑Sat Aug 22, 2020 12:27 pm This looks like a simply supported boundary condition. I would recommend checking the boundary conditions for the bottom nodes of your columns.
fixY 0.0 1 1 1 1 1 1
- Sat Aug 22, 2020 12:22 pm
- Forum: OpenSeesPy
- Topic: Dynamic analysis under bidirectional earthquake
- Replies: 4
- Views: 5370
Dynamic analysis under bidirectional earthquake
Hi,
I am carrying out dynamic analysis on a 3D RC structure with fixed supports using a bidirectional earthquake. When I extract the straining actions of the base columns at the base section, i get no moments about the x and y axes. why is that? All frame elements are modeled using the dispBeamColumn element.
0.01 -911.536 -0.00131958 -0.00140777 0 0 9.01374e-011
0.02 -911.533 0.0122507 0.0126421 0 0 3.09545e-010
0.03 -911.524 0.0807038 0.0822782 0 0 -3.18308e-008
0.04 -911.51 0.230929 0.236235 0 0 5.27547e-007
0.05 -911.484 0.451771 0.469283 0 0 5.57384e-006
0.06 -911.449 0.69925 0.740998 0 0 2.22992e-005
0.07 -911.408 0.922459 0.998208 0 0 4.31111e-005
0.08 -911.359 1.08531 1.19794 0 0 5.99747e-005
0.09 -911.302 1.18016 1.32252 0 0 8.05646e-005
0.1 -911.238 1.23188 1.38825 0 0 9.47996e-005
0.11 -911.169 1.30013 1.45313 0 0 0.000100139
0.12 -911.089 1.47798 1.61717 0 0 0.000122112
0.13 -910.992 1.84486 1.97374 0 0 0.000167999
0.14 -910.863 2.43329 2.57278 0 0 0.00026348
0.15 -910.695 3.2199 3.40495 0 0 0.000683585
0.16 -910.484 4.12743 4.39641 0 0 0.00344265
0.17 -910.218 5.06711 5.43825 0 0 0.00809269
I am carrying out dynamic analysis on a 3D RC structure with fixed supports using a bidirectional earthquake. When I extract the straining actions of the base columns at the base section, i get no moments about the x and y axes. why is that? All frame elements are modeled using the dispBeamColumn element.
0.01 -911.536 -0.00131958 -0.00140777 0 0 9.01374e-011
0.02 -911.533 0.0122507 0.0126421 0 0 3.09545e-010
0.03 -911.524 0.0807038 0.0822782 0 0 -3.18308e-008
0.04 -911.51 0.230929 0.236235 0 0 5.27547e-007
0.05 -911.484 0.451771 0.469283 0 0 5.57384e-006
0.06 -911.449 0.69925 0.740998 0 0 2.22992e-005
0.07 -911.408 0.922459 0.998208 0 0 4.31111e-005
0.08 -911.359 1.08531 1.19794 0 0 5.99747e-005
0.09 -911.302 1.18016 1.32252 0 0 8.05646e-005
0.1 -911.238 1.23188 1.38825 0 0 9.47996e-005
0.11 -911.169 1.30013 1.45313 0 0 0.000100139
0.12 -911.089 1.47798 1.61717 0 0 0.000122112
0.13 -910.992 1.84486 1.97374 0 0 0.000167999
0.14 -910.863 2.43329 2.57278 0 0 0.00026348
0.15 -910.695 3.2199 3.40495 0 0 0.000683585
0.16 -910.484 4.12743 4.39641 0 0 0.00344265
0.17 -910.218 5.06711 5.43825 0 0 0.00809269
- Tue Oct 15, 2019 3:29 pm
- Forum: OpenSees.exe Users
- Topic: involuntary change of the current directory
- Replies: 0
- Views: 1788
involuntary change of the current directory
Hi,
i am trying to run three files [model.tcl, Gravity.tcl, PushX.tcl] from inside another file using the "source" command:
wipe;
puts [pwd];
source model.tcl;
puts [pwd];
source Gravity.tcl;
source PushX.tcl;
All files are in the same folder. However, when i try running the script, the current directory is changed while executing the first file (model.tcl) and I find my outputs in this other directory and then the second command (source Gravity.tcl;) can't be executed because the current directory is no longer the one where the three files are located. I used the commend "puts [pwd]" to show me the current directory and it can be seen from the results that it has changed after executing the "source model.tcl;" command .. [the results of the pwd commands are put between *** to highlight them]
*** H:/10-story three-bay building/pushover ***
Section UC With Tag 11 Has Been Generated
Section UC With Tag 12 Has Been Generated
Section UC With Tag 13 Has Been Generated
Section UC With Tag 14 Has Been Generated
Section UC With Tag 15 Has Been Generated
Section UC With Tag 21 Has Been Generated
Section UC With Tag 22 Has Been Generated
Section UC With Tag 23 Has Been Generated
End of Define Sections
End of Define Model Elements
*** C:/Users/Abdelrahman Taha ***
couldn't read file "Gravity.tcl": no such file or directory
while executing
"source Gravity.tcl"
(file "RunPushover.tcl" line 7)
<<< Process finished (PID=9944). (Exit code 0)
================ READY ================
why would that happen and how to fix it?
Thanks
i am trying to run three files [model.tcl, Gravity.tcl, PushX.tcl] from inside another file using the "source" command:
wipe;
puts [pwd];
source model.tcl;
puts [pwd];
source Gravity.tcl;
source PushX.tcl;
All files are in the same folder. However, when i try running the script, the current directory is changed while executing the first file (model.tcl) and I find my outputs in this other directory and then the second command (source Gravity.tcl;) can't be executed because the current directory is no longer the one where the three files are located. I used the commend "puts [pwd]" to show me the current directory and it can be seen from the results that it has changed after executing the "source model.tcl;" command .. [the results of the pwd commands are put between *** to highlight them]
*** H:/10-story three-bay building/pushover ***
Section UC With Tag 11 Has Been Generated
Section UC With Tag 12 Has Been Generated
Section UC With Tag 13 Has Been Generated
Section UC With Tag 14 Has Been Generated
Section UC With Tag 15 Has Been Generated
Section UC With Tag 21 Has Been Generated
Section UC With Tag 22 Has Been Generated
Section UC With Tag 23 Has Been Generated
End of Define Sections
End of Define Model Elements
*** C:/Users/Abdelrahman Taha ***
couldn't read file "Gravity.tcl": no such file or directory
while executing
"source Gravity.tcl"
(file "RunPushover.tcl" line 7)
<<< Process finished (PID=9944). (Exit code 0)
================ READY ================
why would that happen and how to fix it?
Thanks