Page 1 of 1

Import of tcl

Posted: Thu Feb 27, 2020 1:57 pm
by Poterium
Hallo. I would like to purchase this software, as I find it very useful. However, I have a qustion that is very important for the usefulness of the software. Is it possible to import a tcl file made without this program, in order to continue the analysis with STKO?

Thank You

Re: Import of tcl

Posted: Thu Feb 27, 2020 2:37 pm
by STKO Team
Dear user,

We do not support importing an existing TCL file. And we are not going to implement it at the moment because it will take too much effort, and even if we do it, what you would import is an already-discretized mesh, while STKO works with CAD Geometries (curves, surfaces, solids).

The main aim would be to stop writing TCL files by hand. What you could do instead is to visualize the results of your model in the STKO post-processor. In this case you can just add the "mpco" recorder command in your TCL scripts, and it will create the output database for STKO.

Try to re-build your model in STKO pre-processor, you will see (after you learn it) that you'll be able to create complex model in few hours.

Best regards

STKO Team

Re: Import of tcl

Posted: Sat Feb 29, 2020 2:31 pm
by Poterium
Thank You for your response,

I am asking because it would be very helpfull to create the model (geometry, restraints, constraints etc) in STKO and then to extract the tcl file and to make additions which are much more easy typing (for example when you have numerous different fiber sections it would be much more easy to put them in the tcl file programming in Python). Then, it would be helpfull to import the tcl file in STKO in order to visualize the results. Moreover, I would like to import older tcl files.
I consider it of great importnace to offer such a possibility.

Kind regards

Re: Import of tcl

Posted: Mon Mar 02, 2020 8:59 am
by STKO Team
Dear Poterium,
I am asking because it would be very helpfull to create the model (geometry, restraints, constraints etc) in STKO and then to extract the tcl file and to make additions which are much more easy typing
Of course you can do this, make your model, then instead of using the "Run Analysis" command, just use the "Write Input File" command. It will just write the TCL file, but it will not run OpenSees automatically.
Then, it would be helpfull to import the tcl file in STKO in order to visualize the results
You can do this too. Take your existing TCL files, write the "mpco" command. This will write the *.MPCO output database that you can visualize in STKO post-processor.
Moreover, I would like to import older tcl files
Yes we understand that it would be nice to have your older models be editable in the STKO pre-processor. If we find time for it and if more and more users ask for this feature we can considere implementing it.

Re: Import of tcl

Posted: Mon Mar 02, 2020 10:49 am
by Poterium
You can do this too. Take your existing TCL files, write the "mpco" command. This will write the *.MPCO output database that you can visualize in STKO post-processor.
Thank you. Can I make changes to the model or only see the results? I understand that only see the results. Is that right?

Re: Import of tcl

Posted: Thu Mar 05, 2020 10:31 am
by STKO Team
You can either do your model in STKO, then write the tcl file from STKO, and then you can modify them before running the analysis.
Otherwise, if you already have hand-written TCL files, you can add manually the "mpco" recorder command and see the results in STKO post processor

Re: Import of tcl

Posted: Sat Mar 07, 2020 11:34 am
by Poterium
I did not understand. If I build the model in STKO and then export it in tcl file, then make modifications in this file and import it back, can I continue editing it in STKO?

Re: Import of tcl

Posted: Mon Mar 09, 2020 8:50 am
by STKO Team
No, if you export TCL files and then you modify them manually you can't import them back in STKO. What you could do is to use the AnalysisStep "Custom command" that is basically a TCL script. It is typically used to create operations that are not available in STKO. In this way your TCL script is part of the *.SCD file.