SOFiSTiK

Basics
Version 2010

E SOFiSTiK AG, Oberschleissheim, 2010

SOFiSTiK

Basics

This manual is protected by copyright laws. No part of it may be translated, copied or reproduced, in any form or by any means, without written permission from SOFiSTiK AG. SOFiSTiK reserves the right to modify or to release new editions of this manual. The manual and the program have been thoroughly checked for errors. However, SOFiSTiK does not claim that either one is completely error free. Errors and omissions are corrected as soon as they are detected. The user of the program is solely responsible for the applications. We strongly encourage the user to test the correctness of all calculations at least by random sampling.

Basics
1 1.1. 1.2.

SOFiSTiK
11 11 11 21 21 23 23 23 24 24 25 27 27 210 211 211 214 215 215 31 31 31 32 32 35 41 41 43 43 43 47 411 411 412 51 51

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SOFiSTiK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Examples for the Use of the Software . . . . . . . . . . . . . . . . . . . . .

2 How to use SOFiSTiK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1. Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2. Program Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.1. Preprocessing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.2. Analysis Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.3. Design Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.4. Postprocessing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3. User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4. Input Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5. Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6. Interactive Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7. News . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.8. Name Conventions of the SOFiSTiK Files. . . . . . . . . . . . . . . . . . 2.9. Backup of Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.10. SOFiSTiK Options.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.10.1. Language Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.1. 3.2. 3.2.1. 3.2.2. 3.3. 4 4.1. 4.2. 4.2.1. 4.2.2. 4.2.3. 4.3. 4.3.1. 4.4. 5 5.1. Graphical Input SOFiPLUS(X). . . . . . . . . . . . . . . . . . . . . . . . . . General Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Work Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Start without the program Structural Desktop (SSD) . . . . . . . Start out of the program Structural Desktop (SSD) . . . . . . . . . Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SSD SOFiSTiK Structural Desktop. . . . . . . . . . . . . . . . . . . . . User Interface SSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic Work Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Template Files name.sofistix . . . . . . . . . . . . . . . . . . . . . . . . . . . . Structure and Function Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculation Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Special Features for Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Input with TEDDY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i

SOFiSTiK
5.2. 5.3. 5.4. 5.4.1. 5.4.2. 5.4.3. 5.4.4. 5.5. 5.6. 5.6.1. 5.6.2. 5.6.3. 5.6.4. 5.7. 5.8. 5.8.1.

Basics
52 53 54 55 55 55 56 57 58 58 59 510 511 511 514 515 61 62 62 62 62 62 63 63 64 64 64 65 65 65 65 66 67 67 68 69 612 615

