BuildingTcl Release 1.3 is up on NEESforge

[silvia]

i have a new release for BuildingTcl in NEESforge:

neesforge.nees.org/


i have mainly updated the viewer.

I welcome and appreciate any recommendations/comments on BuildingTcl.

[hrodrigues]

i have a problem.
i can't run it.

impossible to find tcl85.dll
how to solve it ?
Hugo

[silvia]

have you installed the latest Tcl.

the latest opensees goes with the latest Tcl.

[hrodrigues]

Silvia,

the ActiveTcl 8.5.5.0 for Windows is already available i install it and it works.
http://www.activestate.com/store/downlo ... 0dcd6f4078

the 8.5 version is not available in the OS downloads.


one more question .. the OpenSeeS.exe 2.0.0 have 5.21MB and the OpenSeeS.exe included in the BuildingTcl have 5.28MB any differences ??
tkx

Hugo

[silvia]

it's the very very latest, not yet released! (look at the file date)
shhh, don't tell Frank!

try executing the os file that comes with it, does it complain?

[hrodrigues]

ok!
no problems now ...

thank you!!

[hrodrigues]

Silvia,

The BuildingTcl is very good.
I’d like to know if for 3D buildings there is anything coming ?

[silvia]

i'm working on it!
i welcome any and alll comments, good and bad!

thank you for trying it.

[jefferyr]

Some thoughts/observations:

The current design of OpenSees has the use of procedures with arguments.

The current design of BuildingTcl uses procedures to define key/value pairs.

Would it be possible to change the main procedures within OpenSees to call
new procedures that are empty for a standard installation of OpenSees, and
defined if BuildingTcl is being used?

example pseudocode:

proc uniaxialMaterial { type
IDconcCore
fc1C
eps1C
fc2C
eps2C
lambda
ftC
Ets } {

define_stuff $type $IDconcCore ... $Ets;

... do normal OpenSees stuff ...

}

#
# If BuildingTcl is being used.
#
proc define_stuff { type IDconcCore ... Ets } {

addMaterialData ...
addMaterialData ...
.
.
.
addMaterial
}

#
# If BuildingTcl is NOT being used.
#
proc define_stuff { type IDconcCore ... Ets } {

# do nothing
}

This would allow the required commands to populate the dB to be transparent to the user
and allow old OpenSees files to be used with BuildingTcl. Since these new procedures would
be called only once per analyze call, the performance hit should be negligible.

The alternative would be to supply scripts that automatically modify the 'old' OpenSees tcl
input files and insert the new required commands in place of the old.

Comments would be appreciated.

Thanks

[silvia]

i'm a little confused.
you can still use old opensees files within buildingTcl.... but they wouldn't be picked up in the database, no.....
right now buildingTcl does the translation from its language to OS language. translating back would be another set of work...

please explain more.

[ryotsu]

I tried as stated above, but doesn't seem to work for me too.

[samdbgt]

I think this latest Tcl release has some bugs in it. It just does not run in my machine. What is the configuration that this needs to run smoothly in a 2013 machine. Well, I have one of the best configurations of 2013.





---------------------------------
CORBIN GRAVELY
http://www.qspray.com/
--------------------------------