Version reporting function

A forum dedicated to feature requests and the future direction of OpenSees, i.e. what would you like, what do you need, what should we explore

Moderators: silvia, selimgunay, Moderators

Post Reply
divamva
Posts: 27
Joined: Wed Jun 30, 2004 6:52 am
Location: National Technical University of Athens

Version reporting function

Post by divamva »

It may prove useful to have a function available in the Tcl interface that would report what version of openSEES is currently running. It will probably help to ensure that any structural model is running on an up-to-date version of OpenSEES, at least as up-to-date as it needs!

This should be incredibly simple to implement.
silvia
Posts: 3909
Joined: Tue Jan 11, 2005 7:44 am
Location: Degenkolb Engineers
Contact:

Post by silvia »

doesn't it say it on top???
Silvia Mazzoni, PhD
Structural Consultant
Degenkolb Engineers
235 Montgomery Street, Suite 500
San Francisco, CA. 94104
Nero
Posts: 51
Joined: Wed Jun 22, 2005 2:19 am

Post by Nero »

silvia wrote:doesn't it say it on top???
I may be wrong, but I think what he means is the ability to grab the version while executing a script. That way you could compare the current version to any requirements the script has, and then output a warning/error if the version is too old.

Ex, if there was a command, "CurentVersion" that returned the current running version of OS:

Code: Select all

set ReqVersion 1.7
if { $ReqVersion > CurrentVersion } {
  puts "Warning: You must be running OpenSees 1.7 to run this script"
else {
  #execute analysis here.
}
Something like that.
divamva
Posts: 27
Joined: Wed Jun 30, 2004 6:52 am
Location: National Technical University of Athens

Post by divamva »

Thanks Nero, that is exactly what I mean. In this way you can send a script to your collegues and they will immediately receive the proper error (incorrect version of openSEES) rather than a cryptic error about a material model not being present.
Nero
Posts: 51
Joined: Wed Jun 22, 2005 2:19 am

Post by Nero »

divamva wrote:Thanks Nero, that is exactly what I mean. In this way you can send a script to your collegues and they will immediately receive the proper error (incorrect version of openSEES) rather than a cryptic error about a material model not being present.
One problem I see is this- none of the past versions have this command, thus, they will end up with just a random error for the "CurrentVersion" command or whatever it would be. It'll be beneficial for the version that introduces the command, but would not be of any help to someone who has, say, v. 1.6
Post Reply