Support of international character codes (UTF8) . . . . . . . . . . . Starting the Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Combinations with the Altkey (selection) . . . . . . . . . . . . . . . . Combinations with the Ctrlkey (selection) . . . . . . . . . . . . . . . Overview of all Ctrl / AltCommands . . . . . . . . . . . . . . . . . . . . Example with Column Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . Input of Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Help and Interactive Manuals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activating the Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Acrobat Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Your own Comments . . . . . . . . . . . . . . . . . . . . . . . . . . Export/Import of Annotations in Manuals . . . . . . . . . . . . . . . . . TEDDY the SOFiSTiK Commander. . . . . . . . . . . . . . . . . . . . . . Special Features of SOFiSTiK . . . . . . . . . . . . . . . . . . . . . . . . . . . . TEDDY Information Centre . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6 CADINP Input Language. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1. Definitions and Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1.1. Lines (physical sentences) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1.2. Records (logical structure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1.3. Separation Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1.4. Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2. Input Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.1. Basic Input Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.2. Default Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.3. Repetition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.4. Increments/Decrements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.5. Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.6. Record Continuation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.7. Record Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.8. Positioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.9. Defining Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.10. HelpRecord . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.11. Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.12. List of Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.13. LET and STO Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.14. Arithmetic Expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.15. FUN Definition of functions . . . . . . . . . . . . . . . . . . . . . . . . . . . ii

Basics

SOFiSTiK
615 616 618 619 620 620 624 625 625 626 626 627 627 628 629 632 635 635 635 636 636 636 637 638 638 639 640 641 643 644 645 646 646 647 649 71 81 81

6.2.16. Conversion of Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.17. LOOP,ENDLOOP Loops and Jumps . . . . . . . . . . . . . . . . . . . 6.2.18. IF Logical Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.19. @CDB Selection of a CDBASE . . . . . . . . . . . . . . . . . . . . . . . 6.2.20. @KEY Access to the CDBASE . . . . . . . . . . . . . . . . . . . . . . . . 6.2.21. @() Access to the CDBASE . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3. General Records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.1. HEAD Title Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.2. END End of an Input Block . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.3. TXB Introducing Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.4. TXE Concluding Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.5. <TEXT> Text block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.6. </TEXT> End of a text block . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.7. ECHO Output Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.8. PAGE Control of Input/Output . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.9. SIZE Graphic Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4. Generation of Pictures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.1. <PICT> Start of a picture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.2. GNT Scale of a picture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.3. GPL Polyline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.4. GPM Polymarker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.5. GFA Fill Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.6. GGDP Generalized Drawing Primitive . . . . . . . . . . . . . . . . . . 6.4.7. GTXT Text Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.8. GSCA Dimensioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5. Attributes of Graphic Representations . . . . . . . . . . . . . . . . . . . . . 6.5.1. GCOL Colour Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5.2. GPLI Polyline Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5.3. GPMI Polymarker Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5.4. GTXI Text Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5.5. GFAI Fill Area Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6. Insertion of a Picture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6.1. <LINK> Insertion of a Picture . . . . . . . . . . . . . . . . . . . . . . . . . 6.7. Parametric Input. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.8. Compatibility of Data files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 8 8.1. DEF Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . Starting an Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

SOFiSTiK
8.2. 8.3. 8.4. 8.5. 8.6. 8.7. 8.8. 8.9. 8.10. 9 9.1. 9.2. 9.3. 9.3.1. 9.3.2. 9.3.3. 9.3.4. 9.3.5. 9.3.6. 9.3.7. 9.3.8. 9.4. 9.4.1. 9.4.2. 9.4.3.

Basics
81 83 85 86 87 88 89 810 812 91 91 91 92 92 92 92 94 94 96 98 910 911 911 911 911 101 101 102 102 103 103 104 104 105 105 105 106 107

#DEFINE Parameter Substitution . . . . . . . . . . . . . . . . . . . . . . . #INCLUDE Block Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . #IF Conditional Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Iteractive Analysis with Multiple Modules. . . . . . . . . . . . . . . . . . . Operating System Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . Job History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Start of a Single Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Special Features for Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Protocol File (.PRT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Result File (.LST and .ERG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printout with URSULA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activation of URSULA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Support of international character codes (UTF8) . . . . . . . . . Printing Dialogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Advanced Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Functions in control tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Special Features for Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Graphical Output GRAFiX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Work Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.1. General Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.2. Standard Warnings and Error Messages . . . . . . . . . . . . . . . . . . . 10.3. Troubleshooting Strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.3.1. Problems with Database (*.cdb) . . . . . . . . . . . . . . . . . . . . . . . . . 10.3.2. Input Error in TEDDY Datafile . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.3.3. Error in System Generation with SOFiPLUS . . . . . . . . . . . . . . 10.3.4. Error during Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.3.5. Problems with Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.4. Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.4.1. Support Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.4.2. Customers Obligation to Cooperate . . . . . . . . . . . . . . . . . . . . . 10.4.3. Support Request via SOFiSTiK Online Portal . . . . . . . . . . . . . iv

Basics

SOFiSTiK
107 108 111 111 112 113

10.4.4. Support Request out of SSD / TEDDY . . . . . . . . . . . . . . . . . . . 10.4.5. Create a Diagnostic.xml File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 11.1. 11.2. 11.3. Additional Information and Help . . . . . . . . . . . . . . . . . . . . . . . . Infoportal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CADINP Samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Forum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SOFiSTiK
This page intentionally left blank

Basics

vi

Basics
1
1.1.

SOFiSTiK
Introduction.
SOFiSTiK

The SOFiSTiK AG develops and distributes engineering software with particular emphasis on civil and structural engineering. The software has been developed following a sofisticated concept, allowing the standard user to reach a quick and efficient solution to a given task. Despite this the possibilities for a specialist with large experience in numerical methods are not restricted. The software is made up of a modular structure and provides general available open interfaces. The modules numerical kernels are classic batch programs, these in turn are getting their input from small text files and a database. For each program module there is an own manual. The manuals contain information about the theoretical backgrounds and descriptions for the input and output of the programs. We recommend to inform about the respective program module in the corresponding manual before using the program.

1.2.

Examples for the Use of the Software

For each program there are introducing examples. A part of these examples are more detailed described in the respective manual. The input files for these examples are to be found in the installation directory SOFiSTiK in the respective subdirectories program_name\english. Furthermore the users have the possibility to get information about many features of SOFiSTiKSoftware on the home page of the SOFiSTiK AG (www.sofistik.com) with the link Infoportal. Detailed examples do not only show the power of these programs but may be used as templates for your own solutions.

Version 2010

11

SOFiSTiK

Basics

Link Infoportal You can find further information about examples and help for the programs in this manual chapter 11: Additional Information and Help.

12

Version 2010

Basics
2
2.1.

SOFiSTiK
How to use SOFiSTiK.
Principles

The centre of SOFiSTiK analysis programs is a very efficient database (CDBASE). A set of programs, which are addressed by standard text files or by graphical user interfaces, interchange all their information through this database. SOFiSTiKSoftware consists of numerous different modules. For all beginners the SOFiSTiKStructuralDesktop SSD is the best choice because it will handle many of the complex interactions between the modules. There is a separate tutorial available, a short introduction may be found in the manual SOFiSTiK Bases (sofistik_1.pdf). To exploit the full power of the software it is useful to know the modular structure and the CADINPcommand language as this is the most powerful and the most basic access method. An experienced user will never disaccustom himself from the flexibility of applying CADINP macros, especially for large complex systems. Especially the possibility to keep all secondary information in comments and formulas is a very valuable feature. There is the following organisation and operating structure: Input file or database creation manually or using a generation program Performing the Analysis Output of results The process is not ruled by any rigid system, which means that the software is very flexible. The user can always choose the most effective form of input for his purposes and is only constrained by minimal obligations in sequences of analysis. Moreover it is possible to transfer data between different computers and operating systems without difficulty.

Version 2010

21

SOFiSTiK

Basics

22

Version 2010

Basics
2.2. 2.2.1. Program Modules Preprocessing

SOFiSTiK

interactive programs: CrossMAX SOFiPLUS MONET COLUMN FOOTING Batchprograms: AQUA SOFiMSHA SOFiMSHB SOFiMSHC SOFiLOAD TENDON CSM Materials and Cross Sections Import and Export of Finite Elements and Beam Structures Generation of Finite Element Meshes from Geometry Definitions Geometry modeling and Generation of Finite Element Meshes Loadgenerator for Finite Elements and Frameworks Geometry of Prestressing Tendons Construction Stage Manager Graphical input of cross sections with AutoCAD (part of SOFiPLUS) Graphical Input of FEmeshes in AutoCAD Graphical input of FEmeshes Generation of input data for columns Graphical input of foundations (all not described within this manual)

2.2.2.
STAR2 PFAHL ASE HASE SEPP TALPA PHYSICA DYNA

Analysis Programs
Statics of Beam Structure Theory of 2nd Order Statics of ThreeDimensional Pile Structures General Static Analysis of Finite Element Structures Halfspace and other Stiffness Elements Statics of Plane Plates and Disks Statics of Plane or Axisymmetric Geomechanical Structures Multiphysics powered by MPS Dynamic Analysis

Version 2010

23

SOFiSTiK
ELLA HYDRA Extended Live Load Analysis

Basics
Seepage and Thermal Analysis with Finite Elements Analysis of thermal problems

2.2.3.
MAXIMA BDK AQB BEMESS WIST

Design Programs
Superposition Lateral Torsional Buckling for Steel Cross Sections Design of Cross Sections and of Prestressed Concrete and Composite Cross Sections Design of Plates and Shells Angular Retaining Walls (system and design)

2.2.4.

Postprocessing
Graphical Representations of Finite Elements and Beam Structures Selective Printing of Data from the Database (will be integrated in GRAFIX)

interactive programs: WiNGRAF DBVIEW Batchprograms: AQUP WING DBPRIN SIR DYNR PROT TEXTILE Graphical Representation of General Cross Sections Graphical Representations of Finite Elements and Beam Structures Print Results from the Database Sectional Results Transient Results and Response Spectra Preparation of Tendon Protocols Cutting Pattern Membrane Structures

24

Version 2010

Basics
2.3. User Interface.

SOFiSTiK

After the installation of the software the explorer has linked several file extension types to SOFiSTiK programs and allows a direct start:

These file types recognized by the explorer have the following contents: The extensions .SOFISTIK are the project files of the SDD (SOFiSTiK Structural Desktop). The extensions .NDB are the project files for the program MONET. They contain only the data used by MONET. The extensions .DAT are input files A double click will open the program TEDDY, with the right mouse button you have access to WPS (run)

Version 2010

25

SOFiSTiK

Basics

The extensions .CDB are database files a double click will open the program Animator, with the right button mouse you have access to: Dbinfo Programmers diagnose tool Export SOFiSTiK Export Graphic Graphical presentation of data Tendon Graphical input of tendons Unlock Remove data base locks The extensions .PLB are output files containing text and graphics. The double click will invoke URSULA. The extensions .PRT contain the log of the total analysis. They contain information about error messages and warnings, statistics, parameters of the equation system, memory usage and analysis time. The extensions .ERG are classical output files in text format. They have the similar content as the .PLB, but do not contain pictures. The extensions .LST are the components making the ERG file. The LST file always contains the result of the last module and may be helpful for fast error tracking. The extensions .DBV are documents for the program DBVIEW, they contain the parameters of certain tabular views on contents of the CDBASE. GRA The extensions .GRA are CADINP input files of the program WiNGRAF and can be opened and modified with TEDDY.

26

Version 2010

Basics
2.4. Input Files.

SOFiSTiK

The input files are in a free input form in the socalled CADINPformat (see Chapter 5). This is a programmable macrolanguage which makes very efficient input handling possible. For a static position there are multiple, even nested files possible. The files with the extensions .AQU, .KNO, .ELM, .LAS are files generated by MONET, which are linked to the DAT (input) files. The file .AQU contains material and crosssections, .KNO the nodes, .ELM the elements and .LAS the loads. The extensions .SIR are input files which are generated by the program SIR. They can be opened and modified with TEDDY. The extensions .SOFISTIX are special presentation files of the SDD (SOFiSTiK Structural Desktop). Using these files you can get default inputs in the SSD for selected systems for a further processing.

2.5.

Database

For each position of an analysis system one database with a project name and one or more data files are created. The database can be valuable in large projects and therefore it should be saved via Backup. In this context the term system is defined as the sum of all parts of a structure or substructure, which interact statically during their lifetime. The programs SOFIMESH or SOFiPLUS generate the analysis system for the structure being analyzed. The total number and the type of the elements are thus definitely defined. However for the analysis a partial system can be used. This is defined by the group number, which is the truncated quotient of the element number divided by a group divisor (e.g.1000). The user should keep this structuring in mind from the earliest stages of the design. Boundary conditions and material constants can be modified as desired. Load cases can be analysed or superimposed by the use of certain modules. Design can be carried out and results can be presented graphically. All results are saved as the most recent values. The analysis of a load case with modified loads overwrites the previous results. When crosssections are modified, all the results that depend on them (reinforcement, stresses, etc.) are deleted if not specified otherwise.

Version 2010

27

SOFiSTiK

Basics

The database is managed by the system CDBASE. Its index sequential structure allows an effective access via a double key. The description of the data is given via the file CDBASE.CHM, the subroutines can be obtained by users for programming purposes. A database can be transferred in both ways to and from the AutoCAD based system SOFiPLUS. A fully interactive program named DBINFO is available for handling the database. It not only prepares statistical information but also allows for various output and editing possibilities and has a powerful copy function. The program DBINFO can be called with one of the following possibilities: from the command shell call of the command shell in the TEDDY with icon call DBINFO input of the database name from the TEDDY right mouse button > Database... > Information from the Explorer Marking the database (name.cdb) right mouse button > Open Dbinfo

28

Version 2010

Basics
After calling the program DBINFO the following menu appears: a s l m Access history Structure (Eements) Loadcases Merge 2nd database o Output medium b create a backup

SOFiSTiK

d Dump of records

g output with 8 Digits ON

e Edit records ** on your own risk only ! z Clear the error flag (Clear all locks if called via DBINFO project,Z) q quit Please press the desired key Option a prints a log file of all the programs that accessed the database. Options s and l give information about the load cases and the elements stored in it. Option m allows the import of load cases from another database. Although, this only makes sense when both databases contain the same analysis system. Such a need exists mainly for very large systems when several colleagues analyze different scenarios for the same system. When running DBINFO project,Z all error flags and all the record locks will be removed. These result from a program crash for example. The removing of the locks is also possible in the TEDDY with the right mouse button > Database... > clear locks or in the Explorer with the right mouse button > Open Unlock. HINT: In the SOFiSTiK environment (Cmp. DEF Enviroment Variables) you can change the parameter CDACCESS=SINGLE. This will deactivate the multitasking possibilities and no record logs are created. Option d displays content of the database. Option e allows the user to change the content of the database. You only should do so on explicit order by a SOFiSTiK supporter. A description of the content of the data base would be advantageous for this purpose.

Version 2010

29

SOFiSTiK
2.6. Interactive Modules.

Basics

The modular structure reflects itself in the conception of the interactive modules. Instead of a single window which changes between input and output views, the user can open several programs with different windows which exchange messages and have access to the same database. To change between the windows there are function keys and icons in the tool bar within TEDDY, WPS, URSULA and other programs: The program WPS (wps.exe) to perform the analysis The program ANIMATOR for animated views of structures and results The program URSULA to view and manipulate the printout including graphics With TASKS it is possible to insert different analysis or design tasks (in analog mode to the tasks SSD SOFiSTiK Structural Desktop). The program GRAFiX to generate sofisticated true scale drawings of system, loading and results The program WINGRAF to generate sofisticated true scale drawings of system, loading and results The program DBVIEW to create tables with numerical contents of the database and graphic functions. (The program will be integrated into WINGRAF) The program MONET for the graphic construction and mesh generation of system and loading

210

Version 2010

Basics
2.7. News

SOFiSTiK

SOFiSTiK programs are under continuous development. The manuals are not printed therefore on a regular basis, but are packed together with the programs as PDF files. The changes in the programs are gathered in HTMLLOG files, and are available for the user in several ways: SOFiSTiK publishes these files via the Internet. TEDDY includes in its help an option for the LOG files.

2.8.

Name Conventions of the SOFiSTiK Files.

The most important files of SOFiSTiK software are the input files and the database (.CDB). The other types of files are: The files of the SOFiSTiK programs have various extensions which have the following meanings: .EXE .DLL .CMD .ERR .TAB .TAX .TBB .HTM .PDF .CHM .WTM .DEF .INI Execution program (MSDOS/Windows) Shared dynamic link library (Windows) Batch file Error file of a program containing all error messages, input records and output text in various languages Contains other external data for programs (Tables) Contains user specific attitudes Contains compiled data of the .TAB files. Latest changes file These files contain the changes to each program since the last manual, as well as the corrected errors. Adobe portable document format (Manuals) Compressed HTML help files Windows macro file for TEDDY Definition file for parameters Parameter file for design codes

Version 2010

211

SOFiSTiK
The following files result from an analysis: .DAT .DWG

Basics

Input file, (not mandatory) Input file for plan from SOFiPLUS, in which the analysis system and the load are entered .SOFISTIK project files of the SDD (SOFiSTiK Structural Desktop) .SOFISTIX template file of the SDD (SOFiSTiK Structural Desktop) .AQU Input file for crosssections from MONET generated .KNO Input file for nodes from MONET generated .ELM Input file for elements from MONET generated .LAS Input file for loads from MONET generated .GRA Input file from WINGRAF generated .DBV Document from DBVIEW .NDB .NBK .NDA .LST .ERG .PRT .PLB .CDB .CDE .$Dn .zdn Database for MONET Backup of database for MONET Backup of database for MONET for reorganization Output files of the individual programs Output files of the entire analysis Protocol file of the entire analysis Result file with text and graphics Database, should not normally be deleted. Eigenforms of dynamic analysis As well as other files with $ (Windows) or z (Linux) and a letter and number. Restart files (e.g. stiffness matrix) may be deleted; however, these files may have to be regenerated later, which can demand significant computing time. As well as other files with $ (Windows) or z (Linux) and two numbers: Temporary work files that can always be deleted. Usually these files are deleted by the program itself if it finishes properly. Files with wild number combinations in their names are auxiliary files of the operating system, which can no longer be deleted due to a warm start of the computer.

.$0n .z0n

212

Version 2010

Basics
.$$$ .zzz .#nn .ynn .### .yyy .SDB

SOFiSTiK
Auxiliary files under Windows which can be deleted. Auxiliary files under Linux which can be deleted. Auxiliary files under Windows which can be deleted. Auxiliary files under Linux which can be deleted. These are errorlog files under Windows which can be deleted. These are errorlog files under Linux which can be deleted. Shadow database: This file is usually deleted by closing of all involved programs.

Version 2010

213

SOFiSTiK
2.9. Backup of Data.

Basics

Last but not least it must be mentioned that all valuable data can be destroyed under certain circumstances. Beside clumsiness of the user, information on the hard disk can be destroyed due to faulty hardware, operating system faults or even a program error. Thus you must regularly make Backup copies using the COPY or BACKUP command, this information you can save to floppies or other media. The basic rule is that valuable information should always be stored in three independent medias, because an error during a Backup may destroy both the copy and the original. Input data should be backuped daily. In the case of larger projects the entire database, which is often the result of several weeks of analysis, should be backuped in regular intervals. Important data is considered to be your created DATfiles as well as the files .SOFISTIK and the project files .NDB or .DWG. If your CDB contains important information you may create a condensed Backupversion via DBINFO. Within TEDDY there is a function to delete unimportant files in your project directories (clean up).

214

Version 2010

Basics
2.10. SOFiSTiK Options.

SOFiSTiK

For the SOFiSTiK programs there are three setting menus available for the specific SOFiSTiK settings. Menu SOFiSTiK > User Options Storage location Options for the individual PC These settings are stored in the Registry database. Superordinate options for all projects These settings are stored in a file SOFiSTiK.DEF in a parent directory, usually this is the SOFiSTiK programs directory. ** Options belonging to the project These settings are stored in a file SOFiSTiK.DEF in the current project directory. ***

SOFiSTiK > Global Options

SOFiSTiK > Project Options

**

In a network installation it is possible, to store the file SOFiSTiK.DEF into a parent directory on the network. In this case, an environment variable SOFiSTiK = network path has to be set.

*** The settings of the file SOFiSTiK.DEF in the project directory overwrite the default settings of the parent directory (Global options).

2.10.1. Language Settings

There is a difference between the language of the dialogues and the input and output language of the files. The language of the dialogues is stored within the Registry database on the local computer and is adjustable under SOFiSTiK > User Options. The program must be restarted to activate this change.

Version 2010

215

SOFiSTiK

Basics

The input or output language of the files is saved in a file SOFiSTiK.DEF. Depending on whether this linguistic setting should be valid for all projects or only for one single project, the setting is done with SOFiSTiK > Global Options or SOFiSTiK > Project Options.

216

Version 2010

Basics
3
3.1.

SOFiSTiK
Graphical Input SOFiPLUS(X).
General Hints

SOFiPLUS(X) is a CADbased preprocessor to define structures and loads for analysis with SOFiSTiK programs. SOFiPLUS can be purchased as a pure addon to AutoCAD or included with an integrated AutoCAD ORM engine as SOFiPLUSX. The program writes directly into a SOFiSTiK database while generating a result file and a file to control the calculations. For the structural analysis SOFiSTiK structural programs are needed.

3.2.

Work Flow

The general work flow is described in the manual SOFiPLUS_1.PDF. Additionally you can find examples and tutorial movies for the individual features at the link Infoportal at the homepage of the SOFiSTiK AG (www.sofistik.com).

Version 2010

31

SOFiSTiK
3.2.1.

Basics

Start without the program Structural Desktop (SSD)

SOFiPLUS(X) is started via the Program Manager or from the link on the desktop. For working with SOFiPLUS(X) an existing drawing of a structure is used or the structure is drawn directly. Then a structural system with the appropriate database and AutoCAD units is defined. Now the structural system and the loads can be defined. The SOFiSTiK database for subsequent analysis use will be generated via the program SOFiMSHC.

3.2.2.

Start out of the program Structural Desktop (SSD)

The program SSD is started via the Program Manager or from the link on the desktop. Starting a new project the dialog box SOFiSTiK: System Information start appears on the screen, because working without a database is not possible. The kind of preprocessing is set to SOFiPLUS(X) graphical Preprocessing. Therefore the part below is filled and additional settings for working with SOFiPLUS(X) can be configured.

32

Version 2010

Basics

SOFiSTiK

After closing the dialog box with OK several tasks are inserted in the project tree to the left. By doubleclicking the task GUI for Model Generation (SOFiPLUS(X)) the program SOFiPLUS(X) is started. Now the structural system and the loads could be defined. The SOFiSTiK database will be generated via the program SOFiMSHC. To set the default kind of preprocessing to SOFiPLUS(X) graphical Preprocessing use the global options (pulldown menu SOFiSTiK Global Options ...).

Version 2010

33

SOFiSTiK

Basics

34

Version 2010

Basics
3.3. Structure

SOFiSTiK

After starting SOFiPLUS(X) the following screen will appear:

The commands can be accessed via different tools (menus, toolbars, ribbons). Warnings and/or errors during writing into the database will be displayed in the sidebar. To become acquainted with the program SOFiPLUS(X) you can retrieve an example project from the Infoportal. Additionally you can find explanations for a graphical input with SOFiPLUS(X) by means of examples in the SSD tutorial (SSD_TUTORIAL_1.PDF). Training courses for SOFiPLUS(X) as well as for the program SSD are offered regularly

Version 2010

35

SOFiSTiK
This page intentionally left blank

Basics

36

Version 2010

Basics
4
4.1.

SOFiSTiK
SSD SOFiSTiK Structural Desktop.
User Interface SSD

The SOFiSTiK Structural Desktop (SSD) represents a uniform user interface for the total range of SOFiSTiK software. The module controls preprocessing, processing and postprocessing. A double click on the program icon or a sofistikfile will start the program TEDDY The system can be entered graphically with SOFiPLUS(X) or as parameterized text input using TEDDY. The control of the calculation and design process takes place using dialogue boxes, which are accessed via the task tree.

Version 2010

41

SOFiSTiK
The screen is divided into three main areas.

Basics

task tree

table area

work area

42

Version 2010

Basics

SOFiSTiK

4.2.

Basic Work Flow

The SSD is task oriented. The tasks are arranged in groups (e.g. the group System contains the tasks for materials, cross sections, geometry, loads and combination rules). When creating a new project, the necessary groups and tasks are set by default depending on the chosen problem.

4.2.1.

Groups

The computational groups are organized in a treestructure. This structure can be changed by the user at any time, as the individual tasks can be dragged to the desired place with the mouse. The user can remove or insert additional groups at any time with associated tasks. Example of a possible groupstructure of the SSD: System: System, loads and combination rules Linear Analysis: Calculation and superposition Design Area Elements: Design ULS and SLS

4.2.2.

Tasks

The tasks available are accessed via the rightclickmenu in the task tree. They can be normally inserted at any place within the tree. When you select the command Insert Task with the right mousebutton, the following dialogue with all available tasks appears.

Version 2010

43

SOFiSTiK

Basics

44

Version 2010

Basics
Task Tree

SOFiSTiK

In the task tree the options are accessed via the rightclickmenu which automatically adjusts itself to show only those available. Right click menu in the task tree The right click menu will provide relevant functions for the selected task. Examples: Process Edit Reports > Dialogue > Text Input (name.dat) > Result viewer (name.plb)

Table Area Database information is written in the table area: Possible categories: Geometry Loads Results These results can be copied with right click menu into the clipboard. Possible format: Text format EXCEL format

Version 2010

45

SOFiSTiK
Work Area

Basics

The work area displays the ANIMATOR visualisation of the system by default. The work area changes to WinPS during processing to show calculation status and the TEDDY for further text input prior to analysis. The graphical input with SOFiPLUS(X) operates within its own separate window making the best possible use of dual monitors.

46

Version 2010

Basics
4.2.3. Template Files name.sofistix

SOFiSTiK

For processing of frequently recurrent standard tasks, the Template files of the type name.sofistix are provided. General templates are saved in a subdirectory of the SOFiSTiK directory, for example C:\Programs\SOFiSTiK\2010\ANALYSIS.25\ SSDTemplates. Adding User defined Template Directories For own Templates, the user can define further template directories. SOFiSTiK > User Options > SSDTemplate Path > (FindButton and Add )

In this directory, further subdirectories can be created. These subdirectories appear as tabs and template icons. There is only one level of subdirectories available.

Version 2010

47

SOFiSTiK
User Defined Template Files

Basics

Any file name.sofistik can be stored into the desired template directory as template name.sofistix. All current project settings can be saved as templates including the arrangement and sequence of the tasks. The materials and cross sections are dependent on the chosen design code. A fixed design code cannot be changed within the project. File > Save Project As Template ...

A later changing of the code is possible if the template is stored with Save tasks without Design Code dependant information.

48

Version 2010

Basics

SOFiSTiK

The existing template directories are shown under directories. The saved file name.sofistix is now available as a further template.

Version 2010

49

SOFiSTiK
Usage of Template Files name.sofistix File > New Project from Template... The existing templates from the template path are offered. Root directory: General Subdirectories: cadb and pretee

Basics

The desired file name.sofistix is selected and stored under a new data file name with the button Save As ... into a project directory. The new file contains all tasks of the template. In addition, the data (for example cross sections, geometry... etc.) from the template are transferred into the new file. The data is then immediately ready for calculation. With Templates without Design Code, the design code can be altered. The materials and cross sections must be checked and amended.

410

Version 2010

Basics
4.3. 4.3.1. Structure and Function Mode Calculation Status

SOFiSTiK

Every task has its own symbol to show the actual calculation status.

Without calculation green check mark blue arrow blue cross red cross green cross

Input is written directly into the database no calculation required new input data > calculation required old data > calculation required error message > calculation required warning message > calculation possible necessary

Version 2010

411

SOFiSTiK
4.4. Special Features for Start

Basics

For special cases the user may start the program from a command shell by using the following command lines: Parameter + or ++ nosingle test Description Opens the last file or the last but one. Is used without a switch or / . Starts the application as a separate instance (no single application). A general test flag is set. This is only of interest for the developers. Depending on the level of development, an individual message window is activated. When starting the SSD the automatical opening of the AnimatorView is suppressed. When starting the SSD a complete DATfile is created and the SSD window is closed again immediately.

noani dat:name

412

Version 2010

Basics
5
5.1.

SOFiSTiK
Input with TEDDY.
Overview

TEDDY is a powerful control centre as well as an editor, which fully supports and utilises the CADINP language.

help window

input window

navigation window for input

TEDDY provides you with an integrated help system listing all the possible commands at the status line. By pressing F1 you will get the corresponding manual

Version 2010

51

SOFiSTiK

Basics

to a specific command (PDF file) on your screen, without interfering with your editor. The ESCkey will close the help window.

5.2.

Support of international character codes (UTF8)

Starting with Version 2010, the so called UTF8 characters are processed by TEDDY. In HEAD and TEXTlines now country specific titles, texts and notes can be entered, which are correctly returned in the result file. The readability of the printout is thus significantly improved. In particular, for instance, Greek and Cyrillic characters can be integrated.

The actual character encoding is indicated in the status bar. With a mouse click on the coding field a setting dialog opens.

52

Version 2010

Basics
5.3. Starting the Editor

SOFiSTiK

TEDDY is a windows application and can be started by the standard methods. a double click on the program icon or a DATfile will start the program TEDDY For special cases the user may start the program from a command shell by using the following command lines: ted [/options] [filename] [line column] filename: As a filename you may also enter a + or ++ this will load the last or second last file respectively. By using abc*.dat the open file dialogue will be started with the given pattern match. The following command *.* will select the whole directory. options: /sSofistikPfad /1 to /4 Path for the SOFiSTiKexecutables (Change or set the environment variable SOFiSTiK=...) will create additional instances of TEDDY The number will select the colour of the TEDDYicon.

Version 2010

53

SOFiSTiK
Overview of the possible input commands: Parameter + or ++ 0 1 2 3 4 nosingle test Description

Basics

Line No.

Opens the last file or the last but one. Is used without a switch or / . Allows the start of up to 5 instances (Default: 0). Starts the application as a separate instance (no single application). A general test flag is set. This is only of interest for the developers. Depending on the level of development, an individual message window is activated. The cursor is placed directly into the given line. The line number must be the last transferred parameter.

5.4.

Commands

The most important functions are accessible via the function keys: F1 F2 F3 F4 F5 F6 F7 F8 F9 F12 help to the current input record (quit with ESCkey) search search again search and replace mark Block start or end copy marked block move marked block duplicate current line change window start analysis

Moreover there are a lot of special keys. These are combinations of the Altkey or Ctrlkey and another key pressed simultaneously. These combinations are a very useful feature for an experienced typist used to the touch typing method. Some of the combinations are given below:

54

Version 2010

Basics
5.4.1.
Alt + L Alt + B Alt + H Alt + R Alt + W Alt + Z

SOFiSTiK
Combinations with the Altkey (selection)
marks several lines (block of lines) marks several columns (column block) remove block markers read file as block write (marked) block to a file copy marked block

5.4.2.
Ctrl + A Ctrl + C Ctrl + V Ctrl + X Ctrl + S Ctrl + Y Ctrl + Z

Combinations with the Ctrlkey (selection)

marks all copy marked block paste marked block cut marked block save file delete Line undo

5.4.3.

Overview of all Ctrl / AltCommands

A complete arrangement of all Ctrl commands, you will find in the TEDDYhelp menu Help > Ctrl commands .... If you press the Ctrlkey and the Kkey (Ctrl+K) for more than two seconds you will get also an overview of all the special key combinations:

Version 2010

55

SOFiSTiK

Basics

Here one will also find combinations of three keys (Ctrl+K + R) and their counterparts with the Altkey (Alt+R).

5.4.4.

Example with Column Block

An empty column block will be created: (Alt + B) key for block start drag the block (Alt + B) key for block start The block is now marked with a certain colour. (Alt + Z) key The column number dialogue is now active. Now you can do a lot of things with the values in the column, like generating sequences or calculating the sum of the values, just to mention a few.

56

Version 2010

Basics

SOFiSTiK

5.5.

Input of Data.

Every SOFiSTiKprogram expects input data. The data is supplied in text files. The data is stored in a certain sequence, so that each program knows where to get its data. An input segment thus starts with the reserved identifier PROG and the name of the program for which the data is to be used. A file may contain input to as many modules as desired or needed, e.g. PROG AQUA Data for the AQUA program PROG SOFIMSHA Data for the SOFIMSHA program PROG SEPP Data for the SEPP program

Version 2010

57

SOFiSTiK

Basics

TEDDY is able to recognize a file as an input file by the structure of the very first line. It can for example look as follows: PROG progname +PROG progname PROG progname $PROG progname Further TEDDY assumes every file having the extension .DAT to be a SOFiSTiK input file. You may specify other extensions via the option Extras > File type. Provided that the file progname.ERR exists, TEDDY can recognize all record names and their corresponding commands. The statusline of the window displays the current record name and its commands as well as the name of the module used and the current input language.

record name

list of items

module language

5.6. 5.6.1.

Help and Interactive Manuals. Activating the Help

Help is activated with the F1key. The page of the manual, matching the current input command of the current program will be shown. The names of the manuals, which are in PDF format, are composed with the progname and a special character sequence (_0 German or _1 English) indicating the language. They have to be available of course. In a navigation window you will see the table of contents, which allows you to jump to the theoretical or the example sections in the manuals. But as soon as TEDDY

58

Version 2010

Basics

SOFiSTiK

becomes the active window again, the help will automatically switch to the current manual page. You may quit help with the Esckey, but only if TEDDY is the active window. As an alternate method you can use the close (X) button of the Acrobat Reader. It is possible to print out the complete manual or just a couple of pages. The layout of the manual is optimised for a double sided print out.

5.6.2.

Acrobat Reader

For viewing the manuals you will need the Acrobat Reader (Version 5.0 or higher) This software is share ware. If the Acrobat software is already installed on your computer no alterations are made by the SOFiSTiK setup. You can also change the size and position of the help window. The best option is not only a matter of taste but also of the screen resolution. The following options are available: Help F1 Freeze Keywords Arrange Help Vertical Arrange Help Horizontal Full View for Help Close Help Esc Hint: If you close the Acrobat with an <ESC> from within the TEDDY window it will stay in memory and pop up very fast the next time.

Version 2010

59

SOFiSTiK
5.6.3. Creating Your own Comments

Basics

If you want to make annotations within the help files you will need a full version of the Adobe Acrobat, which is also recommendable for many more reasons.

The tool bars should be activated. You will now have several tools available. Choose on of them via mouse click and create your comments. (See the Adobe OnlineHelp for more details) When leaving the PDFfile you should save your changes. The annotations are saved into the PDF file and may be also seen from the Acrobat Reader. However if you want to change the annotations you need the full version of Acrobat again. There you have a navigation window with all annotations selectable, editable and erasable.

510

Version 2010

Basics
5.6.4. Export/Import of Annotations in Manuals

SOFiSTiK

Before loading a new version of the manual especially when obtaining automatic updates you should save your annotations and reimport them within the new PDFfile. Thats why the automatic lifeupdatetool SONAR has several options to deal with the manuals. The intended option is to keep all new manuals in a separate download directory. Then you should copy the plugin from the SOFiSTiKCD \statik\win32\extra\ImExAnot.api into the Plugin directory of your AcrobatInstallation. You open then all PDF files with annotations and have the choice between: File > Export > All SOFiSTiK Annotations File > Export > Own SOFiSTiK Annotations The original possibility of the AdobeExport is not so well suited, as it is bound to the page numbers, while our plugin uses the names of the pages (e.g. Recordnames). Thus on a new version with additional inserted pages you will find your annotations at the originally intended place in most cases. The annotations will be saved into a file of type FDF (name.FDF). When you have the new PDF version opened, you may import them via: When leaving the PDFfile you should save the changes of course. If you use SONAR to download the newest versions from the Internet, you may have the problem to exportimport comments for many manuals. Thats why there is the option file > batch processing > SOFiSTiK Comments to do this for all PDF between two directories. One possibility to manage this properly, is to download the manuals always into a special download directory, assuring that (only) newer versions will be treated always. In a second step (if the filedate of a manual is larger than the last export/ import) one has to copy these manuals to a third temporary directory, where they are updated from the old PDFs, before replacing them.

5.7.

TEDDY the SOFiSTiK Commander.

Besides the editing features of TEDDY, it is used as a control centre of the total analysis. From TEDDY you can start the calculations and call up the pre and postprocessing modules. To execute these features a tool bar is supplied in TEDDY, which consists of the following icons:

Version 2010

511

SOFiSTiK
Overview of modules in data file Program start WPS (F12) Quick start PS (without prompt) Quick start PS only current module of the input +/PROG (Change of module selection) (+) PROG with filter +PROG (activate all modules) PROG (deactivate all modules) +/PROG from to Cursor SOFiSTiK data files Input file *.DAT Result file *.ERG List file *.LST Protocol file *.PRT MONET Animator (Structure and results animated) GRAFIX (graphical results) WinGRAF (graphical results) DBVIEW (selected printed results) Result viewer URSULA Tasks (see also SSD)

Basics

512

Version 2010

Basics
Data export from CDB Archive Clean up Explorer CommandShell

SOFiSTiK

Version 2010

513

SOFiSTiK
5.8. Special Features of SOFiSTiK

Basics

In the rightclick menu of TEDDY some important commands are put together to support the work with SOFiSTiK. The settings in this rightclick menu can be customised by the user with the menu Extras > edit macros > SOFiSTiK.wtm.

Within the menu SOFiSTiK you will find some specific features aimed at SOFiSTiK programs.

514

Version 2010

Basics

SOFiSTiK

5.8.1.

TEDDY Information Centre

Help > Licenseinfo

Information about installed programs

Version 2010

515

SOFiSTiK
Manuals

Basics
Help > SOFiSTiK Documentation

For every SOFiSTiK program there is a LOG file in HTML format. Here all the changes and enhancements are listed for the respective versions of the programs. . Help > SOFiSTiK LOG Files

With the program Diagnose all SOFiSTiKspecific settings and resource files are collected. It is very helpful for installation problems or problems caused by the op-

516

Version 2010

Basics
erating system. (But available only in German)

SOFiSTiK
Help > Diagnostic

Version 2010

517

SOFiSTiK
This page intentionally left blank

Basics

518

Version 2010

Basics
6 CADINP Input Language.

SOFiSTiK

The input language CADINP for free input format of data is the result of a further development of a project CADINT, which originated from the Federal Ministry of Research and Technology for the study in the CAD area (M.Ahn, K.H.Bckeler, W.Haas / Eingabe Konventionen fr CADProgramme, CADBericht KfkCAD 39, Kernforschungszentrum Karlsruhe, 1976). The variation of this format, which was developed by SOFiSTiK, includes several additional capabilities. In certain points it therefore has some deviations from the above mentioned CADINT standard. The full capability of the language can be achieved in combination with SPS and/or WPS, when functions for block building and parameter substitution are used. CADINP and SPS represent a full programming language for the calculation of problems in structural engineering, which will outdo any guided GUI. The processing occurs in two stages. SPS or WPS use a single file or a set of subfiles to create an input file for every program being used. This is called parsing. During this process globally defined text elements are inserted and larger blocks are inserted or skipped. Strings are addressed with $(name). The strings can be defined or undefined in the input file or the SOFiSTiKenvironment. At this stage no calculations have take place, that is why there is a difference, whether the string A = 2+2 is inserted at $(A)*3 or ($(A))*3. Each computational program starts its own CADINP processor, which then starts the arithmetic calculations. The variables used within CADINP are marked with a # at the beginning. They do not need any brackets and represent numbers. They can be converted to text input data where needed, especially within comments. However they can only be used within the local scope of the single program. The combination of these two stages allows the description of a complete analysis systems by means of manual calculations and documentation of the analysis assumptions and the resulting computer calculations. This in turn produces a complete analysis document in the computer.

Version 2010

61

SOFiSTiK
6.1. 6.1.1. Definitions and Descriptions Lines (physical sentences)

Basics

The input consists of lines. Each line contains up to 255 characters and corresponds to one line on the screen.

6.1.2.

Records (logical structure)

Similar or logical connected data are put together in records. Each record has a name. The records do not have to conform with the line separation.

6.1.3.

Separation Characters

The individual values within a record are separated by the separation character. One or more blank characters (space bar) serve as separation characters.

6.1.4.

Data

Data can be numbers or text (=Literals). Numbers may have a sign and an exponent. If an integer number is expected, the given number will be rounded to the nearest integer, e.g. 2 0.04 .5 3.7E8 0.5E3

Texts are arbitrary strings of characters. Only the first four characters are significant. Text should be delimited by apostrophes if there is danger of confusion with numbers, record names or items, or if it includes blank spaces or the characters , or ; or $, e.g. ALFA NODE 1S45 A B 1.45 A;B Ab"

With Version 2010 all international characters (UTF8) may be used, previous versions allowed only the local codepage characters. However the short ident keys with exactly 4 characters allow only for pure ANSIcharacters (i.e. no Umlauts or accents). Lower case characters are automatically converted to uppercase characters, as long as they are not between apostrophes. However a few exceptions are enforced to upper case (e.g. names of actions) to avoid ambiguites, these will be marked as LITnn instead of Litnn in the column unit. If a literal contains a variable (see 6.2.13.) there are three cases to be distinguished:

62

Version 2010

Basics

SOFiSTiK

The literal has been defined with apostrophes and starts with an equal sign (=). In that case the literal is passed unchanged but without the leading = to the program allowing to define formulas. This if course only useful if the program can handle the literal in that form as intended. If the variable has been defined with a literal, this content will be inserted instead of the variable. If the variable has been defined with a value, this value will be formatted and inserted instead of the variable in the literal. For an optional literal i.e. instead of a number and for variables containing literals only the form #name without any arithmetics or indices is allowed (e.g. A#1 with #1=25 yields A25). Within a real pure Literal however you may use the #() function with the format as a second parameter i.e. #(#ALPHA,8.3). The integer part of the format selects the number of total characters (8), while the decimal part selects the numbers of decimal digits (3). The first argument may be any complex arithmetic expression.

6.2. 6.2.1.

Input Syntax Basic Input Format

The input consists of records. The input record consists of the record name followed by data in the order specified in the input description. Each record occupies one input line. The record name can be omitted when the record is of the same type as the preceding one. A record can start at any position in a line. The data is separated from each other by one or several separation characters.

Version 2010

63

SOFiSTiK
6.2.2. Default Value

Basics

If the minus sign () is given instead of a data value, the program uses the corresponding default value as specified in the programs description. If less data is entered for some record than its description demands, the corresponding default values will be used in the place of the missing data. The minus sign must be embedded between separation characters. Default values can be redefined inside a header record that defines a table.

6.2.3.

Repetition

If the equal sign (=) is entered in the place of a data value, the program will use the corresponding value of the preceding record. However this is only possible if the record name has not been changed. If two equal signs (==) (with no blank spaces in between!) are entered, all of the values in the following records will be the same. Positioning of the preceding record is not considered. If the value of the previous record is a generation instruction or a list of values, the generation or the complete list will be repeated. The repetition characters must be enclosed in separation characters.

6.2.4.

Increments/Decrements

If a double plus or minus (++ or ) is entered in the place of a data value, the program will use the corresponding value of the preceding record incremented or decremented by 1. This will also work with Literals, Lists and Generation sequences. However this is only possible if the record name has not been changed. The increment/decrement characters must be enclosed in separation characters.

64

Version 2010

Basics
6.2.5. Comments

SOFiSTiK

The comment characters $ , ! or // turns the rest of a line into a comment, which will be ignored by the program. All this comment operators should be separated from the comment itself and the input data in the same line with a separation character. Within a +PROGline (see SPS) only the $character is allowed as a comment and it must be separated by blancs. Within a +SYScommand line no comments are allowed at all.

6.2.6.

Record Continuation

A double dollar sign $$ means that the input record is continued in the next line. The characters following $$ are considered as a comment. A separation character must be entered right before $$. Thus it is not possible to write expressions or a list of values extending more than one line.

6.2.7.

Record Partition

More than one record can be in the same line. The records must be separated by a semicolon (;). The semicolon needs not to be between separation characters. This feature is not valid for the input of text lines (e.g. HEAD).

6.2.8.

Positioning

By entering a name of an item inside a record, you can provide the value for that item regardless of its position. Example: A record is defined by the items K1 K2 K3 K4 K5. The following input is then equivalent: RECORD RECORD RECORD RECORD 1.00 2.00 3.00 1.00 K4 2.00 3.00 K1 1.00 K4 2.00 K5 3.00 K4 2.00 K1 1.00 K5 3.00

Version 2010

65

SOFiSTiK
6.2.9. Defining Tables

Basics

The predefined order of the input data can be altered by entering a record consisting only of the names of the items. In this case the following records must not contain a record name, as this would reinitialize the sequence of items. The last example could have also been given as: RECORD K1 1.00 K4 2.00 K5 3.00

A table definition remains valid until a new record name is entered or the same record name is repeated. Inside a table the positioning is still possible even for those items not defined in the table definition. The default values can be modified inside the header of a table by following the item with an equal sign (=) and the new default value without any separation characters. RECORD K1 1 2 3 K2 2 5 6 K5=4 6

is equivalent to RECORD K1 1 2 3 K2 2 5 6 K5 6 4 4

Such a construct is also a nice suitable solution to the problem of ambiguous literals. If a literal value exists (e.g. GRP) for the first item position which is also a valid record name, a change of the sequence and perhaps a default assignment may solve this problem without the need to use quotes: BEAM TO 1 2 TYPE TEMP TEMP PA 30 25 FROM=GRP

66

Version 2010

Basics
6.2.10. HelpRecord

SOFiSTiK

A list of the possible record names can be obtained by entering HELP. HELP followed by a record name prints a list of the items of the record. HELP followed by a record name and an item name will print the allowable input values and parameters for the corresponding position. This option is meaningful especially during interactive error finding.

6.2.11. Generation
An instruction for automatic record generation can be given instead of a data value. In this way a series of records can be created automatically. When generating a record the command must be enclosed within parentheses. Its elements must be separated by separation or underline characters. There are two types of generation instructions: primary automatic generation instruction (Start_value End_value Increment) secondary generation instruction (Start_value Increment) The primary generation instruction specifies the number of the individual records to be generated. It can be used only once per record, yet in any position inside the record. The corresponding secondary generation instruction can be defined for every parameter. The generation of literals is also possible. The increment is then also considered as a literal but may contain only numbers. The increment can also be negative. If the specified end value of a primary generation instruction is not reached with an accuracy of 0.0001 of the increment, an error message will be displayed. The other generation instructions of the CADINTlanguage are not implemented because they contradict with the arithmetic expressions.

Version 2010

67

SOFiSTiK
Example: NODE (1 5 1) 0 (0.5 0.1) generates the input records: NODE NODE NODE NODE NODE Example: REIN (A0.1 D0.4 10.1) generates the input records: REIN REIN REIN REIN A0.1 B0.2 C0.3 D0.4 1 2 3 4 5 0 0 0 0 0 0.5 0.4 0.3 0.2 0.1

Basics

6.2.12. List of Values

A list of values can be given instead of a generation loop . This is a series of values separated by commas or underline characters. Value,Value,Value,Value e.g. 1,2,7,9

A list of values may not contain any separation characters and can not be spread across multiple lines. When several lists of values are defined within a single record, their number of values must agree not only with each other, but also with any other defined primary generation. The maximum number of values per list is limited by an internal amount of memory. A list of 25 values is usually possible. A list of values can also be built up by fixed literals (LIT). Combinations of numbers and literals or a list of freely defined literals are however not allowed.

68

Version 2010

Basics
6.2.13. LET and STO Variables

SOFiSTiK

One can define variables to be used in the following records. A # must be set between the input of LET or STO and the variable name. These variables are designated as up to 16 characters of an alphanumerical text (1st character has to be a letter) and an optional index or only by a #sign followed by a simple numerical positive value. The variables can be used then instead of numbers. The assignment of a variable is performed by the record LET# or STO#. This item is followed either directly by the name of the variable without any separation characters, or after a separation character by an expression for the variable number. After one more separation character follows the value to be assigned to the variable. LET# or STO# do not alter the currently defined record name and must be given in each assignment. Names of variables must not contain special characters or collide with a reserved sequence of characters like (SIN, COS or SQR). Instead of one numerical value a list of values or a primary generation instruction or a literal may be entered. In this case the rest of the values is assigned to the variables following the input variable. This defines an array if a named variable is used. A variable is used if the item or an expression comntaining the variable is provided with a leading = character. For special cases like the insertion within a literal, assignment of a default value, conflicts with identical function names, it is possible to identify a string as a variable name with a leading # sign.

Version 2010

69

SOFiSTiK
Examples of variable assignments: LET#PI 3.1415 LET#TXT My Text LET#11 4,5,6 LET#A 4,5,6 LET#A(2) 5.1 LET#A(3) 7,8 LET#1 =A(1) LET#1 #(A+1) LET# #10 12.50 $ $ $ $ $ $ $ $

Basics

Pi is assigned to variable #PI Assigning a literal assigned to variables 11,12,13 4,5,6 are assigned to A[0:2] Assignment to an array element Enlargement by 2 elements Using second element of array Using second element of array

$ 12.50 is assigned to variable, $ whose number is stored in #10 $ (Indexing) $ Value of the variable, whose $ number is stored in variable #10, $ is assigned to variable 4

LET#4 ##10

LET#F(100) 0 $ Declaration of an array, LET#F 1,2,3,4,5,6,7 $$ filling via lists 11,12,13,14,15,16,17 $$ and consecutive lines 21,22,23,24,25,26,27 If a variable is assigned to an expression, the expression is calculated first and then its value is assigned to the variable. To print variables for debugging purpose you may use the construct PRT# with a similar syntax for addressing the variable name. The name of the variable is expected without separation characters immediately behind the #. For more comfort one should use TXB / TXE or <TEXT> within literal text. Variables with a name may be saved permanently in the database. The command STO#name will save the current or specified value of this variable in the database, which then can be used by all other programs accessing the database from that. e.g.
STO#c 30 $ $ assignment and storage of the variable in the database

610

Version 2010

Basics

SOFiSTiK

If a save variable should be removed from the database there is the command DEL#name. For this case it is also allowed to specify wild card characters. The commands DEL#OPT* or DEL#A?00 will delete all variables with that pattern. For special cases it is possible to reinitialize a variable with the last saved value with the following commands: RCL#ALL Read all named variables RCL#name Read one named variable/array RCL#name(3) Read one entry of an array RCL#name cdbfile Read variable from another CDB data base Reserved VariableNames There are some reserved Names, which are automatically created by a programm run. The user may use and redefine those names however within his CADINPdata block with new values. Variables VERSION(0) and VERSION(1) will be preset with the version number of the Release (dll) and the program itself, allowing to define common input data for multiple versions. Variable PI will be preset to 3.141593. The arrays of variables GRP_MASS, SCT_MASS and MAT_MASS as well as GRP_REIN and SCT_REIN are redefined after a print or evaluation of system statistics. They contain the masses (MASS) and reinforcements (REIN) of all groups (GRP_) and section numbers (SCT_) or Materials (MAT_), where the index 0 contains the total sum. All other variables start with the first three characters of the program creating them followed by an underline: ASE uses the array ASE_ITER as follows ASE_ITER(0) = first load case number ASE_ITER(1) = last load case number ASE_ITER(2) = last achieved load factor Variables of Array AQB_USAGE will be set by AQB with the usage factors of the design tasks of the last input block. All Variables starting with OPT_ are reserved for OPTIMA. To trace the assignment of values, there is a command DBG#. This will toggle test prints and an interactive debug mode. DBG# uses the variable #0, which can not

Version 2010

611

SOFiSTiK
be used for other purpose therefore DBG#0 DBG#1 DBG#2 DBG#3 DBG#4 DBG#8 DBG# and DBG# 2

Basics

No output of intermediate values Output of the generated input records Additional output of all value assignments Additional output of selected structures (CDB access) Printout to console stream/window Input from console stream/window (interactive mode) Switch between option 15 and option 0 (=break and continue) Immediate STOP of total program run, although all outstanding TXELines will be printed after the error message

6.2.14. Arithmetic Expressions.

In place of a numerical value any desired arithmetic expression may be used. The expression may contain parentheses, but no separation characters. The allowable operators are: + * / ** or ^ == >= > & <> <= < | Addition, Subtraction Multiplication, Division Exponentiation Condition of equality/inequality Relational condition Relational condition result: true (1.) or false (0.) Bitwise logical operation on the integer part with AND or OR

If no operator is given, a multiplication will be performed. The bindings of the operators are according to the mathematical rules.

612

Version 2010

Basics
The following functions are allowed inside an expression:

SOFiSTiK

SIN(x),COS(x),TAN(x) Trigonometric functions ATN(x),ATN(y,x) Arc of tangent x or y/x ARC(x) Convert angles to arcus SQR(x) Square root ABS(x) Absolute value EXP(x) Exponents of e LOG(x) Natural logarithm LGT(x) Base 10 logarithm DIV(x,y),xDIVy,DIV(x/y) Integer part of x/y MOD(x,y),xMODy,MOD(x/y) Division remainder of x/y MIN(x,y,..),MAX(x,y,..) Minimum or Maximum numbers RANDOM(x) random value between 0 and 1 (x=0 reinitialises the seed) IIF(expr,val1,val2) returns val1 if expr is not equal zero and val2 if expr equals to zero. Arithmetic expressions may also appear within a list of values or generation instructions. The functions DEG, GON and RAD may be placed before any argument, but separated from it by a comma. Their definition is kept if an assignement contains only one of those names (e.g. LET#0 RAD). Examples: SIN(30.)+3*COS(45.) SIN(RAD,2.435) 100.+MOD(354,32) 120.+12. 3(5.0+4.0) COS(#1) SIN#1 345*#11+##12 Interpolation and Tables: A special feature is available when accessing arrays of variables. If the index is not integer, but rational, an interpolation between the values of the array will take place: oder SIN30+3COS45 oder 100+354MOD32

Version 2010

613

SOFiSTiK
LET#A(0) LET#A(1) LET#A(2) LET#A(3) LET#B 10.0 14.0 16.0 17.0 => #B = 14.6

Basics

=A(1.3)

The same procedure is also available for higher interpolation schemes. Then we need two arrays of the X and Y values with the same length. These variables are then connected by a special assignement of a literal as a table definition: LET#X LET#Y LET#SIG 0.0,2.0,3.5 0.0,100.0,100.0 TAB(X,Y)

The expression SIG(1.73) interpolates for this Xvalue betwen the given Yvalues linearly. If higher functions are requested, a third array is needed, giving the derivatives of the function: LET#DY LET#SIG ,0, TAB(X,Y,DY)

For the example above only the derivative at the middle point has been specified. Thus we have quadratic parabulas for the interpolation function. If derivatives are specified at both ends of an interval we have cubic splines as interpolation functions. Variables and Literals: In case it is required to store text in a variable this may be done with the LET/STO command in the same way: LET#TEXT ABCDEFGHIJK

The text will be saved in blocks with 4 characters each in the name of the variable, #TEXT(1) would thus be equivalent to EFGH in the above example and it is possible to change that item only, but there is no storage of single characters. However when using a text variable it is possible to use sub strings with the format #TEXT(3:7) selecting the third to seventh character. (Instead of the numbers any arithmetic expresssionas are also valid of course). A text variable may be read from the CDB and it is possible to convert with a LET/STO command a text to numbers. The following example will save the two numbers in variables #VALT(0) and #VALT(1):

614

Version 2010

Basics
LET#TEXT LET#VALT 1.23,1.48 VAL(#TEXT)

SOFiSTiK

6.2.15. FUN Definition of functions

If an arithmetic expression is needed more often or the meaning of a variable should be changed during the run, it is possible to define a function. Such definition is done as a literal according to: LET#F e.g. LET#F LET#1 =FUN(x,3*#x**32*#x**2+5*#x) #F(1.234) =FUN(var,formulaexpression)

The Literal has to start with the character sequence =FUN( , followed by a formal parameter name, followed by an expression containing any variables defined so far. If the formal parameters name has been defined already, it will not be changed by the call. Recursive calls are allowed.

6.2.16. Conversion of Units.

For every numerical value, list of values or generation it is possible in general to append the input unit explicitly in square brackets. So instead of definig a length in the default unit m as 0.3048 it is also possible to specify 304.8[mm] or 12[in]. CADINP will check however if that unit is allowed, thus this option is only available for those items selected for this option. These are identified in the manual with a [*] in the column named dimension.

Version 2010

615

SOFiSTiK
6.2.17. LOOP,ENDLOOP Loops and Jumps

Basics

The most powerful form of generation is achieved through loops. This form corresponds to the FORTRAN DOLoops or to the FOR NEXT loops of BASIC. The loop is initiated by the record LOOP and terminated by the record ENDLOOP. A loop is executed as many times as determined by the number following LOOP. It may also be terminated if the expression following ENDLOOP becomes zero or negative. If the name of a variable is given instead of the number after the LOOP, then the number of elements contained in that variable will be used. Loops can be nested up to 32 levels, containing any number of input elements. If LOOP is not followed by a number, it will be performed at most 9999 times. Each loop construction must not exceed 255 lines. Multiple records, however, can be entered at the same line (separated by ;). If you still need more than 256 lines you have to specify before the first LOOP LET#LOOPSIZE number_of_lines It is possible to store the index of the loop in a variable, if the name is appended to the LOOP keyword. The index starts counting at zero. The variable may be changed within the loop, but it will be restored after evaluation of the terminating condition in each cycle. Example: Generation of nodes and springs on a semicircle at a distance of 30 degrees. LET#1 1 , LET#2 0. LOOP 7 NODE #1 COS(#2) SIN(#2) SPRI #1 #1 DX COS(#2) DY SIN(#2) CP 1.E5 LET#1 #1+1 LET#2 #2+30. ENDLOOP Instead of LOOP 7 / ENDLOOP you could use LOOP / ENDLOOP #2<=180. With an endloop condition one can leave a loop prematurely. Example for twolevel generation: LOOP#1 3 ADEF #1+1

616

Version 2010

Basics

SOFiSTiK
LOOP 2 ; BDIV 0.5 #1+1 ; 0.2 1 ; ENDLOOP ENDLOOP

creates: ADEF 1 ; BDIV 0.5 1 ; 0.2 1 ; 0.5 1 ; 0.2 1 ADEF 2 ; BDIV 0.5 2 ; 0.2 1 ; 0.5 2 ; 0.2 1 ADEF 3 ; BDIV 0.5 3 ; 0.2 1 ; 0.5 3 ; 0.2 1 If you want to run a loop over all elements of an array, this may be done by giving only the name of the array (without the # ): LET#A 10,22,34,55,76,83 LOOP#1 A $ Only the name, #A would be the value 10! KNOT #1+1 X #A(#1) ENDLOOP With a small extension it is also possible to store the number of elements in a variable, where the value of 0 is obtained if the variable does not exist: LOOP#NUM DEF(A) ; ENDLOOP

Version 2010

617

SOFiSTiK
6.2.18. IF Logical Conditions

Basics

Conditional blocks are an important element of every programming language. The execution of jumps (go to) is not possible within CADINP as it is proven to be able to solve any problem without this feature. The conditional block is executed if the expression following the IF is greater than zero. You might want to use the logical expressions for this. Texts may be only compared with == and != operators, the comparisson is case sensitive. Example: $ #1 is the control variable with possible values +1/1 IF #1 These lines are input when #1 > 0 ... ELSE These lines are input when #1 < 0 or = 0 ... ENDIF IF #1==12 These lines are input when #1 equals 12 ... ELSE These lines are input when #1 does not equal 12 ... ENDIF The generation of a CASE construction is available by using a series of additional ELSEIF statements: if (Condition_1) .... elseif (Condition_2) .... elseif (Condition_3) .... else .... endif

618

Version 2010

Basics
Example: IF (#A<0.3) LET#VALUE 0.50 ELSEIF(#A>1.0) LET#VALUE 0.70 ELSE LET#VALUE 0.50+0.20*(#A0.3) ENDIF

SOFiSTiK

$ condition 1 $ or condition 2 $ else this value

VALUE

0.7 0.5 A 0.3 1.0

That means that only one possibility is chosen for VALUE depending on A.

6.2.19. @CDB Selection of a CDBASE

CADINP allows the access to data of any SOFiSTiKDatabase. Of course you need a description of the contents of the database (cdbase.chm). The syntax has three parts. The @CDB selects the file name of the data base: @CDB filename selects an arbitrary database filename.CDB. Default is the actual project database. An explicit definition of this database is however not allowed. All data within the CDB consists of multiple records with identical structures organised within different 64Bit indices KWH/KWL. In general each data record has a part containing integer numbers and a second one containing the floating point data. The description of all structures is given for the user within the file CBBASE.CHM and for the programs within the file CDBASE.CDB.

Version 2010

619

SOFiSTiK
6.2.20. @KEY Access to the CDBASE
@KEY KWH KWL [SEL1 SEL2 SEL3

Basics

SEL4 SEL5 SEL6 IERR]

selects an access index KWH/KWL according to the CDBASE description. KWH is a 8 character identifier while KWL is an optional number (e.g. load case or section number). Values KWL and SEL1 to SEL6 are preset automatically. For special purpose an optional filtering rule given by up to 6 integer or 4 character key values SEL1 to SEL6 may be specified. Key values which are not important or will be defined with the accessfunction have to be specified as 1. The keys correspond to the integer positions of the database. The record index has to exist in the database. You will get an error otherwise. The read position is set to the beginning of the index. If you specify for IERR a number of a variable (for example 999), its value will be set to a positive value if the given key exists. If the variable #CDB_IER has been defined, it will contain the same value.

6.2.21. @() Access to the CDBASE

A record is accessed by the use of an arithmetic function @() as special case of an arithmetic expression: @(position+offset) or @(no,position+offset)

reads from the database the next record, which passes the @KEYfilter which is modified for the second case by no at the position of the last defined KEYi. The value of the expression is the stored data with the name position or if position is a number the value at the position relative to the last selection value of the filter. The value 0 and negative values will therefore yield the integer values within the selection keys. An access to the index of an array can be done via offset. The access function will start at the current position. If you access a value with the same or a lower position, CDBASE will read the next record. If the endoffile condition is encountered an error will occur if you have used the form @(position), while for @(nr,position) a loop is used once and the function jumps to the beginning.

620

Version 2010

Basics

SOFiSTiK

You may also specify two state variables. If these variables have been defined non negative, the result values will be saved there and error messages will not appear: CDB_LEN for the actual length of the record CDB_IER for the errorflag (0=ok, 1=record to short, 2=end_of_file, 3=key_not_defined). This is required to prevent the program to enter an infinite loop. Example 1: To get the effective Iyvalue of cross section 5 from the actual projectdatabase, you enter: @KEY SECT_EFF 5 LET#5 @(IY) Example 2: To use the support forces of node 101 and 102 of load case 12 as loads you enter: @CDB @KEY LOAD LOAD Example 3: To use shell forces of the nodes 101 and 102 of group 2 of load case 12 you enter: @CDB project1 @KEY QUAD_NFO 12 2 LET#101 @(101,mxx) LET#102 @(102,myy) Example 4: To get all support forces of nodes with last digit 0 as loads you may enter: $ Selector Group 2 $ moment mxx $ moment myy project1 N_DISP 12 1 PX @(101,PX) PY @(101,PY) 2 PX @(102,PX) PY @(102,PY)

Version 2010

621

SOFiSTiK

Basics

@CDB project1 @KEY N_DISP 12 LET#CDB_IER 0 LOOP $ ALL RECORDS LET#10 @NR,@PX,@PY,@PZ IF (#CDB_IER<2)&(#10<>0) $ END OR HEADDER IF 0==MOD(#10,10) $ LAST DIGIT 0 LOAD #10 PX #11 #12 #13 ENDIF ENDIF ENDLOOP #CDB_IER<2 $ TO TERMINATE THE LOOP Example 5: To get the section number of the beam 101 (As we have to read two different cases alternate, we can not use the predefined literals): LET#CDB_IER 0 @CDB projekt1 @KEY 100 0 1 1 1 1 LET#NR 0 LOOP LET#10 @(3),@(2) IF #10 ; LET#NR #10 ELSE IF #NR==101 LET#Q #11 ENDIF ENDIF ENDLOOP #CDB_IER<2

$ 4 IntegerKeys $ $ $ $ ALL records 1. and 2. Integer New BEAM section of beam

$ TO TERMINATE THE LOOP

622

Version 2010

Basics
Example 6:

SOFiSTiK

For text elements saved in the database special caution has to be payed for the fact that we have to distinguish between pure ASCIItext [chr] and unicodetext [str]. In the following the first part reads the CHRName of the design code with elementary functions, while the second part reading the unicode designation of the material has to use the names of the cdbase.chm:

@KEY 10 1 $ READ DESIGN CODE AND ACTIONS let#NT LIT(@7,@8,@9,@10) $ DESIGNATION OF CODE let#A1 LIT(@2) $ NAME OF ACTIONS let#A2 LIT(@2) let#A3 LIT(@2) @KEY MAT 1 LET#MATTXT LIT(@TITLE)

Version 2010

623

SOFiSTiK
6.3. General Records.

Basics

The input consists of blocks. Each input block usually begins with the HEAD lines and ends with an END record. Some programs allow the input of more than one block. The analysis is ended in those cases when an empty block (END/END) is found. The same layout is used in all manuals for the input description of all records. Apart from the record name, which is written in a special box at the upper right, there are four columns in each table. The first column contains the names of the items of the record. Explanations and allowable literals are given in the second column. The dimension of the input parameter can be found in the third column. The character stands for a dimensionless parameter, a * stands for values with different possibilities, that are selected via PAGE UNII. LIT is given for items allowing only preddefined literals. Litnn defines input, which can accept free text of up to nn characters. LITnn defines literals which are enforced to upper case. The last column shows the default values. Here, the character means that no default value exists, and that the parameter itself is not necessary. On the contrary, a ! means that a value must definitely be specified. Finally, a * means that the default values depend on various conditions which are explained in the text. Some records have the same meaning in all of the programs. These are:

624

Version 2010

Basics

SOFiSTiK

6.3.1.
Item

HEAD Title Lines

Description

Title line

LIT72

Up to 10 title lines can be defined. The first one is reserved for the structure description and can only be defined in the programs AQUA, SOFiMSHA/B/C and in templates of the SOFiSTiK series. This line is imported by all other modules from the database, thus it can not be changed. The rest of the lines can freely be defined by entering the record HEAD followed by a separation character and any desired text up to 72 characters. If no title lines are defined inside a data block, the previous ones remain in use. See PAGE about specifying a page headline. Title lines must not be delimited by apostrophes. Defaults of the Heading lines may be specified in SOFiSTiK.DEF via the variables KOPF1, KOPF2 and KOPF3.

6.3.2.
Item

END End of an Input Block

Description

End of input or of an input block

The record END closes each input block. Inside a data block for instance, each single load case of the analysis can be defined. The end of the entire input is defined by a double END record. If this record is missing and the input file is at its physical end, this record is automatically generated by CADINP.

Version 2010

HEAD
Unit Default

END
Unit Default

625

SOFiSTiK

Basics

6.3.3.
Item

TXB Introducing Text

Description

Introductory text

6.3.4.
Item

TXE Concluding Text

Description

Closing text

Any desired explanatory text can be added to an input block by TXB and TXE, either before the analysis (TXB) or after it (TXE). The number of lines is unlimited. For each of those two kinds of text, one may specify larger text blocks between <TEXT> ... </TEXT> and pictures between the items <PICT> and </PICT>. However a picture is not allowed within a <TEXT> ... </TEXT> block. The TXB/TXE lines should not be entered between apostrophes. Within the text variables in the form of #(variable,dd) will be replaced by their current value using the format dd. HTML components may be used within the text. A component starts with a < not followed by a blank or another < . Known components will be interpreted, unknown will be discarded. SOFiSTiK programs know about (others will be discarded): <FF> <LF> <b> .... </b> <i> .... </i> <u> .... </u> New Page Blank Line Bold Italic Underlining

626

TXB
Unit Default

LIT72

TXE
Unit Default

LIT72

Version 2010

Basics
6.3.5.
Item

SOFiSTiK
<TEXT> Text block
Description

Header of a text block

LIT72

6.3.6.
Item

</TEXT> End of a text block

Description

End of a text block

LIT72

You may define a continuous block of text within the special record names <TEXT> and </TEXT> without the need of specifying record names. The text will be appended to the region selected by the last TXB or TXE command. The Text following the <TEXT> name will become part of the table of contents in URSULA. For the definition of templates one can specify editable fields via special HTML Tags: <EDIT:name>$(name)</EDIT> Editable Reference on Parameter value

<EDIT:name,Format=6.2>$(name)</EDIT> Editable Reference on Parameter value with a format of ###.## (total width.decimal digits) Format=6 reserves 6 characters wide Format=6 places left adjusted <EDIT:name,List=str1,str2,str3>$(name)</EDIT> Editable Reference on Parameter value with a list box of allowed values <EDIT:name,List=str1,str2,str3,Update=Y es>$(name)</EDIT> Enforces an update of the template immediately after input of data

Version 2010

<TEXT>
Unit Default

</TEXT>
Unit Default

627

SOFiSTiK

Basics

6.3.7.
Item

ECHO Output Control

Description

OPT

Echo option This parameter defines a set of output or computing options, to which the record ECHO applies. The actual list of the possible options can be found in the corresponding manual. FULL stands for all output options. 1 0 1 2 3 or or or or or OFF no computation NO no output YES normal output FULL extended output EXTR extreme output

VAL

At the beginning of the program all options for new results are preset to 1. The output parameter for already computed values (e.g. nodal coordinates in analysis programs) is set to 0. By entering ECHO NODE you can for example assign the value FULL to the option NODE. Therefore the default value for VAL will only be activated if an ECHO record for this option is given. The exact effect of all options can be found in the output description of the individual manuals. You should generally note that the shortest possible output is achieved by YES, while a rich output is obtained by FULL. By EXTR one achieves the output of values, which are either useful in further computational steps or can use up a lot of paper. Thus, use of this value should be made with care. If the user wants to prevent the output of certain results, he must deactivate them explicitly by NO. If for example one only wants the option REAC set, one must enter: ECHO FULL NO ECHO REAC

628

ECHO
Unit Default

LIT

FULL

LIT

FULL

Version 2010

Basics
6.3.8.
Item

SOFiSTiK
PAGE Control of Input/Output
Description

FIRS LINE MARG LANO

Number of the first page of the output Negative entries turn page numbering off Number of lines per page Column number for left margin Output language, if implemented 0 German 1 English 2 French 3 Spanish Input language, if implemented 0 German 1 English System of units for output System of units for input See explanations Format of page header 0 single line header 1 multiline header 2 ZTVK with graphic char. 3 ZTVK without graphic char. 4 short header Printout level in the output file 2 error messages only 1 warnings as well 0 additional information 1 computing times as well Identification of page (e.g. page II/

LANI

UNIO UNII FORM

PRIL

PAG

LIT12

The record PAGE is somehow obsolete, because its parameters are derived from the operating system or should be defined in the SOFISTIK.DEF file. All para-

Version 2010

PAGE
Unit Default

* * * *

* * *

629

SOFiSTiK

Basics

meters except the languages and units may be defined in URSULA at the time of printing. 0. single line header with long text
Dr.Eng. Charly Brown * 9012 Newtown * 12, Software drive, Tel.08144/2725 AQUA General Cross Sections (V 1.097) 25.05.95 Page 11 Title of structure (1st and all further HEAD lines)

1. multiline header (only if provided explicitly)

Dr.Eng. Charly Brown, Consulting Engineer 9012 Newtown * 12, Software drive, Tel.08144/2725 AQUA General Cross Sections ( 6087) Title of structure (1st and all further HEAD lines) Page : 11 25.05.95

2. ZTVK header and title box

+++ !Bauteil : Bauteilbeschreibung (3.KOPF Zeile) !Archiv Nr. ! !Block : Blockbeschreibung (4.KOPF Zeile) Seite: 11 ! ! ++ ! !Vorgang : Vorgangsbeschreibung (5. KOPF Zeile) ! ! +++ +++ !Subsructure: Substructure description (3rd HEAD line) !Archive No.! !Block : Block description (4th HEAD line) page: 11 ! ! ++ ! !Method : Method description (5th HEAD line) ! ! +++

3. Short Header
AQUA 5.095 Dr.Eng.Charly Brown Title of structure (1st head line) page 2 date 25.05.95

In the ZTVK Version only the first 48 characters of header lines are used. The persistent name of the company can be changed only by SOFiSTiK. However it is possible to change the name for a specific project within the SOFiSTiKEnvironment. The SOFiSTiK programs strive to present the output in the most suitable engineering units. The dimensions used in the database are expressed in SIunits kN,

630

Version 2010

Basics

SOFiSTiK

m, sec. However, other units can also be used for input and output (e.g. N, mm or cm2) as well as a different number of decimals. The control is implemented through the input parameters UNIA and UNIE. The conversion of all programs was extensive. It can not be guaranteed therefore that this value is used in all subdomains of the programs too. For reasons of consistency a change of the units in the input was implemented very cautiously. Values are composed as grp*8+sgrp (compare SOFISTIK.DIM): grp 0 1 2 0 1 2 3 4 5 6 = = = = = = = modified SISystem(kN,m,MPa) USSystem (kip, inch, ksi etc) metric system (N, mm etc.) Standard units or dynamic units General structural engineering (e.g. cm instead of m) Steel construction, (e.g. mm instead of m) Bridge construction, (e.g. MN instead of kN) Soil Mechanics (e.g. MN instead of kN) Hydrology Mechanical engineering (e.g. N instead of kN)

sgrp

In the file SOFISTIK.DIM all definitions are filed. Under column 7 you can set your own values. As the file is complemented by SOFiSTiK from time to time, it might be more reasonable to ask SOFiSTiK for modifications. The conversion to USunits follows a convention from 1 July 1959 which has unified American and British definitions: 1 inch = 0.0254 m (precisely!) 1 yard= 0.9144 m 1 lb = 0.45359237 kg (avoirdupois) 1 lbforce = 4.4482216 N If the unit ton is used, it is always equal to the short ton (2000 lb). With CADINP command HELP you can enquire the actual dimensions of the input.

Version 2010

631

SOFiSTiK

Basics

6.3.9.
Item

SIZE Graphic Format

Description

TYPE

Paper size Positive value Negative value Scale 0 *

landscape format portrait format *

SC

format filling engineering scale, best pos sible for filling the page

W H MARG

Paper width Paper height Draws a border NO draws an inner border + scale here W and H define the size of the area to be drawn at (for single sheet plotters and laser printers) YES draws a free border around the drawing W and H define the size of the paper (2cm margin, otherwise .5cm) FULL an additional border to cut the drawing at the outer paper limits is drawn (for drum plotters) Form of the border STAN standard frame ZTVK ZTVK88 frame

FORM

632

SIZE
Unit Default

URS

cm cm LIT

* * FULL

LIT

Version 2010

Basics

SOFiSTiK

This record appears within all programs having a graphical output. It defines the output format. In general, there are two variations of the task. The user selects the paper format either implicitly using TYPE or explicitly by the width W and the height H. The program can set the scale itself by picking the largest possible scale with the common values of 1:1, 1:2 and 1:5 or their multiples. An explicit setting of the scale SC will be used, if technically feasible. Setting SC to 0 results in the largest possible drawing regardless of the scale. The user specifies the scale and by setting W and/or H to zero the appropriate paper size is automatically chosen. If only one of the two values is set to zero, then the drawing size will be automatically calculated to fit in the second direction, the scale does not need to be defined in this case. When using TYPE you can also specify the American formats or the special format for HewlettPackard Plotters instead of the DIN sizes. In this case a frame is created around the picture using the inputs of FORM and MARG. This picture will printed with program URSULA in exactly this form. In the case of URS or P001...P999 a picture without a frame is created. Then the frame is drawing from program URSULA before printing. URS uses the current URSULA profile. P... selects a profile number predetermined with URSULA. A preceding minus sign selects the portrait orientation: URS,URS P001...P999 A,A B,B C,C D,D HPA,HPA HPB,HPB HPC,HPC HPD,HPD HP4,HP4 HP3,HP3 HP2,HP2 HP1,HP1 The maximum size usable within URSULA The size usable within URSULA from a profile number ANSI Paper A ANSI Paper B ANSI Paper C ANSI Paper D (11 x 8.5 inch) (17 x 11 inch) (22 x 17 inch) (34 x 22 inch) (259 x 199 mm) (416 x 259 mm) (529 x 378 mm) (809 x 528 mm) (276 x 193 mm) (404 x 276 mm) (564 x 366 mm) (787 x 564 mm)

Hewlett Packard Paper A Hewlett Packard Paper B Hewlett Packard Paper C Hewlett Packard Paper D Hewlett Packard Paper 4 Hewlett Packard Paper 3 Hewlett Packard Paper 2 Hewlett Packard Paper 1

Version 2010

633

SOFiSTiK
WIN,WIN MP,MP LP,LP MPW

Basics
Paper size of current WINDOWS printer Matrix printers with 8 x 12 inch (200 x 287 mm) Laser printers with A4 paper (198.4 x 280 mm) Wider Matrixprinters 14 x 12 inch paper For these formats the default is MARG NO.

634

Version 2010

Basics
6.4. Generation of Pictures

SOFiSTiK

With the following records true scale sketches may be inserted within the comments before or after the analysis. The classical GKSprimitives Polyline, Polymarker, fill area and text are available. Further there are the generalized Drawing primitive and a special command to measure distances which provides extended labelling possibilities.

6.4.1.
Item

<PICT> Start of a picture

Description

XCM YCM TEXT

Horizontal size Vertical size Heading of picture

Every picture starts with the record <PICT> . It contains all elements up to the next </PICT>. A transformation No 1 will be preset in cm as dimension.

6.4.2.
Item

GNT Scale of a picture

Description

NO SC XMIN YMIN XMAX YMAX WXMI WYMI WXMA WYMA

Number of transformation Desired Scale Window of usercoordinates

Window of workstation (paper space)

A transformation is selected (only NO given) or defined with this record. The program will automatically select an uniform scaling in all directions. If the user wishes different scalings in X and Ydirection. he has to specify SC < 0 and all four coordinates of the window. GKS supports three different transformations.

Version 2010

<PICT>
* *
Unit Default

cm cm Lit64

GNT
Unit Default

* * * * cm cm cm cm

* 0 * 0 *

635

SOFiSTiK

Basics

6.4.3.
Item

GPL Polyline
Description

X1 Y1 X2 Y2 .... X16 Y16

Coordinates of Polygon (Alternate definition of polygons is via multiple records each containing only one single vertex X1,Y1. This allows the definition of up to 255 vertices)

6.4.4.
Item

GPM Polymarker
Description

X1 Y1 X2 Y2 .... X16 Y16

Coordinates of Polymarker locations

6.4.5.
Item

GFA Fill Area

Description

X1 Y1 X2 Y2 .... X16 Y16

Coordinates of Fill area (Alternate definition of polygons is via multiple records each containing only one single vertex X1,Y1. This allows the definition of up to 255 vertices)

636

GPL
Unit Default

* * * * ... * *

! ! X1 Y1 ... X15 Y15

GPM
Unit Default

* * * * ... * *

! ! X1 Y1 ... X15 Y15

GFA
Unit Default

* * * * ... * *

! ! X1 Y1 ... X15 Y15

Version 2010

Basics
6.4.6.
Item

SOFiSTiK
GGDP Generalized Drawing Primitive
Description

TYPE

Type of element CIRC Full circle ARC circular arc VECT centred vectors VEC1 starting vectors VEC2 ending vectors Coordinates or Increments of coordinates of element

X1 Y1 X2 Y2 .... X15 Y15

The GGDP is a method provided by GKS to create more complex primitives. With SOFiSTiK these are: CIRC RC VECT A full circle with centre at (X1,Y1) and a point on the periphery (X2,Y2). OPT is not used. A circular arc with centre at (X1,Y1) and a periphery from point (X2,Y2) to (X3,Y3). OPT is not used. A single vector at point (X1,Y1) with the directional components (X2,Y2) or an array of vectors extending along the base line from P1 to P3 to P5 etc in the direction P2, P4 P6 etc. VECT will draw the vectors with its centre at the baseline, while VEC1 will put the starting point and VEC2 will use the end point with the arrow head at the baseline.

Version 2010

GGDP
Unit Default

LIT

CIRC

* * * * .... * *

! ! ! ! ....

637

SOFiSTiK

Basics

6.4.7.
Item

GTXT Text Label

Description

X Y TEXT VAL DIM ND

Coordinates of insertion point Text numeric value Dimension Number of digits

Text may be positioned in several ways. The displayed text itself may be composed from a given text and an numerical value. For the latter you may select a conversion and format according to the SOFISTIK.DIM.

6.4.8.
Item

GSCA Dimensioning
Description

X1 Y1 X2 Y2 TEXT VAL DIM ND

Coordinates of first point Coordinates of second point Text Numeric value Dimension Number of digits

GSCA is a special form of labelling. A dimensioning line will be drawn and a text will be written at the line. The default of the text is the distance between the two points, but it may be specified as explicit number and/or a given text. The combination of the default distance with a given text requires the text to end with an equal = sign. For the shown value a conversion and format according to the SOFISTIK.DIM may be selected.

638

GTXT
Unit Default

* * *

! ! 1 *

GSCA
Unit Default

* * * * *

! ! 1 *

Version 2010

Basics
6.5. Attributes of Graphic Representations

SOFiSTiK

The drawing elements Line, Mark, Text and Area can have various attributes. The user usually specifies all the attributes within the programs with graphical output by entering bundled numbers. These are constructed according to the following expression: ind = 1000 col + 100 ibr + ityp For Windows programs different palettes are foreseen for screens with bright or dark background as well as monochrome or coloured printers. You can change these definitions via URSULA Options in the Registry for all programs. The following CADINPrecords are only available within the picture definitions <PICT> ... </PICT>. The comments and descriptions of the parameters are valid however for all other graphical programs as well.

Version 2010

639

SOFiSTiK

Basics

6.5.1.
Item

GCOL Colour Selection

Description

COL R G B

Pen number or colour name Red component Green component Blue component

GCOL selects the colour for all primitives. For COL you have the choice between one of the numbers from 1 to 15 or the literals for the standard colours from below. If your device allows it, you may specify a colour (recommended 9 to 15) by its RGBcomponents. col = Colour Index STAN RED GREE BLUE YELL MAGE CYAN BROW 0 1 2 3 4 5 6 7 8 = background = black or white = red = green = blue = yellow = magenta = cyan = brown (Pen 1) (Pen 2) (Pen 3) (Pen 4) (Pen 5) (Pen 6) (Pen 7) (Pen 8)

640

GCOL
Unit Default

Version 2010

Basics

SOFiSTiK

6.5.2.
Item

GPLI Polyline Attributes

Description

IND COL TYPE

WIDT SCAT

Bundled SOFiSTiKIndex Colour (as with GCOL) Line type SOLI solid DASH dashed DOT dotted DDOT dashdotted NDAS narrow dashed NDOT narrow dotted NDDO narrow dash dotted WDAS wide dashed WDOT wide dotted WDDO wide dashdotted Width factor of line Style of dimensioning GSCA 1 inclined small lines 2 small circles 3 arrow heads

For Polylines holds for the bundled index: ind = 1000 col + 100 widt + type widt = Line thickness factor 0 = normal thickness 1 = thickness times 1.4 2 = thickness times 2.0 3 = thickness times 2.8 4 = thickness times 4.0 5 = thickness times 5.6 etc. 1 = continuous 2 = medium dashed 3 = medium dotted 4 = medium dotted dashed 5 = tightly dashed

type = line style

Version 2010

GPLI
Unit Default

/LIT LIT

641

SOFiSTiK
6 = tightly dotted 7 = tightly dotted dashed 8 = sparsely dashed 9 = sparsely dotted 10 = sparsely dotted dash

Basics

642

Version 2010

Basics

SOFiSTiK

6.5.3.
Item

GPMI Polymarker Attributes

Description

IND COL TYPE SIZE

Bundled SOFiSTiKIndex Colour (as with GCOL) Marker type (Number or Literal) . + * o X Scale factor

For Polymarkers hold: ind = 1000 col + 100 size + type size = marker size 0 = normal size 1 = size times 1.4 2 = size times 2.0 3 = size times 2.8 4 = size times 4.0 5 = size times 5.6 etc. 1 = . Point 2 = + Plus 3 = * Star 4 = o Circle 5 = x Cross

type = Mark type

Version 2010

GPMI
Unit Default

/LIT LIT

643

SOFiSTiK

Basics

6.5.4.
Item

GTXI Text Attributes

Description

IND COL H BX BY HALI

Bundled SOFiSTiKIndex Colour (as with GCOL) Text height Writing direction Horizontal alignment NORM default of PATH LEFT aligned to the left CENT centred RIGH aligned to the right Vertical alignment NORM default of PATH TOP top of cell CAP top of characters HALF centre line BASE writing line BOTT lower bottom line Writing direction RIGH to the right LEFT to the left UP upwards DOWN downwards Expansion factor Additional spacing Font number

VALI

PATH

EXPA SPAC FONT

For text the following hold for the bundled index: ind = 1000 col + font font = Character style installation dependent

644

GTXI
Unit Default

/LIT cm LIT

1 1 0 NORM

LIT

NORM

LIT

RIGH

1.0 0.0

Version 2010

Basics

SOFiSTiK

6.5.5.
Item

GFAI Fill Area Attributes

Description

IND COL STYL

TYPE

Bundled SOFiSTiKIndex Colour (as with GCOL) Fill area Style HOLL Hollow SOLI Solid PATT Pattern HATC Hatch BPAT Pattern with boundary BHAT Hatch with boundary Style index

For areas (Fill Area) for the bundled index holds: ind = 1000 col + 100 styl + type 0 = hollow (only boundary drawn) 1 = solid (entire area filled) 2 = pattern 3 = hatch type = Fill Area Style Index (only styl =2/3) The effect of the parameter type is device dependent. Classical vector plotters for example cannot represent any bit patterns. Pattern 1 corresponds to completely blank, whereas pattern 2 usually corresponds to a uniform sparse shading, which gets more dense by increasing numbers. Special patterns are reserved from type=11 and above. Adding a 32 to a pattern will make it opaque. Different variations exist for opaque hatch lines, in one or two directions. type 1/2/3 4/5/6 712 1324 25,26 27 = = = = = = vertical / horizontal / vertical+horizontal diagonal +45 deg / 45 deg / +45 and 45 deg as 1 to 6 dashed as 1 to 12 with larger scale reinforced concrete earth ibr = Fill Area Style

Version 2010

GFAI
Unit Default

/LIT LIT

645

SOFiSTiK
6.6. 6.6.1.
Item

Basics

Insertion of a Picture <LINK> Insertion of a Picture

Description

filename.bmp

Pictures with BMPformat can be inserted with <Link> in input files and templates. The insertion of pictures is not possible in a block for texts with <Text> ... </Text> or for pictures which should be generated with <Pict> ... </Pict>.

646

<LINK>
Unit Default

LIT72

Version 2010

Basics
6.7. Parametric Input.

SOFiSTiK

The current version of the input language CADINP allows the definition of standard input with free parameters. For example, a simple truss of the following type can be defined by:

Truss The parameters here are the span width, the height as well as the crosssectional area of the bars. An input for SOFIMSHA could be defined as follows: HEAD TRUSS $ LET#1 12.40 $ SPAN WIDTH LET#2 2.30 $ HEIGHT $ NODE 1 0 0 PP (2 4 1) (#1/4 #1/4) 0 5 #1 0 PP NODE 6 #1/4 #2/2 7 #1/2 #2 8 3*#1/4 #2/2 TRUS (1 4 1) (1 1) (2 1) NCS 1 TRUS 5 1 6 NCS 1 6 6 7 == ; 7 7 8 == ; 8 8 5 == TRUS (11 13 1) (2 1) (6 1) NCS 2 TRUS (14 15 1) (6 2) 3 NCS 2 END More powerful data generation is available using loops. For example, the following input allows the generation of a series of nodes on a hyperbolic arc:

Version 2010

647

SOFiSTiK

Basics

PROG SOFIMSHA HEAD Cooling Tower $ Meridian Hyperbolic equation (r/r0)**2((zz0)/zz)**2 = 1 $ (r1/r0)**2(z0/zz)**2 = 1 => (1/zz)**2 $ (r2/r0)**2((hz0)/zz)**2 = 1 $ parameter: sto#H 160.0 $ Total Height sto#R0 30.0 $ smallest radius sto#R1 55.0 $ Radius at bottom sto#R2 35.0 $ Radius at top let#1 SQR(#r1**2#r0**2) LET#z0 #H*#1*(SQR(#R2**2#R0**2)#1)/(#R2**2#R1**2) let#zz #z0/SQR((#r1/#r0)**21.0) let#m 16 $ subdivision in height TXB Generation of a hyperbolic cooling tower TXB height radius TXB 0.0 #(r1,9.1) TXB #(z0,9.1) #(r0,9.1) TXB #(h,8.1) #(r2,9.1) TXB TXB Parameter zz of hyperbolic equation = #(zz,9.3) $ let#2 #H/#m $ deltaz LOOP#1 #m+1 ; let#z #1*#2 NODE #1*50+1 #r0*sqr(1.+((#z#z0)/#zz)**2) 0.0 #z ENDLOOP For the beginner these inputs are likely to be confusing, however, this is a very powerful possibility which allows to automize frequently happening calculations. Many macros have developed from simple beginnings.

648

Version 2010

Basics
6.8. Compatibility of Data files

SOFiSTiK

Text based input data is suited to be used for long term storage of data, better than any proprietary binary format. Unfortunately the input syntax is changed some times, SOFiSTiK has to consider the readability of the manual, the catch of data errors and the compatibility of the data records. Thus we have established the following guidelines: Input records will be extended most likely at the end of the structure, but if an entry fits in better at an other position (e.g. third coordinate added) it will be inserted. Especially designations will remain the last entry in most cases. Thus the user should use the names of the item as a prefix for all extended data, eg.: NODE 100 10.25 20.00 24.00 FIX PZ For larger data volumes the use of a table is always favourable, the use of explicit standard items should be avoided. For exported data the deletion of unnecessary data may help to reuse elder data records. It is also possible that the names of a record or the items will be changed. This is a strong indication for a changed syntax or data format. Although we try to catch as many old data definitions (eg. mm instead of m), the user should control his data in those cases thoroughly. There are also some cases where a possible literal has the same name as an item or record name. The use of quotes for the literal will then allow a unique identification. A very common case however is that the defaults have to be changed. This may be triggered by change of the design codes, a better programming logic or the demands of our customers. There is no golden way. If one specifies only the minimum range of values, one may reuse the data more easily, but it may happen that a new release will produce different results. The default to select national dependant parameters depending on the settings of the operating system is a nice feature, but it may create different results on different computers and should be avoided therefore.

Version 2010

649

SOFiSTiK
This page intentionally left blank

Basics

650

Version 2010

Basics
7 DEF Environment Variables.

SOFiSTiK

A lot of parameters for SOFiSTiK programs are defined by the environment variables. A variable has a name usually in capital letters and a string, which can be used in specific locations. The relevant topics are: Settings for layout (paper size, output language etc) Parameters for the database CDBASE (buffer, multitasking etc.) Standard input records The environment variables are set in the classical way with the commands of the operating system (My Computer>Properties>Extended). In a CMDBox this is done via:
SET parameter=Value

In UNIX it is necessary to use shellcommands like:

export parameter parameter=value setenv parameter value

Bash, Bourne and Korn shell Cshell

As many of these parameters are only needed for individual programs, it makes sense to keep these definitions in a configuration file. For SOFiSTiK programs this file is
SOFISTIK.DEF

In this file all variables for SOFiSTiKEnvironment as well as any definitions of input macros can be stored (see Chapter 8.2.):
e.g. SOFISTIK_C=49 GRAFSIZE=SIZE HP 0 HEAD1=New Building InsuranceCompany STDMAT=BETO 1 B 35 ; STAH 2 BST 500

The definition of the input file has priority. Then comes the definition in the environment of the operating system, and at last a definition in SOFISTIK.DEF. If for different projects different properties are requested, it is recommended to save the SOFiSTiK.DEF file in the project directory. This should be done when editing with TEDDY via SOFiSTiK > Options.

Version 2010

71

SOFiSTiK
The following table contains the currently known/used values: Variable
SOFISTiK_NAME SOFISTiK_C Parameters (separated by comma) alternate user name nation (International Telefon code) 00 01 49 43 41 44 81 86 91 30 31 32 33 34 45 46 47 39 351 352 353 358 2 = = = = = = = = = = = = = = = = = = = = = = = possible values

Basics

Generic Europe United states Germany Austria Switzerland Great Britain Nippon China India Greece Netherlands Belgium France Spain Danmark Sweden Norway Italy Portugal Luxembourg Ireland Suomi/Finland utf8

ch_set (character set of computer) Input language SOFISTiK_A Headder type in printout

0 1 0 1 2 3 0 1 2 3 3 2 1 0 1

= German = English = = = = = = = = = = = = = one line multiple lines ZTVK grafical ZTVK standard chars deutsch englisch franzsisch spanisch nothing at all only error messages errors and warnings statistics computing times

language of output

level of messages

Units of output

see SOFISTIK.DIM

72

Version 2010

Basics
Variable
SOFISTIK_P Parameters (separated by comma) Parameters for LST/ERG files number of lines per page No of columns left margin No of lines bottom margin No of lines top margin Type of formfeed 68 6 0 0 0 1 2 0 1 82 0 1

SOFiSTiK
possible values

= blank lines only = formfeed character = 1H1 (old FORTRAN) = default = convert UNIX to WIN = default = omit numbers

Type of linefeed Total of printable columns Pagenumber SOFISTIK_GH SOFISTIK_GW KOPF1 KOPF2 KOPF3 SOFISTiK_PRODIR SOFISTiK_TMPDIR PSJOBPAR PSJOBINFO CDBASEMEM CDACCESS Size of default Grafic area for URSULA in mm First Headder Line Second Headder Line Third Headder Line alternate directory for the database and project files alternate directory for all temporary project files Default Values for PS Time & File stamping for PS Size of Memory for CDBASE in Bytes or MBytes CDBASE multitasking feature

Default fits in all versions of layout, larger

Saves all project files without explicit pathname Defaults to SOFISTIK_PRODIR see Chapter 6. see Chapter 6. default: 1MB SINGLE = deactivate NOWAIT = do not wait if locked (usefull for remote analysis)

Version 2010

73

SOFiSTiK
Variable
CDBASETEMP CDBASEVER Parameters (separated by comma) Directoryname for temporary scratch files Version of CDBASE format possible values

Basics

Using TEMP or TMP if not defined CDBASEVER=400 max. 2 GB, compatibel to 97. CDBASEVER=401 as Version 501, but without password option CDBASEVER=403 as Version 503, but without password option CDBASEVER=501 maximum 256 GB (Default) CDBASEVER=503 maximum 1024 GB

The variables which are described in the above table have to be set in the SOFISTIK.DEF at beginning before the first expression in parentheses:
SOFISTIK_C=... SOFISTIK_GH=... SOFISTIK_GW=... SOFISTIK_A=... SOFISTIK_P=... [Layout1] ....

74

Version 2010

Basics
8
8.1.

SOFiSTiK
Starting an Analysis.
Generalities

Each program expects its input data in a file. The input consists of records, which have a name and are constructed in free format according to the CADINP rules. Generally several individual modules are executed while working on a project. The interaction of these modules is necessary for a complete analysis. In this case the normal procedure is to gather the entire data in one or a few files, and through the appropriate records within the data make calls to the respective programs. Therefore the structure of an input file results in the following scheme: +PROG AQUA Input data for program AQUA +PROG SOFIMSHA Input data for program SOFIMSHA +PROG STAR2 Input data for program STAR2, 1st load case END Input data for program STAR2, 2nd load case END +SYS COPY *.ERG D: +PROG WING Input data for graphics END The first line should be a PROG line. Each module can be called as often as desired. The order of execution of the programs corresponds to the order of the PROG lines in the file. If PROG is entered instead of +PROG, the associated module will be omitted. Single modules can also be selected directly.

8.2.

#DEFINE Parameter Substitution

SPS is further capable of making global replacements in the input file. The declaration of text macros must take place before they are used. This is done via a line

Version 2010

81

SOFiSTiK

Basics

#define text=name. The name of a text macro consists of up to 10 characters without $. The first character of a name of a text macro has to be a letter. The value of the text macro is a text of arbitrary length. Parameters within an assignment are not evaluated until the replacement. A redefinition of an assignment is possible. A parameter in the input data or in a block can be referred to by using the syntax $(name). Blank spaces are not allowed between $ and (. Upper/lower case letters have no influence. The replacement can be recursive. Definitions like $(A$(INDEX)) are allowed. Example: $PROG #define #define #define #define PROG CONC STEE SREC SREC END PROG SYST NODE NODE NODE BEAM BEAM END (extension for TEDDY) LENGTH=3.70 WIDTH=30 HEIGHT=50 PLATE=50 20 10 80

AQUA 1 B 25 1 BST 500 1 $(HEIGHT) $(WIDTH) 2 $(PLATE) ASU 2.3 SOFIMSHA GIRD 1 0.0 0.0 FIX PP 2 $(LENGTH)/2 0.0 3 $(LENGTH) 1 1 2 1 2 2 3 1

Unlike the CADINP variables #() the $() variables are replaced by strings, so we can insert literals or generation macros. There are two default parameters, namely $(NAME) containing the primary name of the output file and $(PROJECT) containing the name of the project. These can be helpful especially for SYS commands. Text macros which are not defined in the input file can be set with a SETrecord. When the command (e.g. in the environment) is given:

82

Version 2010

Basics
SET SIZE=LP O FORM ZTVK SPS can insert in all the files the relevant format: SIZE $(SIZE)

SOFiSTiK

Moreover it is possible to describe global parameters for SPS in a SOFISTIK.DEF file. This results in a hierarchy of three layers: Firstly a definition in the input data Secondly the definition with SET (to be avoided!) Lastly a definition in SOFISTIK.DEF

8.3.

#INCLUDE Block Definitions

By the use of block building several lines of the data can be used more than once at any point in the dataset. A maximum of 256 internal blocks and an unlimited number of data blocks in an arbitrary order are allowed. Blocks can be recursively built in a depth of up to 32 levels. #DEFINE name #ENDDEF #UNDEF name #INCLUDE name Beginning of block name (up to 8 characters) End of block Delete a defined block Insertion of block name from memory or file name

Using blocks does not only free the user from copying reoccurring input lines, but also enables the use of subprograms. Example: #define SECT $PROG AQUA $ TRAPEZOIDAL CROSSSECTION PARAMETER BO,BU,H POLY UPZ VERT 1 #1/2 #3/2 2 #2/2 #3/2 CURF 3 #enddef PROG AQUA

Version 2010

83

SOFiSTiK
STEE 1 ST 37 SECT 1 ; LET#1 0.60,0.20,0.60 #include sect SECT 2 ; LET#1 0.60,0.30,0.60 #include sect SECT 3 ; LET#1 0.60,0.30,0.70 #include sect END

Basics

When inserting files in UNIX it is important to consider the lower/uppercase letters used for the filenames! The old formats $BLOCK BEG/END/SET are still supported, but should not be used anymore.

84

Version 2010

Basics
8.4. #IF Conditional Input

SOFiSTiK

IF THEN ELSE constructions can be defined. This means that larger input blocks can be inserted and removed, which is more difficult using the IF constructions in CADINP, and that several program calls can be grouped in one block. The relevant control lines are familiar to all CProgrammers. In the first column the following possibilities can be used: #if expression any line, also PROG and SYS #else any line, also PROG and SYS #endif expression may be just the name of a block or a variable which is evaluated to be true if it is defined and not empty and not equal to zero. But it might be also a comparison $(MODE)==EC or $(MODE)<>EC or $(MEMBERS)>3. Be aware however that the comparisons are purely lexically based on strings, adjusted to the right for numbers, and to the left for all other cases. Therefore we have A<B, AA < BA, 10<18 but unfortunately also 10.0 > 12. If expression is not true, the first block will be skipped and the block after #else will be used. Naturally the second block can be omitted if not needed. These constructions can be nested in up to 32 levels. An unmotivated #else or #endif will lead to errors, as well as an unfinished construction. Example: #define DOAQB=0 #if DOAQB PROG AQB HEAD ..... LC ..... DESI ..... END #endif PROG STAR2 HEAD .....

Version 2010

85

SOFiSTiK
#if DOAQB $ Design with AQB #else DESI ..... #endif ..... END

Basics

The indentation is only used for readability. In the above example STAR2 is used for the design. If DOAQB=1, AQB is used for the design task.

8.5.

Templates

A special form of input files is called a template. The structure of these files is given as follows: #DEFINE #DEFINE #DEFINE #DEFINE L1=10.0 L2=20.0 L3=30.0 P=12.0

PROG TEMPLATE (or any other program name) LET#L1 $(L1) LET#L2 $(L2) LET#L3 $(L3) LET#L #L1+#L2+#L3 <TXA> This is the analysis of a continuous beam with 3 spans: L1 = <EDIT:L1>$(L1)</EDIT> L2 = <EDIT:L2>$(L2)</EDIT> L3 = <EDIT:L3>$(L3)</EDIT> SUM = #(L,10.2) </TXA> <PICT> .... </PICT> PROG AQUA following al the data In many cases this is like a normal dataset, which only includes the preface of the total analysis. It is summarised under a special program name called TEMPLATE.

86

Version 2010

Basics

SOFiSTiK

The input consists only of text and picture elements combined with arithmetic expressions. But the mechanism is general available for all programs. Now within URSULA you may change the selected parameters and reanalyze this given module. This allows other users to benefit from these macros which may contain rather complicated treatment, but need only a few problem dependant parameters .

8.6.

Iteractive Analysis with Multiple Modules.

2nd Order Theory for nonlinear materials is contained in the programs STAR2/AQB. However, only one method of computation of the reinforcement can be considered by STAR2. A computation with different methods can be implemented by an iteration between AQB and STAR2. The iteration is controlled by the parameter ITER of the record PROG. PROG STAR2 CTRL I LC .... END PROG AQB ITER parm BEAM ....; LC.... ULTI ....; NSTR.... END BEAM ....; LC.... ULTI ....; NSTR.... END PROG STAR2 ITER parm HEAD .... CTRL II 1 END 1st Step for 1st Order Theory Definition of loading cases parm separated by blank spaces 1st selection and design definition 2nd selection and design definition

The maximum number of iterations to be made is regulated by ITER (e.g. ITER 30), default is 20 iterations. This mechanism has been extended with Release 23 for other combinations of general modules. To terminate the iteration it is required to specify within the CADINPdefinition explicitly EXIT_ITERATION.

Version 2010

87

SOFiSTiK

Basics

PROG TEMPLATE STO#TARGET 0 ; STO#PARAM 1.0 PROG AQUA ITER RCL#PARAM QNR .... Definition of sectuion using #PARAM PROG AQB ITER BEME .... Design and save results ENDE @KEY / LET# TARGET ... Calculate a target function to become zero IF ABS(#TARGET)<0.001 EXIT_ITERATION ELSE STO#PARAM new_target_value ENDIF

8.7.

Operating System Commands.

Any desired shell commands can be integrated in an analysis. Parameter substitution is also active for these lines, for example the character string $(NAME) is replaced by the primary name of the input or the output file, while $(PROJECT) is replaced by the name of the project. *SYS command +SYS command SYS command command will be executed as in any batch file, if the last PROG line was active. command will be executed as in any batch file. command will not be executed, all following *SYS lines deactivated.

e.g: +SYS del $(PROJECT).$D1 deletes the stiffness matrix

+SYS wait name.exe parameter WPS is initiated to wait with the processing of the further modules until the active process is finished with +SYS wait name.exe.

88

Version 2010

Basics
8.8. Job History

SOFiSTiK

In an analysis with many individual programs it can become of importance to make a reconstruction for the timehistory of a problem. Therefore SPS adds some auxiliary information to the generated input files. The information is controlled by an environment variable: SET PSJOBINFO=n n n n n = = = = 0 1 2 3 no information filename and date (only in data echo) like 1, including job number (only in data echo) like 2, yet in an additionally generated header

The default is 2. The job number consists of an 8letter description of the computer and a varying number, which is stored in a PSJOBNR file. In a multiuser environment PSJOBNR should be put in the current directory, if access conflicts have occurred. Examples for PSJOBINFO: PROG AQUA $ Datafile: D:\STATIC\P00\DAT0.DAT HEAD ..... PROG AQUA $ Datafile: D:\STATIC\P00\DAT0.DAT $ Jobnumber: PCNr:17/8700063 HEAD ..... (.#01) 14:48:48 25/05/95

(.#01)

25/05/95 14:48:48

The file PSJOBNR is needed for cases with PSJOBINFO=2 or higher. The first 8 columns contain any desired text. They are not printed, if they are blank. If SPS does not find a PSJOBNR file, it will create one in the local directory.

Version 2010

89

SOFiSTiK
8.9. Start of a Single Program

Basics

Sometimes it can occur that one would like to start a program directly. This is generally possible if the input file already contains all parameter replacements. If you want to create a parsed file from a normal input file, you can do this by using WPS with File > Save Parsed File ... if you want to save the complete parsed file or alternatively with File > Save Parsed Module: name ... if only a single module is required to be parsed. The module selection is done in the WPStree.

810

Version 2010

Basics

SOFiSTiK

The start of the single programs occurs then with program filename [parm] [projekt] filename is the name of the input file; it indicates also the basic name of the output files. If the name contains blanks, it must be enclosed with . project is the name of the data base. In general the same parameters as for SPS are used in parameter. Some extra parameters are added though. For example in controlling, what type of metafile is to be created and whether an existing metafile is appended or deleted. If one starts an analysis program without using any parameters, the program will start up by showing its name, version number and the list of the possible parameters. The user is asked for the name of an input file. An empty input file (or Return key) ends the program immediately. This procedure is helpful in order to test the integrity of the program. The license and the version of the ERRfile are checked.

Version 2010

811

SOFiSTiK
8.10. Special Features for Start

Basics

For special cases the user may start the program from a command shell by using the following command lines: Parameter + or ++ 0 1 2 3 4 nosingle test Description Opens the last file or the last but one. Is used without a switch or / . Allows the start of up to 5 instances (Default: 0). Starts the application as a separate instance (no single application). A general test flag is set. This is only of interest for the developers. Depending on the level of development, an individual message window is activated. WPS starts in batch mode. The calculation is started immediately and at the end the window is closed automatically. Generates a message window at the end of the calculation if an error occurs. Makes sense only in connection with b or run. If the parameter e is not set and the calculation ends with an error, no message window is indicated. Nevertheless, WPS does not end, so that the error can be read in the error protocol. Closes the window after calculating regardless of whether an error has occurred or not. Makes sense only in connection with b or run and without e. After a calculation the window does not close. Makes sense only in connection with b or run. Attaches the result file (name.plb or name.erg) to a perhaps available result file. The calculation starts immediately (e.g. when calling from Teddy with "quick start").

close

noclose z run

812

Version 2010

Basics
run:xx

SOFiSTiK
The calculation starts immediately (e.g. when calling from Teddy with "quick start"). xx is the number of the PROG line, which is the only active module to be calculated. Sets the module "PROG module urs: xx" active and all other inactive. Name of the CDB (if the name differs from DAT name).

urs:xx cdb:name

Version 2010

813

SOFiSTiK
This page intentionally left blank

Basics

814

Version 2010

Basics
9 Output.

SOFiSTiK

During calculation with PS / WPS three output files are generated in general: the protocol file (.PRT) the result file (.LST and .ERG) the URSULA output and graphic representations (.PLB)

9.1.

Protocol File (.PRT)

The .PRT file is a text file and nominated as protocol file and contains important messages about the general operating situation. It will normally only be needed in case of errors or bad performance problems. It contains for example: the startup information, version numbers, consumed computing times, information about errors, convergence conditions, files etc.

9.2.

Result File (.LST and .ERG)

The .ERG file is a text file containing the entire text output in a form suitable for printing. This file can also be examined or edited by a text editor or printed as it is. Page numbering is performed automatically by the programs of the SOFiSTiK series as determined by the database. Under Windows the output of the files occurs over the Windows printer drivers. They are activated by option print or by drag and drop onto a printer icon.

Version 2010

91

SOFiSTiK
9.3. 9.3.1. Printout with URSULA. General

Basics

URSULA is a resultviewer, which is easy to use. It is used to accumulate the printout of all SOFiSTiK programs and to send it to the printing device. URSULA has a similar layout as the WindowsExplorer and provides the user with various options for designing individual printout, e.g. in the selective choice of the output volume (text / graphics) or in the layout design (company logo, footer, etc.). All the general settings (font, page numbers, date, margin, etc.) are defined in the menu SOFiSTiK > Global Options and SOFiSTiK > Project Options (see in the Administration Manual).

9.3.2.

Activation of URSULA
A specific check box within WPS (Default in SOFiSTiK > Global Options) has to be activated before URSULA can be used. After an analysis the printout (with the extension PLB) can be opened via the URSULA icon. The output can be modified according to user preferences. The userspecified settings are stored in a corresponding URSfile and are usually available after a recalculation.

9.3.3.

Features

Selecting the volume of the printout The output volume can be configured by the user to his requirements. With the bulb icon in the URSULA tree, the printout of the modules is activated or deactivated. With the book icons you can switch on and off the sections. The settings for the output volume are saved in the corresponding URSfile and are normally available again after a recalculation. Individual sections can be temporarily moved in the URSULAtree and the changes are considered when you print the file. However the changed sequence is no longer available after a recalculation. Therefore the requested module order should be defined already in the input file.

92

Version 2010

Basics

SOFiSTiK

Insert table of contents With Insert > Insert Table of Contents there is generated automatically a table of contents of the complete printout. For the module headings in the table of contents, the module text from the URSULA tree is inserted, or the module name if no text is defined. Disabled sections are not included. Furthermore, the page number of the printout is added. The setting Insert Table of Contents is saved in the URS file.

Version 2010

93

SOFiSTiK
9.3.4.

Basics

Support of international character codes (UTF8)

Starting with Version 2010, all special characters are shown with URSULA. The readability of the output result has been significantly improved. In particular, for instance, Greek symbols can be integrated in the expression.

9.3.5.

Printing Dialogue

Preview Window In the Print dialogue a preview window is added. Furthermore, the type and location of the selected printer is displayed. Output to File A printing output to a file is also possible. When selecting Generate PDF file, a PDF file created in the current directory with the associated filename name.PDF. No additional Software from Adobe is required.

94

Version 2010

Basics

SOFiSTiK

Special Print Options There can be printed several smaller pages on one sheet. Temporarily the design of the page number or the date can be changed for printing.

Version 2010

95

SOFiSTiK
9.3.6. Advanced Features

Basics

Zoom handling Besides the usual zoom functions, a slider is available, and so a fast and continuous zooming in the current window is possible. With Ctrl + mouse wheel a systematical zoom in or out is possible and with Ctrl + mouse drag, a specific zoom window can be opened.

Options of Selection By URSULA following selection options are supported: Line Block Column Block Table columns

96

Version 2010

Basics
Individual words

SOFiSTiK

With Edit> Copy, the selected area can be saved in the clipboard. A save in Excel format also is possible (Edit> Copy to Excel, and in Excel Edit> Insert Contents). The drawing of a line block with the mouse takes place outside of the margin.

The drawing of a column block with the mouse takes place within the margin. Alternatively first highlight a field in the header, now in connection with rightclick menu > Select Column a full column block can be selected.

Version 2010

97

SOFiSTiK

Basics

9.3.7.

Functions in control tree

Selection in the control tree Similar as in the Explorer, several sections can be selected with the Ctrl or Shift key in connection with the mouse and can be edited parallel in the rightclick menu. Support of the chapters If a result file is structured by chapter entries (> Input with TEDDY !#!Chapter), these chapters are supported by URSULA. The individual chapters can be activated or deactivated (at the disabled chapters the icon is rotated by 90) and completely pushed together (in the rightclickmenu).

98

Version 2010

Basics

SOFiSTiK

Assistance in troubleshooting In case of warnings the affected modules and the relevant sections of the printout are marked in the navigation tree by a green cross. Advanced editing capabilities of the PLB printout Custom changes to the result file (page breaks, blank lines, ...) are saved in the corresponding URS file. They are still available when the PLB is opened again. After a recalculation, they will only be available in exceptional cases, because a unique assignment is no longer possible.

Version 2010

99

SOFiSTiK
9.3.8. Special Features for Start

Basics

For special cases the user may start the program from a command shell by using the following command lines: Parameter + or ++ 0 1 2 3 4 test Description Opens the last file or the last but one. Is used without a switch or / . Allows the start of up to 5 instances (Default: 0). A general test flag is set. This is only of interest for the developers. Depending on the level of development, an individual message window is activated. Enforces a text view. Enforces a graphic view. Enforces an automatic refresh (no demand), if the PLB has changed. Supports steel list. Creates a text file. Explicit target of an URSfile. _xxx = List of pseudo extensions for a total file. Example: ursula name.plb ssd: _002; _003; _006 Creates from name_002.plb, name_003.plb and name_006.plb a total PLB. Adds several PLBs to a total file. Example: ursula name.plb plbs: name1.plb; name2.plb Creates from name.plb, name1.plb and name2.plb a total PLB.

t g r stli:AutoCAD Version txt:name.txt urs:name.urs ssd:_xxx

plbs:name1.plb; name2.plb

910

Version 2010

Basics

SOFiSTiK

9.4. 9.4.1.

Graphical Output GRAFiX. General Hints

GRAFiX is a program for the graphical postprocessing of calculations with Finite Elements and frame and girder systems. It allows the graphical representation of the most values and information which are saved in the database, e.g. information about structures, calculation and design results. Additionally to the functionality of the predecessor program WinGRAF, there are more results available for the graphical representation due to another interface to the database. Thereby a faster and more variable access on the database values is guaranteed.

9.4.2.

Work Flow

The program GRAFiX works with the graphical interface HOOPSOpenGL. Due to that there are more useful possibilities for the user, e.g.: interactive turn fast Hidden Line/Surface global transparency expansion of structural members interactive selection of single elements Due to the GUI interfaces QT and C++ a better handling is enable via variable GUI elements which can be scaled. The graphical representation of cross sections is possible in the program GRAFiX.

9.4.3.

Structure

Via a multidocument environment several databases which are represented and managed then in different windows can be opened simultaneously.

Version 2010

911

SOFiSTiK

912
text height transparency unit (vect. length) displaced structure exlosion repres. graphical area (several documents possible)

undo

representation sel.

material/time step

load case selection

cross section select.

result tree for current document

layer tree (layer per document)

Basics

Version 2010

Basics
10 Troubleshooting.

SOFiSTiK

In the following chapters we will give you some hints in case of problems with the usage of the software. Problems regarding the installation and the licencing are described in the Administrator manual.

10.1.

General Strategy

Please keep in mind the following points in case you encouter some incomprehensible errors: The probability that en error has been caused by wrong input is significantly large. The observation of warnings at any stage during the analysis or the installation can supply valuable hints. All programs, even those of SOFiSTiK, contain errors as long as the are used. They will show up most likely if you are in hurry and start treating some completely new application area of the programs. You should therefore first examine how the program behaves, using small examples. One of the most frequent causes of such errors is a misleading interpretation of the manual or the implemented theory. If the system was still working yesterday, think about what has changed since then (new computer, new operating system, other inputs etc.) In some cases an error message may not describe the real cause of the error, although this is highly unlikely. It might occur when the error was not correctly detected in a previous module. The programs do not stop at the first error they encounter, but try to continue and to detect as much errors as possible. Rather than searching for hours, sent a support request via Email to SOFiSTiK Hotline or your local supporter. Even if you may be charged for extensive services, it usually will be more economical as SOFiSTiK has better possibilities to locate the error.

Version 2010

101

SOFiSTiK
10.2. Standard Warnings and Error Messages

Basics

The story of an analysis is stored in a protocol file of the file type (*.PRT). In all special situations (program error or user error) this file must be examined. The execution of the analysis is automatically stopped if such an error occurs. Regular errors or Warnings have the form: Warnings, the program prints the message: ++++ WARNING NO. nnnnn IN PROGRAM xxxx as well as one or more lines of explanations. The analysis continues. User or data error, the program prints the message: ++++ ERROR NO. nnnnn IN PROGRAM xxxx as well as one or more lines of explanation. The analysis continues or stops. Finally, each program writes the number of warnings and errors in the .PRTFile. If the program has been aborted this will also be visible in this file.

10.3.

Troubleshooting Strategies

In the following chapters we like to introduce a few strategies, how to deal with program errors. In most cases you will be able to find and resolve your problem. Minimize Input Datafile: To minimize the SSD project files and SOFiPLUS drawings is the most important strategy to find and eliminate input errors Please delete every ssdtask, structural elements, program blocks, load cases, etc. which are not involved with your problem. Now you have a small and clear project, which can be checked easily. In almost every case you will find out where the problem occurs and also you will be able to solve it by yourself. Please use this strategy also if you cant find the problem and send your minimized project file with your support request via Email to support@sofistik.de .

102

Version 2010

Basics
10.3.1. Problems with Database (*.cdb)

SOFiSTiK

Error messages of the Database CDBASE can occur for the following reasons: The file size is more than the physical limit (2 Gigabytes). A possible solution is to reduce the size of the file by splitting and merging the file into several databases with DBINFO. The following CDBASERVER commands are available for the creation of a database: CDBASEVER=400 old Version, maximum 2 GB, compatible to 97, Current Default. CDBASEVER=401 new version, maximum 256 GB same space requirements as version 400 CDBASEVER=403 new version, maximum 1024 GB, Directory entries need more space. Due to an abnormal termination of programs the file gets disorganised. If only the locks are not released you may remove them with a special button or with the command: DBINFO projekt,Z If the file is badly damaged, the best solution is to delete or restore the database and repeat the analysis. Saving the data base periodically is quite wise especially for working with large projects.

10.3.2. Input Error in TEDDY Datafile

In case of a wrong input in the TEDDY file, the program gives you an error message. If you open the URSULA output and go to the ECHO print, the error message is plotted directly after the incorrect input line. Also the error message gives you some hints what should be the correct input. This will help you in most cases to find and eliminate the wrong input.

Version 2010

103

SOFiSTiK
10.3.3. Error in System Generation with SOFiPLUS

Basics

If you run into errors while meshing your SOFiPLUS drawing you may use a very simple algorithm to locate the problem. First mark randomly half of your structure and delete it. Now start the meshing again. If the problem occurs again, mark the next half of your structure,delete it, mesh again and so on. If the problem does not occur, go back and mark the other half of your structure, delete it and mesh again. With this principle of deleting stepwise half of the structure you will minimize your system. Probably you will find the error by yourself and can solve it. If the problem is solved you go back to your complete system and solve the problem there as well. If you cant solve the problem please send your minimized drawing to our support.

10.3.4. Error during Calculation

Normally we face two major problems in case the analysis will be aborted with an error message. Either the system is instable or no convergence was found during a non linear analysis. System instable: In case you use the program ASE for the analysis and have an instable system, the program calculates Eigenvalues using a numerical trick. Now you can check the displacements of the Eigenvalues with the ANIMATOR. Then you will see very quick, what causes the instability. Normally the instability problems occur in large 3d systems with lots of hinges and kinematic constraints. Therefore we recommend the following procedure: Create your system Step by Step and avoid to define any hinges and kinematic constraints in the first Steps. Now define a load case self weight and start the linear analysis. If you get some reasonable results go further on and start to define the first few hinges. Now export your system and start the linear analysis again. If everything works fine, go on with this procedure until everything is defined. If you work Step by Step, you always know the last changes and can easily go back. Possible input errors will be found very fast. In case you cant find the problem, please send your minimized file to our support. Nonlinear Analysis: The most common problem during a non linear analysis is, that no convergence will be reached. Either the structure is to weak for the applied loads, or the chosen algorithm has some numerical problems. In the first case you may change dimen-

104

Version 2010

Basics

SOFiSTiK

sions and therefore enforce the structure. In the second case you may change the iteration method. In both cases the program gives you detailed information about possible changes in your non linear analysis. With this hints you may solve the problem. In other cases please reduce your system to one single load case and delete everything, which is not necessary to reproduce the convergence problem. Sent this reduced file to our support.

10.3.5. Problems with Results

The interpretation of the results may cause some questions. Every manual contains a chapter Theoretical Principles. Inside this chapter the basics of the design algorithms are explained so that a manual check of the design results will be possible. In case there are still some questions open, please send a small example and also the results of your hand calculation to our support.

10.4.

Support

In case the above discussed strategies does not solve your problems, please contact our support via Email support@sofistik.de . You will find the General Terms of Support Conditions on our website:
http://www.sofistik.com/fileadmin/FILES/sonstiges/Terms and Conditions for SupportServices_01_02_2009.pdf

10.4.1. Support Accessibility

As you know, you may contact us via our SOFiSTiK Online Portal, via EMail, via Fax or via phone. In order to work most efficient without any interruption from incoming phone calls, you cant contact our supporters directly. Our primary target is, to help you as soon as possible and to increase our response quality level continuously. Most support requests are very complex and cant be solved in a short time. For that we work us into your problems and data files and contact you via EMail or phone call. Either we have a solution or we reproduced your problem and can start directly into a detailed discussion to find a common solution or at least a work around.

Version 2010

105

SOFiSTiK
10.4.2. Customers Obligation to Cooperate

Basics

In order to avoid time consuming mails and phone calls, would you please consider the following issues in your support requests. This assistance is very important for a fast and direct solution to your support request. We always need to know your customer number. For example you will find the number printed in the htmlfile of your last support request, or on your last maintenance invoice. We always need to know the used program versions. For example SOFiCADDetailing version 17.2 with AutoCAD 2008, or SOFiPLUS version 17.1 with AutoCAD 2008. Using the FEA package every analysis creates a protocol file *.prt containing all version numbers of the used programs. Please send us this file. Information about the operation system (for example Windows XP, Windows Vista 32 bit, Windows Vista 64 bit, Linux). Please note, we are not involved in your project and have no more information than what you sent to us. Therefore it is very helpful to get condensed data files and a precise problem description. Minimize your drawing or the project input data file. Delete everything which is not necessary to reproduce your problem. Please try to describe your problem as precise as possible. Under which circumstances does the problem occur? What did you do, which clicks? Example FEA: I checked the beam element 2037, x=0.00 m in loadcase 2031. I cant reproduce the amount of reinforcement computed by AQB (Version 13.4023) = 12.35 cm2. The result of my hand calculation gives me only 8.50 cm2. Please find attached my hand_calculation.pdf. Why are the results different? Provide us with additional information besides your data files, describe your workflow, send us scans of your hand calculation, every additional information helps. Please send us every necessary file, so we can reproduce your problem. FEA: files *.sofistik, *.dwg, *.dat, *.prt, diagnostic.xml and if necessary *.gra and *.plb. Please zipp all files We ask kindly for your understanding, but without all relevant data, we cant start working on your request.

106

Version 2010

Basics

SOFiSTiK

10.4.3. Support Request via SOFiSTiK Online Portal

With a valid maintenance contract you have also the possibility to use our SOFiSTiK Online Portal. Using this portal you will have the following benefits: Submit support requests directly in our system Submit support request out of the normal business hours Support requests via SOFiSTiK Online Portal will be processed with higher priority. Access to FAQdatabase to investigate for solutions Investigate in all your support requests Check the actual status of current support requests Every customer has one user account with administration rights. This main user can manage his company data, address, contact persons and SOFiSTiK Online user. For all this reasons we recommend to use this portal. You will find the portal via www.sofistik.com/support on the left hand side > Links > SOFiSTiK Online (Portal). A short description is also available on this website. Access Online Portal: https://wice.sofistik.de/plugin/wp_cic/main For clarity reasons it is very important to use a new support ticket for every question. Please reply only for direct questions to the key issue. For additional questions use a new ticket even if you refer to the same project files. This is very important if you like to investigate in old support requests.

10.4.4. Support Request out of SSD / TEDDY

Both SSD and TEDDY have a special function to create automatically a support request with all necessary description and attachments. Go to the menu HELP > SOFiSTiK Hotline Nevertheless we recommend to use our SOFiSTiK Online Portal

Version 2010

107

SOFiSTiK

Basics

10.4.5. Create a Diagnostic.xml File

All necessary information about installation, licences, program libraries are saved in a diagnostic.xml file. This file is very important for our supporters. To create this file go to TEDDY or SSD menu Help > Diagnostic. Please save the file with the command File > Save as Diagnostic. This file will be created automatically if using the command SOFiSTiK Hotline describe above.

108

Version 2010

Basics

SOFiSTiK

In special cases please start the program out of the program directory: e.g. C:\program files\SOFiSTiK\2010\Analysis.25\diagnose.exe

Version 2010

109

SOFiSTiK
This page intentionally left blank

Basics

1010

Version 2010

Basics
11 Additional Information and Help

SOFiSTiK

For a better understanding our software we provide the user with additional information, documents and examples. As a first choice we recommend to use our Infoportal on our website.

11.1.

Infoportal

On our website www.sofistik.com/Infoportal you may navigate through all sort of information. You may search in our document data base using the categories Document Type, Product Group, Subject and Application. A Search for Keywords is also possible. For example most program features of SOFiPLUS are shown in small Tutorial Movies.

Version 2010

111

SOFiSTiK
11.2. CADINP Samples

Basics

We provide the user with a large sample library sorted by program names. All samples are using the numerical CADINP input language. You will find all samples via TEDDY menu Help > Samples ... .

112

Version 2010

Basics
11.3. Forum

SOFiSTiK

Our User Group is open for all registered SOFiSTiK user and a place for discussion. Please send support requests exclusive via Email to support@sofistik.de and do not poste them into the User Group. You will reach our User Group via www.sofsitik.com/usergroup.

Version 2010

113