Sofistik Basic v.2010

SOFiSTiKBasics

Version 2010

� 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 permissionfrom SOFiSTiK AG. SOFiSTiK reserves the right to modify or to release neweditions 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 stronglyencourage the user to test the correctness of all calculations at least by randomsampling.

Basics SOFiSTiK

i

1 Introduction. 1−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1. SOFiSTiK 1−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2. Examples for the Use of the Software 1−1. . . . . . . . . . . . . . . . . . . . .

2 How to use SOFiSTiK. 2−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1. Principles 2−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2. Program Modules 2−3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.1. Preprocessing 2−3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.2. Analysis Programs 2−3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.3. Design Programs 2−4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.4. Postprocessing 2−4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3. User Interface. 2−5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4. Input Files. 2−7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5. Database 2−7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6. Interactive Modules. 2−10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7. News 2−11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.8. Name Conventions of the SOFiSTiK Files. 2−11. . . . . . . . . . . . . . . . . 2.9. Backup of Data. 2−14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.10. SOFiSTiK Options.. 2−15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.10.1. Language Settings 2−15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3 Graphical Input SOFiPLUS(−X). 3−1. . . . . . . . . . . . . . . . . . . . . . . . . 3.1. General Hints 3−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2. Work Flow 3−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1. Start without the program Structural Desktop (SSD) 3−2. . . . . . . 3.2.2. Start out of the program Structural Desktop (SSD) 3−2. . . . . . . . . 3.3. Structure 3−5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4 SSD − SOFiSTiK Structural Desktop. 4−1. . . . . . . . . . . . . . . . . . . . 4.1. User Interface SSD 4−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2. Basic Work Flow 4−3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.1. Groups 4−3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.2. Tasks 4−3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.3. Template Files name.sofistix 4−7. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3. Structure and Function Mode 4−11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.1. Calculation Status 4−11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4. Special Features for Start 4−12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5 Input with TEDDY. 5−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1. Overview 5−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SOFiSTiK Basics

ii

5.2. Support of international character codes (UTF−8) 5−2. . . . . . . . . . . 5.3. Starting the Editor 5−3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4. Commands 5−4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.1. Combinations with the Alt−key (selection) 5−5. . . . . . . . . . . . . . . . 5.4.2. Combinations with the Ctrl−key (selection) 5−5. . . . . . . . . . . . . . . 5.4.3. Overview of all Ctrl− / Alt−Commands 5−5. . . . . . . . . . . . . . . . . . . . 5.4.4. Example with Column Block 5−6. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5. Input of Data. 5−7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.6. Help and Interactive Manuals. 5−8. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.6.1. Activating the Help 5−8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.6.2. Acrobat Reader 5−9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.6.3. Creating Your own Comments 5−10. . . . . . . . . . . . . . . . . . . . . . . . . . 5.6.4. Export/Import of Annotations in Manuals 5−11. . . . . . . . . . . . . . . . . 5.7. TEDDY the SOFiSTiK − Commander. 5−11. . . . . . . . . . . . . . . . . . . . . 5.8. Special Features of SOFiSTiK 5−14. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.8.1. TEDDY Information Centre 5−15. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

Basics SOFiSTiK

iii

6.2.16. Conversion of Units. 6−15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.17. LOOP,ENDLOOP − Loops and Jumps 6−16. . . . . . . . . . . . . . . . . . . 6.2.18. IF − Logical Conditions 6−18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.19. @CDB − Selection of a CDBASE 6−19. . . . . . . . . . . . . . . . . . . . . . . 6.2.20. @KEY − Access to the CDBASE 6−20. . . . . . . . . . . . . . . . . . . . . . . . 6.2.21. @() − Access to the CDBASE 6−20. . . . . . . . . . . . . . . . . . . . . . . . . . 6.3. General Records. 6−24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.1. HEAD− Title Lines 6−25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.2. END − End of an Input Block 6−25. . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.3. TXB − Introducing Text 6−26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.4. TXE − Concluding Text 6−26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.5. <TEXT> − Text block 6−27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.6. </TEXT> − End of a text block 6−27. . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.7. ECHO − Output Control 6−28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.8. PAGE − Control of Input/Output 6−29. . . . . . . . . . . . . . . . . . . . . . . . . 6.3.9. SIZE − Graphic Format 6−32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4. Generation of Pictures 6−35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.1. <PICT> − Start of a picture 6−35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.2. GNT − Scale of a picture 6−35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.3. GPL − Polyline 6−36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.4. GPM − Polymarker 6−36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.5. GFA − Fill Area 6−36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.6. GGDP − Generalized Drawing Primitive 6−37. . . . . . . . . . . . . . . . . . 6.4.7. GTXT − Text Label 6−38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.8. GSCA − Dimensioning 6−38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5. Attributes of Graphic Representations 6−39. . . . . . . . . . . . . . . . . . . . . 6.5.1. GCOL − Colour Selection 6−40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5.2. GPLI − Polyline Attributes 6−41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5.3. GPMI − Polymarker Attributes 6−43. . . . . . . . . . . . . . . . . . . . . . . . . . 6.5.4. GTXI − Text Attributes 6−44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5.5. GFAI − Fill Area Attributes 6−45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6. Insertion of a Picture 6−46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6.1. <LINK> − Insertion of a Picture 6−46. . . . . . . . . . . . . . . . . . . . . . . . . 6.7. Parametric Input. 6−47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.8. Compatibility of Data files 6−49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7 DEF − Environment Variables. 7−1. . . . . . . . . . . . . . . . . . . . . . . . . .

8 Starting an Analysis. 8−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1. Generalities 8−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SOFiSTiK Basics

iv

8.2. #DEFINE − Parameter Substitution 8−1. . . . . . . . . . . . . . . . . . . . . . . 8.3. #INCLUDE − Block Definitions 8−3. . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4. #IF − Conditional Input 8−5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.5. Templates 8−6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.6. Iteractive Analysis with Multiple Modules. 8−7. . . . . . . . . . . . . . . . . . 8.7. Operating System Commands. 8−8. . . . . . . . . . . . . . . . . . . . . . . . . . . 8.8. Job History 8−9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.9. Start of a Single Program 8−10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.10. Special Features for Start 8−12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9 Output. 9−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1. Protocol File (.PRT) 9−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2. Result File (.LST and .ERG) 9−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3. Printout with URSULA. 9−2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3.1. General 9−2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3.2. Activation of URSULA 9−2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3.3. Features 9−2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3.4. Support of international character codes (UTF−8) 9−4. . . . . . . . . 9.3.5. Printing Dialogue 9−4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3.6. Advanced Features 9−6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3.7. Functions in control tree 9−8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3.8. Special Features for Start 9−10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.4. Graphical Output GRAFiX. 9−11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.4.1. General Hints 9−11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.4.2. Work Flow 9−11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.4.3. Structure 9−11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10 Troubleshooting. 10−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.1. General Strategy 10−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.2. Standard Warnings and Error Messages 10−2. . . . . . . . . . . . . . . . . . . 10.3. Troubleshooting Strategies 10−2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.3.1. Problems with Database (*.cdb) 10−3. . . . . . . . . . . . . . . . . . . . . . . . . 10.3.2. Input Error in TEDDY Datafile 10−3. . . . . . . . . . . . . . . . . . . . . . . . . . . 10.3.3. Error in System Generation with SOFiPLUS 10−4. . . . . . . . . . . . . . 10.3.4. Error during Calculation 10−4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.3.5. Problems with Results 10−5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.4. Support 10−5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.4.1. Support Accessibility 10−5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.4.2. Customer’s Obligation to Cooperate 10−6. . . . . . . . . . . . . . . . . . . . . 10.4.3. Support Request via SOFiSTiK Online Portal 10−7. . . . . . . . . . . . .

Basics SOFiSTiK

v

10.4.4. Support Request out of SSD / TEDDY 10−7. . . . . . . . . . . . . . . . . . . 10.4.5. Create a Diagnostic.xml File 10−8. . . . . . . . . . . . . . . . . . . . . . . . . . . .

11 Additional Information and Help 11−1. . . . . . . . . . . . . . . . . . . . . . . . 11.1. Infoportal 11−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2. CADINP Samples 11−2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.3. Forum 11−3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SOFiSTiK Basics

vi

This page intentionally left blank

Basics SOFiSTiK

1−1Version 2010

1 Introduction.

1.1. SOFiSTiK

The SOFiSTiK AG develops and distributes engineering software with particularemphasis on civil and structural engineering.

The software has been developed following a sofisticated concept, allowing thestandard user to reach a quick and efficient solution to a given task. Despite thisthe possibilities for a specialist with large experience in numerical methods arenot restricted.

The software is made up of a modular structure and provides general availableopen 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 informa-tion about the theoretical backgrounds and descriptions for the input and outputof the programs. We recommend to inform about the respective program modulein 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 aremore detailed described in the respective manual. The input files for theseexamples are to be found in the installation directory SOFiSTiK in the respectivesubdirectories program_name\english.

Furthermore the users have the possibility to get information about many featuresof SOFiSTiK−Software on the home page of the SOFiSTiK AG (www.sofis-tik.com) with the link Infoportal. Detailed examples do not only show the powerof these programs but may be used as templates for your own solutions.

SOFiSTiK Basics

Version 20101−2

Link Infoportal

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

Basics SOFiSTiK

2−1Version 2010

2 How to use SOFiSTiK.

2.1. 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 bygraphical user interfaces, interchange all their information through this database.

SOFiSTiK−Software consists of numerous different modules. For all beginnersthe “SOFiSTiK−Structural−Desktop” SSD is the best choice because it will handlemany of the complex interactions between the modules. There is a separate tu-torial 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 structureand the CADINP−command language as this is the most powerful and the mostbasic access method. An experienced user will never disaccustom himself fromthe flexibility of applying CADINP macros, especially for large complex systems.Especially the possibility to keep all secondary information in comments and for-mulas 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 isvery flexible. The user can always choose the most effective form of input for hispurposes and is only constrained by minimal obligations in sequences of analy-sis. Moreover it is possible to transfer data between different computers and oper-ating systems without difficulty.

SOFiSTiK Basics

Version 20102−2

Basics SOFiSTiK

2−3Version 2010

2.2. Program Modules

2.2.1. Preprocessinginteractive programs:

CrossMAX Graphical input of cross sections with AutoCAD (part of SOFiPLUS)

SOFiPLUS Graphical Input of FE−meshes in AutoCADMONET Graphical input of FE−meshesCOLUMN Generation of input data for columnsFOOTING Graphical input of foundations

(all not described within this manual)

Batch−programs:

AQUA Materials and Cross Sections

SOFiMSHA Import and Export of Finite Elements and Beam Structures

SOFiMSHB Generation of Finite Element Meshes from GeometryDefinitions

SOFiMSHC Geometry modeling and Generation of Finite ElementMeshes

SOFiLOAD Loadgenerator for Finite Elements and Frameworks

TENDON Geometry of Prestressing Tendons

CSM Construction Stage Manager

2.2.2. Analysis ProgramsSTAR2 Statics of Beam Structure Theory of 2nd OrderPFAHL Statics of Three−Dimensional Pile StructuresASE General Static Analysis of Finite Element StructuresHASE Halfspace and other Stiffness ElementsSEPP Statics of Plane Plates and DisksTALPA Statics of Plane or Axisymmetric Geomechanical

StructuresPHYSICA Multiphysics powered by MPS

DYNA Dynamic Analysis

SOFiSTiK Basics

Version 20102−4

ELLA Extended Live Load Analysis

HYDRA Seepage and Thermal Analysis with Finite ElementsAnalysis of thermal problems

2.2.3. Design ProgramsMAXIMA Superposition BDK Lateral Torsional Buckling for Steel Cross Sections

AQB Design of Cross Sections and of Prestressed Concreteand Composite Cross Sections

BEMESS Design of Plates and ShellsWIST Angular Retaining Walls (system and design)

2.2.4. Postprocessinginteractive programs:

WiNGRAF Graphical Representations of Finite Elements andBeam Structures

DBVIEW Selective Printing of Data from the Database(will be integrated in GRAFIX)

Batch−programs:

AQUP Graphical Representation of General Cross SectionsWING Graphical Representations of Finite Elements and

Beam StructuresDBPRIN Print Results from the DatabaseSIR Sectional ResultsDYNR Transient Results and Response SpectraPROT Preparation of Tendon ProtocolsTEXTILE Cutting Pattern Membrane Structures

Basics SOFiSTiK

2−5Version 2010

2.3. User Interface.After the installation of the software the explorer has linked several file extensiontypes 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 (SOFiSTiKStructural 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 filesA double click will open the program TEDDY, with the right mouse but-ton you have access to WPS (run)

SOFiSTiK Basics

Version 20102−6

The extensions .CDB are database filesa double click will open the program Animator, with the right buttonmouse you have access to:

Dbinfo Programmers diagnose toolExport SOFiSTiK ExportGraphic Graphical presentation of dataTendon Graphical input of tendonsUnlock 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 con-tain information about error messages and warnings, statistics, para-meters of the equation system, memory usage and analysis time.

The extensions .ERG are classical output files in text format. Theyhave the similar content as the .PLB, but do not contain pictures.

The extensions .LST are the components making the ERG file. TheLST file always contains the result of the last module and may behelpful for fast error tracking.

The extensions .DBV are documents for the program DBVIEW, theycontain the parameters of certain tabular views on contents of theCDBASE.

GRA The extensions .GRA are CADINP input files of the program WiN-GRAF and can be opened and modified with TEDDY.

Basics SOFiSTiK

2−7Version 2010

2.4. Input Files.The input files are in a free input form in the so−called CADINP−format (seeChapter 5). This is a programmable macro−language which makes very efficientinput handling possible. For a static position there are multiple, even nested filespossible.

The files with the extensions .AQU, .KNO, .ELM, .LAS are files generated byMONET, which are linked to the DAT (input) files. The file .AQU contains materialand cross−sections, .KNO the nodes, .ELM the elements and .LAS the loads.

The extensions .SIR are input files which are generated by the program SIR. Theycan be opened and modified with TEDDY.

The extensions .SOFISTIX are special presentation files of the SDD (SOFiSTiKStructural Desktop). Using these files you can get default inputs in the SSD forselected systems for a further processing.

2.5. Database

For each position of an analysis system one database with a project name andone or more data files are created. The database can be valuable in large projectsand therefore it should be saved via Backup.

In this context the term system is defined as the sum of all parts of a structureor substructure, which interact statically during their lifetime. The programsSOFIMESH or SOFiPLUS generate the analysis system for the structure beinganalyzed. The total number and the type of the elements are thus definitelydefined. However for the analysis a partial system can be used. This is definedby the group number, which is the truncated quotient of the element number di-vided by a group divisor (e.g.1000). The user should keep this structuring in mindfrom the earliest stages of the design.

Boundary conditions and material constants can be modified as desired. Loadcases can be analysed or superimposed by the use of certain modules. Designcan be carried out and results can be presented graphically. All results are savedas the most recent values. The analysis of a load case with modified loads over-writes the previous results. When cross−sections are modified, all the results thatdepend on them (reinforcement, stresses, etc.) are deleted if not specified other-wise.

SOFiSTiK Basics

Version 20102−8

The database is managed by the system CDBASE. Its index sequential structureallows an effective access via a double key. The description of the data is givenvia the file CDBASE.CHM, the subroutines can be obtained by users for program-ming purposes.

A database can be transferred in both ways to and from the AutoCAD based sys-tem 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 andediting 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

Basics SOFiSTiK

2−9Version 2010

After calling the program DBINFO the following menu appears:

a − Access history o − Output mediums − Structure (Eements)l − Loadcasesm − Merge 2nd database b − create a backup

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. Optionss 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, thisonly makes sense when both databases contain the same analysis system. Sucha need exists mainly for very large systems when several colleagues analyze dif-ferent scenarios for the same system.

When running DBINFO project,Z all error flags and all the record locks will beremoved. These result from a program crash for example. The removing of thelocks 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 canchange the parameter CDACCESS=SINGLE. This will deactivate themultitasking possibilities and no record logs are created.

Option d displays content of the database. Option e allows the user to change thecontent of the database. You only should do so on explicit order by a SOFiSTiKsupporter. A description of the content of the data base would be advantageousfor this purpose.

SOFiSTiK Basics

Version 20102−10

2.6. Interactive Modules.The modular structure reflects itself in the conception of the interactive modules.Instead of a single window which changes between input and output views, theuser can open several programs with different windows which exchange mess-ages and have access to the same database. To change between the windowsthere are function keys and icons in the tool bar within TEDDY, WPS, URSULAand 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 print−out includinggraphics

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 ofsystem, loading and results

The program WINGRAF to generate sofisticated true scale drawingsof system, loading and results

The program DBVIEW to create tables with numerical contents of thedatabase and graphic functions. (The program will be integrated intoWINGRAF)

The program MONET for the graphic construction and mesh gener-ation of system and loading

Basics SOFiSTiK

2−11Version 2010

2.7. News

SOFiSTiK programs are under continuous development. The manuals are notprinted therefore on a regular basis, but are packed together with the programsas PDF files. The changes in the programs are gathered in HTML−LOG files, andare 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 data-base (.CDB). The other types of files are:

The files of the SOFiSTiK programs have various extensions which have the fol-lowing meanings:

.EXE Execution program (MS−DOS/Windows)

.DLL Shared dynamic link library (Windows)

.CMD Batch file

.ERR Error file of a program containing all error messages,input records and output text in various languages

.TAB Contains other external data for programs (Tables)

.TAX Contains user specific attitudes .TBB Contains compiled data of the .TAB files.

.HTM Latest changes fileThese files contain the changes to each program since thelast manual, as well as the corrected errors.

.PDF Adobe portable document format (Manuals)

.CHM Compressed HTML help files

.WTM Windows macro file for TEDDY

.DEF Definition file for parameters

.INI Parameter file for design codes

SOFiSTiK Basics

Version 20102−12

The following files result from an analysis:

.DAT Input file, (not mandatory)

.DWG Input file for plan from SOFiPLUS, in which the analysissystem 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 cross−sections 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 Database for MONET

.NBK Backup of database for MONET

.NDA Backup of database for MONET for reorganization

.LST Output files of the individual programs

.ERG Output files of the entire analysis

.PRT Protocol file of the entire analysis

.PLB Result file with text and graphics

.CDB Database, should not normally be deleted.

.CDE Eigenforms of dynamic analysis

.$Dn As well as other files with $ (Windows) or z (Linux) and

.zdn a letter and number. Restart files (e.g. stiffness matrix)may be deleted; however, these files may have to beregenerated later, which can demand significant computing time.

.$0n As well as other files with $ (Windows) or z (Linux) and two

.z0n numbers: Temporary work files that can always bedeleted. Usually these files are deleted by the programitself if it finishes properly. Files with wild numbercombinations in their names are auxiliary files of theoperating system, which can no longer be deleted dueto a warm start of the computer.

Basics SOFiSTiK

2−13Version 2010

.$$$ Auxiliary files under Windows which can be deleted.

.zzz Auxiliary files under Linux which can be deleted.

.#nn Auxiliary files under Windows which can be deleted.

.ynn Auxiliary files under Linux which can be deleted.

.### These are error−log files under Windows which can bedeleted.

.yyy These are error−log files under Linux which can bedeleted.

.SDB Shadow database: This file is usually deleted by closingof all involved programs.

SOFiSTiK Basics

Version 20102−14

2.9. Backup of Data.Last but not least it must be mentioned that all valuable data can be destroyedunder certain circumstances. Beside clumsiness of the user, information on thehard disk can be destroyed due to faulty hardware, operating system faults oreven a program error.

Thus you must regularly make Backup copies using the COPY or BACKUP com-mand, this information you can save to floppies or other media. The basic rule isthat 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 data-base, which is often the result of several weeks of analysis, should be backupedin regular intervals.

Important data is considered to be your created DAT−files as well as the files .SO-FISTIK and the project files .NDB or .DWG. If your CDB contains important in-formation you may create a condensed Backup−version via DBINFO. WithinTEDDY there is a function to delete unimportant files in your project directories(clean up).

Basics SOFiSTiK

2−15Version 2010

2.10. SOFiSTiK Options..

For the SOFiSTiK programs there are three setting menus available for the spe-cific SOFiSTiK settings.

Menu Storage location

SOFiSTiK > User Options Options for the individual PCThese settings are stored in the Regis-try database.

SOFiSTiK > Global Options Superordinate options for all projectsThese settings are stored in a file SO-FiSTiK.DEF in a parent directory,usually this is the SOFiSTiK programsdirectory. **

SOFiSTiK > Project Options Options belonging to the projectThese settings are stored in a file SO-FiSTiK.DEF in the current project di-rectory. ***

** In a network installation it is possible, to store the file SOFiSTiK.DEFinto a parent directory on the network. In this case, an environmentvariable SOFiSTiK = network path has to be set.

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

2.10.1. Language SettingsThere is a difference between the language of the dialogues and the input andoutput language of the files.

The language of the dialogues is stored within the Registry database on the localcomputer and is adjustable under ”SOFiSTiK > User Options”. The program mustbe restarted to activate this change.

SOFiSTiK Basics

Version 20102−16

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

Basics SOFiSTiK

3−1Version 2010

3 Graphical Input SOFiPLUS(−X).

3.1. General Hints

SOFiPLUS(−X) is a CAD−based preprocessor to define structures and loads foranalysis with SOFiSTiK programs. SOFiPLUS can be purchased as a pureadd−on to AutoCAD or included with an integrated AutoCAD ORM engine asSOFiPLUS−X.

The program writes directly into a SOFiSTiK database while generating a resultfile 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. Additionallyyou can find examples and tutorial movies for the individual features at the linkInfoportal at the homepage of the SOFiSTiK AG (www.sofistik.com).

SOFiSTiK Basics

Version 20103−2

3.2.1. Start without the program Structural Desktop (SSD)SOFiPLUS(−X) is started via the Program Manager or from the link on the desk-top. For working with SOFiPLUS(−X) an existing drawing of a structure is usedor the structure is drawn directly. Then a structural system with the appropriatedatabase 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 theprogram 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 desk-top. Starting a new project the dialog box ”SOFiSTiK: System Information” startappears on the screen, because working without a database is not possible. Thekind of preprocessing is set to ”SOFiPLUS(−X) − graphical Preprocessing”.Therefore the part below is filled and additional settings for working with SOFi-PLUS(−X) can be configured.

Basics SOFiSTiK

3−3Version 2010

After closing the dialog box with OK several tasks are inserted in the project treeto the left. By double−clicking the task ”GUI for Model Generation (SOFi-PLUS(−X))” the program SOFiPLUS(−X) is started.

Now the structural system and the loads could be defined. The SOFiSTiK data-base will be generated via the program SOFiMSHC.

To set the default kind of preprocessing to ”SOFiPLUS(−X) − graphical Prepro-cessing” use the global options (pulldown menu SOFiSTiK − Global Options ...).

SOFiSTiK Basics

Version 20103−4

Basics SOFiSTiK

3−5Version 2010

3.3. Structure

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 thesidebar.

To become acquainted with the program SOFiPLUS(−X) you can retrieve anexample project from the Infoportal. Additionally you can find explanations for agraphical input with SOFiPLUS(−X) by means of examples in the SSD tutorial(SSD_TUTORIAL_1.PDF). Training courses − for SOFiPLUS(−X) as well as forthe program SSD − are offered regularly

SOFiSTiK Basics

Version 20103−6


Basics SOFiSTiK

4−1Version 2010

4 SSD − SOFiSTiK Structural Desktop.

4.1. User Interface SSD

The SOFiSTiK Structural Desktop (SSD) represents a uniform user interface forthe total range of SOFiSTiK software. The module controls pre−processing, pro-cessing and post−processing.

A double click on the program icon or a sofistik−file will start the pro-gram TEDDY

The system can be entered graphically with SOFiPLUS(−X) or as parameterizedtext input using TEDDY. The control of the calculation and design process takesplace using dialogue boxes, which are accessed via the task tree.

SOFiSTiK Basics

Version 20104−2

The screen is divided into three main areas.

task tree table area work area

Basics SOFiSTiK

4−3Version 2010

4.2. Basic Work Flow

The SSD is task oriented. The tasks are arranged in groups (e.g. the group ”Sys-tem” contains the tasks for materials, cross sections, geometry, loads and com-bination rules). When creating a new project, the necessary groups and tasks areset by default depending on the chosen problem.

4.2.1. Groups

The computational groups are organized in a tree−structure. This structure canbe changed by the user at any time, as the individual tasks can be dragged to thedesired place with the mouse. The user can remove or insert additional groupsat any time with associated tasks.

Example of a possible group−structureof 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 right−click−menu in the task tree. Theycan be normally inserted at any place within the tree. When you select the com-mand ”Insert Task” with the right mouse−button, the following dialogue with allavailable tasks appears.

SOFiSTiK Basics

Version 20104−4

Basics SOFiSTiK

4−5Version 2010

Task Tree

In the task tree the options are accessed via the right−click−menu which auto-matically adjusts itself to show only those available.

Right click menu in the task treeThe right click menu will provide relevant functions for the selectedtask.

Examples:Process −> Dialogue Edit −> Text Input

(name.dat) Reports −> Result viewer (name.plb)

Table Area

Database information is written in thetable area:

Possible categories:− Geometry− Loads− Results

These results can be copied with right click menu into the clipboard.

Possible format:− Text format− EXCEL format

SOFiSTiK Basics

Version 20104−6

Work Area

The work area displays the ANIMATOR visualisation of the system by default.The work area changes to WinPS during processing to show calculation statusand the TEDDY for further text input prior to analysis. The graphical input with SO-FiPLUS(−X) operates within its own separate window making the best possibleuse of dual monitors.

Basics SOFiSTiK

4−7Version 2010

4.2.3. Template Files name.sofistixFor processing of frequently recurrent standard tasks, the Template files of thetype name.sofistix are provided. General templates are saved in a subdirectoryof the SOFiSTiK directory, for example C:\Programs\SOFiSTiK\2010\ANALY-SIS.25\ SSD−Templates.

Adding User− defined Template Directories

For own Templates, the user can define further template directories.

SOFiSTiK −> User Options −> SSD−Template Path −> (Find−Button )and Add

In this directory, further subdirectories can be created. These subdirectories ap-pear as tabs and template icons. There is only one level of subdirectories avail-able.

SOFiSTiK Basics

Version 20104−8

User Defined Template Files

Any file name.sofistik can be stored into the desired template directory as tem-plate name.sofistix.

All current project settings can be saved as templates including the arrangementand sequence of the tasks. The materials and cross sections are dependent onthe chosen design code. A fixed design code cannot be changed within the pro-ject.

File −> Save Project As Template ...

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

Basics SOFiSTiK

4−9Version 2010

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

SOFiSTiK Basics

Version 20104−10

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”

The desired file name.sofistix is selected and stored under a new data file namewith the button ”Save As ...” into a project directory.

The new file contains all tasks of the template. In addition, the data (for examplecross sections, geometry... etc.) from the template are transferred into the newfile. The data is then immediately ready for calculation.

With ”Templates without Design Code”, the design code can be altered. The ma-terials and cross sections must be checked and amended.

Basics SOFiSTiK

4−11Version 2010

4.3. Structure and Function Mode

4.3.1. Calculation StatusEvery task has its own symbol to show the actual calculation status.

Without calculation Input is written directly into the database

green check mark no calculation required

blue arrow new input data −> calculation required

blue cross old data −> calculation required

red cross error message −> calculation required

green cross warning message −> calculation possiblenecessary

SOFiSTiK Basics

Version 20104−12

4.4. Special Features for Start

For special cases the user may start the program from a command shell by usingthe following command lines:

Parameter Description

+ or ++ Opens the last file or the last but one. Isused without a switch − or / .

−nosingle Starts the application as a separate instance(no single application).

−test A general test flag is set. This is only of in-terest for the developers. Depending on thelevel of development, an individual messagewindow is activated.

−noani When starting the SSD the automatical openingof the AnimatorView is suppressed.

−dat:name When starting the SSD a complete DAT−file iscreated and the SSD window is closed again im-mediately.

Basics SOFiSTiK

5−1Version 2010

5 Input with TEDDY.

5.1. OverviewTEDDY is a powerful control centre as well as an editor, which fully supports andutilises the CADINP language.

navigation window for input

help window

input window

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

SOFiSTiK Basics

Version 20105−2

to a specific command (PDF file) on your screen, without interfering with your edi-tor. The ESC−key will close the help window.

5.2. Support of international character codes (UTF−8)

Starting with Version 2010, the so called UTF8 characters are processed byTEDDY. In HEAD and TEXT−lines now country specific titles, texts and notes canbe entered, which are correctly returned in the result file. The readability of theprintout is thus significantly improved. In particular, for instance, Greek and Cyril-lic characters can be integrated.

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

Basics SOFiSTiK

5−3Version 2010

5.3. Starting the Editor

TEDDY is a windows application and can be started by the standard methods.

a double click on the program icon or a DAT−file will start the programTEDDY


ted [/options] [filename] [line column]

filename:

As a filename you may also enter a + or ++ this will load the last orsecond last file respectively. By using abc*.dat the open file dialoguewill be started with the given pattern match. The following command*.* will select the whole directory.

options:

/sSofistik−Pfad Path for the SOFiSTiK−executables(Change or set the environment variable SOFiSTiK=...)

/1 to /4 will create additional instances of TEDDYThe number will select the colour of theTEDDY−icon.

SOFiSTiK Basics

Version 20105−4

Overview of the possible input commands:



−0 −1 −2 −3 −4 Allows the start of up to 5 instances

(Default: −0).



Line No. The cursor is placed directly into the givenline. The line number must be the last trans-ferred parameter.

5.4. Commands

The most important functions are accessible via the function keys:

F1 help to the current input record (quit with ESC−key)

F2 search

F3 search again

F4 search and replace

F5 mark Block start or end

F6 copy marked block

F7 move marked block

F8 duplicate current line

F9 change window

F12 start analysis

Moreover there are a lot of special keys. These are combinations of the Alt−keyor Ctrl−key and another key pressed simultaneously. These combinations are avery useful feature for an experienced typist used to the touch typing method.Some of the combinations are given below:

Basics SOFiSTiK

5−5Version 2010

5.4.1. Combinations with the Alt−key (selection)

Alt + L marks several lines (block of lines)

Alt + B marks several columns (column block)

Alt + H remove block markers

Alt + R read file as block

Alt + W write (marked) block to a file

Alt + Z copy marked block

5.4.2. Combinations with the Ctrl−key (selection)

Ctrl + A marks all

Ctrl + C copy marked block

Ctrl + V paste marked block

Ctrl + X cut marked block

Ctrl + S save file

Ctrl + Y delete Line

Ctrl + Z undo

5.4.3. Overview of all Ctrl− / Alt−CommandsA complete arrangement of all Ctrl commands, you will find in the TEDDY−helpmenu ”Help > Ctrl commands ....”

If you press the Ctrl−key and the K−key (Ctrl+K) for more than two seconds youwill get also an overview of all the special key combinations:

SOFiSTiK Basics

Version 20105−6

Here one will also find combinations of three keys (Ctrl+K + R) and their counter-parts with the Alt−key (Alt+R).

5.4.4. Example with Column BlockAn 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 withthe values in the column, like generating sequences or calculating the sum of thevalues, just to mention a few.

Basics SOFiSTiK

5−7Version 2010

5.5. Input of Data.

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

PROG AQUAData for the AQUA program

PROG SOFIMSHAData for the SOFIMSHA program

PROG SEPPData for the SEPP program

SOFiSTiK Basics

Version 20105−8

TEDDY is able to recognize a file as an input file by the structure of the very firstline. 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 SOFiSTiKinput file. You may specify other extensions via the option Extras −> File type.

Provided that the file progname.ERR exists, TEDDY can recognize all recordnames and their corresponding commands. The status−line of the window dis-plays the current record name and its commands as well as the name of the mo-dule used and the current input language.

record name list of items module

language

5.6. Help and Interactive Manuals.

5.6.1. Activating the HelpHelp is activated with the F1−key. The page of the manual, matching the currentinput 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 char-acter sequence (_0 German or _1 English) indicating the language. They haveto be available of course.

In a navigation window you will see the table of contents, which allows you to jumpto the theoretical− or the example sections in the manuals. But as soon as TEDDY

Basics SOFiSTiK

5−9Version 2010

becomes the active window again, the help will automatically switch to the currentmanual page.

You may quit help with the Esc−key, but only if TEDDY is the active window. Asan 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 layoutof the manual is optimised for a double sided print out.

5.6.2. Acrobat ReaderFor 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 yourcomputer no alterations are made by the SOFiSTiK setup.

You can also change the size and position of the help window. The best optionis not only a matter of taste but also of the screen resolution. The following optionsare 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 itwill stay in memory and pop up very fast the next time.

SOFiSTiK Basics

Version 20105−10

5.6.3. Creating Your own CommentsIf you want to make annotations within the help files you will need a full versionof 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−Online−Help for more details)

When leaving the PDF−file you should save your changes. The annotations aresaved into the PDF file and may be also seen from the Acrobat Reader. Howeverif 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 anderasable.

Basics SOFiSTiK

5−11Version 2010

5.6.4. Export/Import of Annotations in ManualsBefore loading a new version of the manual − especially when obtaining auto-matic updates − you should save your annotations and reimport them within thenew PDF−file. That’s why the automatic life−update−tool SONAR has several op-tions to deal with the manuals. The intended option is to keep all new manualsin a separate download directory. Then you should copy the plugin from the SO-FiSTiK−CD \statik\win32\extra\ImExAnot.api into the Plug−in directory of yourAcrobat−Installation.

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 Adobe−Export is not so well suited, as it is boundto the page numbers, while our plug−in uses the names of the pages (e.g. Re-cord−names). Thus on a new version with additional inserted pages you will findyour annotations at the originally intended place in most cases.

The annotations will be saved into a file of type FDF (name.FDF). When you havethe new PDF version opened, you may import them via:

When leaving the PDF−file you should save the changes of course.

If you use SONAR to download the newest versions from the Internet, you mayhave the problem to export−import comments for many manuals. That’s whythere is the option file −> batch processing −> SOFiSTiK Comments to do this forall PDF between two directories.

One possibility to manage this properly, is to download the manuals always intoa special download directory, assuring that (only) newer versions will be treatedalways. In a second step (if the file−date of a manual is larger than the last export/import) one has to copy these manuals to a third temporary directory, where theyare 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 totalanalysis. From TEDDY you can start the calculations and call up the pre− andpost−processing modules. To execute these features a tool bar is supplied inTEDDY, which consists of the following icons:

SOFiSTiK Basics

Version 20105−12

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 SOFiSTiK

5−13Version 2010

Data export from CDB

Archive

Clean up

Explorer

Command−Shell

SOFiSTiK Basics

Version 20105−14

5.8. Special Features of SOFiSTiK

In the right−click menu of TEDDY some important commands are put together tosupport the work with SOFiSTiK. The settings in this right−click menu can be cus-tomised by the user with the menu ”Extras > edit macros > SOFiSTiK.wtm”.

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

Basics SOFiSTiK

5−15Version 2010

5.8.1. TEDDY Information CentreInformation about installed programs Help −> Licenseinfo

SOFiSTiK Basics

Version 20105−16

Manuals Help −> SOFiSTiK Documentation

For every SOFiSTiK program there is a LOG file in HTML format. Here all thechanges and enhancements are listed for the respective versions of the pro-grams.. Help −> SOFiSTiK LOG Files

With the program Diagnose all SOFiSTiK−specific settings and resource files arecollected. It is very helpful for installation problems or problems caused by the op-

Basics SOFiSTiK

5−17Version 2010

erating system. (But available only in German)Help −> Diagnostic

SOFiSTiK Basics

Version 20105−18


Basics SOFiSTiK

6−1Version 2010

6 CADINP − Input Language.

The input language CADINP for free input format of data is the result of a furtherdevelopment of a project CADINT, which originated from the Federal Ministry ofResearch and Technology for the study in the CAD area (M.Ahn, K.H.Böckeler,W.Haas / Eingabe Konventionen für CAD−Programme, CAD−Bericht Kfk−CAD39, Kernforschungszentrum Karlsruhe, 1976).

The variation of this format, which was developed by SOFiSTiK, includes severaladditional capabilities. In certain points it therefore has some deviations from theabove mentioned CADINT standard.

The full capability of the language can be achieved in combination with SPSand/or WPS, when functions for block building and parameter substitution areused. CADINP and SPS represent a full programming language for the calcula-tion of problems in structural engineering, which will outdo any guided GUI. Theprocessing occurs in two stages.

• SPS or WPS use a single file or a set of sub−files to create an input file forevery program being used. This is called parsing. During this process glo-bally defined text elements are inserted and larger blocks are inserted orskipped. Strings are addressed with $(name). The strings can be definedor undefined in the input file or the SOFiSTiK−environment. At this stageno calculations have take place, that is why there is a difference, whetherthe string A = ”2+2” is inserted at $(A)*3 or ($(A))*3.

• Each computational program starts its own CADINP processor, whichthen starts the arithmetic calculations. The variables used within CADINPare marked with a # at the beginning. They do not need any brackets andrepresent numbers. They can be converted to text input data whereneeded, especially within comments. However they can only be usedwithin the local scope of the single program.

The combination of these two stages allows the description of a complete analy-sis systems by means of manual calculations and documentation of the analysisassumptions and the resulting computer calculations. This in turn produces acomplete analysis document in the computer.

SOFiSTiK Basics

Version 20106−2

6.1. Definitions and Descriptions

6.1.1. Lines (physical sentences)The input consists of lines. Each line contains up to 255 characters and corre-sponds 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 aname. The records do not have to conform with the line separation.

6.1.3. Separation CharactersThe 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. DataData can be numbers or text (=Literals). Numbers may have a sign and an expo-nent. If an integer number is expected, the given number will be rounded to thenearest integer, e.g.

2 0.04 −.5 3.7E8 −0.5E−3

Texts are arbitrary strings of characters. Only the first four characters are signifi-cant. Text should be delimited by apostrophes if there is danger of confusion withnumbers, 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 ver-sions allowed only the local code−page characters. However the short ident keyswith exactly 4 characters allow only for pure ANSI−characters (i.e. no Umlauts oraccents).

Lower case characters are automatically converted to uppercase characters, aslong as they are not between apostrophes. However a few exceptions are en-forced to upper case (e.g. names of actions) to avoid ambiguites, these will bemarked 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 distin-guished:

Basics SOFiSTiK

6−3Version 2010

• 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 theprogram can handle the literal in that form as intended.

• If the variable has been defined with a literal, this content will be insertedinstead of the variable.

• If the variable has been defined with a value, this value will be formattedand inserted instead of the variable in the literal.

For an optional literal i.e. instead of a number and for variables containing literalsonly 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 #() func-tion with the format as a second parameter i.e. #(#ALPHA,8.3). The integer partof the format selects the number of total characters (8), while the decimal part se-lects the numbers of decimal digits (3). The first argument may be any complexarithmetic expression.

6.2. Input Syntax

6.2.1. Basic Input Format• The input consists of records.

• The input record consists of the record name followed by data in the orderspecified in the input description.

• Each record occupies one input line.

• The record name can be omitted when the record is of the same type asthe preceding one.

• A record can start at any position in a line.

• The data is separated from each other by one or several separation char-acters.

SOFiSTiK Basics

Version 20106−4

6.2.2. Default ValueIf the minus sign (−) is given instead of a data value, the program uses the corre-sponding default value as specified in the programs description.

If less data is entered for some record than its description demands, the corre-sponding 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. RepetitionIf the equal sign (=) is entered in the place of a data value, the program will usethe corresponding value of the preceding record. However this is only possibleif the record name has not been changed.

If two equal signs (==) (with no blank spaces in between!) are entered, all of thevalues in the following records will be the same. Positioning of the preceding re-cord 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/DecrementsIf a double plus or minus (++ or −−) is entered in the place of a data value, theprogram will use the corresponding value of the preceding record incrementedor decremented by 1. This will also work with Literals, Lists and Generation se-quences. However this is only possible if the record name has not been changed.

The increment/decrement characters must be enclosed in separation characters.

Basics SOFiSTiK

6−5Version 2010

6.2.5. CommentsThe comment characters $ , ! or // turns the rest of a line into a comment, whichwill be ignored by the program. All this comment operators should be separatedfrom the comment itself and the input data in the same line with a separation char-acter.

Within a +PROG−line (see SPS) only the $−character is allowed as a commentand it must be separated by blancs. Within a +SYS−command line no commentsare allowed at all.

6.2.6. Record ContinuationA 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 towrite expressions or a list of values extending more than one line.

6.2.7. Record PartitionMore 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. PositioningBy entering a name of an item inside a record, you can provide the value for thatitem regardless of its position.

Example:A record is defined by the items K1 K2 K3 K4 K5. The following input isthen equivalent:

RECORD 1.00 − − 2.00 3.00RECORD 1.00 K4 2.00 3.00RECORD K1 1.00 K4 2.00 K5 3.00RECORD K4 2.00 K1 1.00 K5 3.00

SOFiSTiK Basics

Version 20106−6

6.2.9. Defining TablesThe predefined order of the input data can be altered by entering a record consist-ing only of the names of the items. In this case the following records must not con-tain a record name, as this would reinitialize the sequence of items.

The last example could have also been given as:

RECORD K1 K4 K5 1.00 2.00 3.00

A table definition remains valid until a new record name is entered or the samerecord name is repeated. Inside a table the positioning is still possible even forthose items not defined in the table definition.

The default values can be modified inside the header of a table by following theitem with an equal sign (=) and the new default value without any separation char-acters.

RECORD K1 K2 K5=4 1 2 6 2 5 3 6 −

is equivalent to

RECORD K1 K2 K5 1 2 6 2 5 4 3 6 4

Such a construct is also a nice suitable solution to the problem of ambiguous lit-erals. If a literal value exists (e.g. GRP) for the first item position which is also avalid record name, a change of the sequence and perhaps a default assignmentmay solve this problem without the need to use quotes:

BEAM TO TYPE PA FROM=GRP 1 TEMP 30 2 TEMP 25

Basics SOFiSTiK

6−7Version 2010

6.2.10. Help−RecordA list of the possible record names can be obtained by entering HELP. HELP fol-lowed by a record name prints a list of the items of the record. HELP followed bya record name and an item name will print the allowable input values and para-meters for the corresponding position.

This option is meaningful especially during interactive error finding.

6.2.11. GenerationAn instruction for automatic record generation can be given instead of a datavalue. 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 recordsto be generated. It can be used only once per record, yet in any position insidethe record. The corresponding secondary generation instruction can be definedfor every parameter.

The generation of literals is also possible. The increment is then also consideredas 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 withan accuracy of 0.0001 of the increment, an error message will be displayed.

The other generation instructions of the CADINT−language are not implementedbecause they contradict with the arithmetic expressions.

SOFiSTiK Basics

Version 20106−8

Example:

NODE (1 5 1) 0 (0.5 −0.1)

generates the input records:

NODE 1 0 0.5NODE 2 0 0.4NODE 3 0 0.3NODE 4 0 0.2NODE 5 0 0.1

Example:

REIN (A0.1 D0.4 10.1)

generates the input records:

REIN A0.1REIN B0.2REIN C0.3REIN D0.4

6.2.12. List of ValuesA list of values can be given instead of a generation loop . This is a series of valuesseparated 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 spreadacross multiple lines.

When several lists of values are defined within a single record, their number ofvalues must agree not only with each other, but also with any other defined pri-mary generation.

The maximum number of values per list is limited by an internal amount of mem-ory. A list of 25 values is usually possible.

A list of values can also be built up by fixed literals (LIT). Combinations of numbersand literals or a list of freely defined literals are however not allowed.

Basics SOFiSTiK

6−9Version 2010

6.2.13. LET − and STO − VariablesOne can define variables to be used in the following records. A # must be setbetween the input of LET or STO and the variable name. These variables are des-ignated as up to 16 characters of an alpha−numerical text (1st character has tobe a letter) and an optional index or only by a #sign followed by a simple numericalpositive value. The variables can be used then instead of numbers. The assign-ment of a variable is performed by the record LET# or STO#. This item is followedeither directly by the name of the variable without any separation characters, orafter a separation character by an expression for the variable number. After onemore 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 eachassignment. Names of variables must not contain special characters or collidewith a reserved sequence of characters like (SIN, COS or SQR). Instead of onenumerical value a list of values or a primary generation instruction or a literal maybe entered. In this case the rest of the values is assigned to the variables followingthe 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 providedwith a leading = character. For special cases like the insertion within a literal, as-signment of a default value, conflicts with identical function names, it is possibleto identify a string as a variable name with a leading # sign.

SOFiSTiK Basics

Version 20106−10

Examples of variable assignments:

LET#PI 3.1415 $ Pi is assigned to variable #PILET#TXT ’My Text’ $ Assigning a literalLET#11 4,5,6 $ assigned to variables 11,12,13LET#A 4,5,6 $ 4,5,6 are assigned to A[0:2]LET#A(2) 5.1 $ Assignment to an array elementLET#A(3) 7,8 $ Enlargement by 2 elementsLET#1 =A(1) $ Using second element of arrayLET#1 #(A+1) $ Using second element of array

LET# #10 12.50 $ 12.50 is assigned to variable,$ whose number is stored in #10$ (Indexing)

LET#4 ##10 $ Value of the variable, whose$ number is stored in variable #10,$ is assigned to variable 4

LET#F(100) 0 $ Declaration of an array,LET#F 1,2,3,4,5,6,7 $$ filling via lists11,12,13,14,15,16,17 $$ and consecutive lines21,22,23,24,25,26,27

If a variable is assigned to an expression, the expression is calculated firstand then its value is assigned to the variable.

To print variables for debugging purpose you may use the construct PRT# witha similar syntax for addressing the variable name. The name of the variable is ex-pected without separation characters immediately behind the #. For more com-fort one should use TXB / TXE or <TEXT> within literal text.

Variables with a name may be saved permanently in the database. The commandSTO#name will save the current or specified value of this variable in the data-base, which then can be used by all other programs accessing the database fromthat.

e.g.STO#c 30 $ assignment and storage of the variable

$ in the database

Basics SOFiSTiK

6−11Version 2010

If a save variable should be removed from the database there is the commandDEL#name. For this case it is also allowed to specify wild card characters. Thecommands 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 valuewith the following commands:

RCL#ALL Read all named variablesRCL#name Read one named variable/arrayRCL#name(3) Read one entry of an arrayRCL#name cdbfile Read variable from another CDB data base

Reserved Variable−NamesThere are some reserved Names, which are automatically created by a pro-gramm run. The user may use and redefine those names however within his CA-DINP−data block with new values.

• Variables VERSION(0) and VERSION(1) will be preset with the versionnumber of the Release (dll) and the program itself, allowing to define com-mon input data for multiple versions.

• Variable PI will be preset to 3.141593.

• The arrays of variables GRP_MASS, SCT_MASS and MAT_MASS aswell as GRP_REIN and SCT_REIN are redefined after a print or evaluationof 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 themfollowed by an underline:

• ASE uses the array ASE_ITER as followsASE_ITER(0) = first load case numberASE_ITER(1) = last load case numberASE_ITER(2) = last achieved load factor

• Variables of Array AQB_USAGE will be set by AQB with the usage factorsof 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 testprints and an interactive debug mode. DBG# uses the variable #0, which can not

SOFiSTiK Basics

Version 20106−12

be used for other purpose therefore

DBG#0 No output of intermediate valuesDBG#1 Output of the generated input recordsDBG#2 Additional output of all value

assignmentsDBG#3 Additional output of selected structures

(CDB access)DBG#4 Printout to console stream/windowDBG#8 Input from console stream/window

(interactive mode)DBG# Switch between option 15 and option 0

(=break and continue)and

DBG# −2 Immediate STOP of total program run, although all outstandingTXE−Lines will be printed after the errormessage

6.2.14. Arithmetic Expressions.In place of a numerical value any desired arithmetic expression may be used. Theexpression may contain parentheses, but no separation characters.

The allowable operators are:

+ − Addition, Subtraction* / Multiplication, Division** or ^ 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 oper-ators are according to the mathematical rules.

Basics SOFiSTiK

6−13Version 2010

The following functions are allowed inside an expression:

SIN(x),COS(x),TAN(x) Trigonometric functionsATN(x),ATN(y,x) Arc of tangent x or y/xARC(x) Convert angles to arcusSQR(x) Square rootABS(x) Absolute valueEXP(x) Exponents of eLOG(x) Natural logarithmLGT(x) Base 10 logarithmDIV(x,y),xDIVy,DIV(x/y)Integer part of x/yMOD(x,y),xMODy,MOD(x/y)Division remainder of x/yMIN(x,y,..),MAX(x,y,..)Minimum or Maximum numbersRANDOM(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 exprequals to zero.

Arithmetic expressions may also appear within a list of values or generation in-structions. The functions DEG, GON and RAD may be placed before any argu-ment, but separated from it by a comma. Their definition is kept if an assignementcontains only one of those names (e.g. LET#0 RAD).

Examples:

SIN(30.)+3*COS(45.) oder SIN30+3COS45SIN(RAD,2.435)

100.+MOD(354,32) oder 100+354MOD32

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 isnot integer, but rational, an interpolation between the values of the array will takeplace:

SOFiSTiK Basics

Version 20106−14

LET#A(0) 10.0LET#A(1) 14.0LET#A(2) 16.0LET#A(3) 17.0

LET#B =A(1.3) => #B = 14.6

The same procedure is also available for higher interpolation schemes. Then weneed two arrays of the X and Y values with the same length. These variables arethen connected by a special assignement of a literal as a table definition:

LET#X 0.0,2.0,3.5LET#Y 0.0,100.0,100.0LET#SIG ’TAB(X,Y)’

The expression SIG(1.73) interpolates for this X−value betwen the given Y−va-lues linearly. If higher functions are requested, a third array is needed, giving thederivatives of the function:

LET#DY −,0,−LET#SIG ’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 arespecified at both ends of an interval we have cubic splines as interpolation func-tions.

Variables and Literals:

In case it is required to store text in a variable this may be done with the LET/STOcommand 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 ispossible 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 anyarithmetic expresssionas are also valid of course). A text variable may be readfrom the CDB and it is possible to convert with a LET/STO command a text tonumbers. The following example will save the two numbers in variables #VALT(0)and #VALT(1):

Basics SOFiSTiK

6−15Version 2010

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

6.2.15. FUN − Definition of functionsIf an arithmetic expression is needed more often or the meaning of a variableshould be changed during the run, it is possible to define a function. Such defini-tion is done as a literal according to:

LET#F ’=FUN(var,formulaexpression)’e.g.

LET#F ’=FUN(x,3*#x**3−2*#x**2+5*#x)’LET#1 #F(1.234)

The Literal has to start with the character sequence “=FUN(” , followed by a formalparameter name, followed by an expression containing any variables defined sofar. If the formal parameters name has been defined already, it will not be changedby 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 toappend the input unit explicitly in square brackets. So instead of definig a lengthin 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 availablefor those items selected for this option. These are identified in the manual with a[*] in the column named dimension.

SOFiSTiK Basics

Version 20106−16

6.2.17. LOOP,ENDLOOP − Loops and JumpsThe most powerful form of generation is achieved through loops. This formcorresponds to the FORTRAN DO−Loops or to the FOR NEXT loops of BASIC.The loop is initiated by the record LOOP and terminated by the record EN-DLOOP. A loop is executed as many times as determined by the number followingLOOP. It may also be terminated if the expression following ENDLOOP becomeszero or negative. If the name of a variable is given instead of the number after theLOOP, 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 256lines 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 appendedto the LOOP keyword. The index starts counting at zero. The variable may bechanged within the loop, but it will be restored after evaluation of the terminatingcondition in each cycle.

Example: Generation of nodes and springs on a semicircle at a distanceof 30 degrees.

LET#1 1 , LET#2 0.LOOP 7NODE #1 COS(#2) SIN(#2)SPRI #1 #1 DX COS(#2) DY SIN(#2) CP 1.E5LET#1 #1+1LET#2 #2+30.ENDLOOP

Instead of LOOP 7 / ENDLOOP you could use LOOP / ENDLOOP #2<=180. Withan endloop condition one can leave a loop prematurely.

Example for two−level generation:

LOOP#1 3ADEF #1+1

Basics SOFiSTiK

6−17Version 2010

LOOP 2 ; BDIV 0.5 #1+1 ; 0.2 1 ; ENDLOOPENDLOOP

creates:

ADEF 1 ; BDIV 0.5 1 ; 0.2 1 ; 0.5 1 ; 0.2 1ADEF 2 ; BDIV 0.5 2 ; 0.2 1 ; 0.5 2 ; 0.2 1ADEF 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 givingonly the name of the array (without the # ):

LET#A 10,22,34,55,76,83LOOP#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 vari-able, where the value of 0 is obtained if the variable does not exist:

LOOP#NUM DEF(A) ; ENDLOOP

SOFiSTiK Basics

Version 20106−18

6.2.18. IF − Logical ConditionsConditional blocks are an important element of every programming language.The execution of jumps (go to) is not possible within CADINP as it is proven tobe able to solve any problem without this feature. The conditional block is ex-ecuted if the expression following the IF is greater than zero. You might want touse 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/−1IF #1

These lines are input when #1 > 0...ELSE

These lines are input when #1 < 0 or = 0...ENDIF

IF #1==12These 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 additionalELSEIF statements:

if (Condition_1)....

elseif (Condition_2)....

elseif (Condition_3)....

else....

endif

Basics SOFiSTiK

6−19Version 2010

Example:

IF (#A<0.3) $ condition 1 LET#VALUE 0.50ELSEIF(#A>1.0) $ or condition 2 LET#VALUE 0.70ELSE LET#VALUE 0.50+0.20*(#A−0.3) $ else this valueENDIF

A

0.3 1.0

0.5

0.7

VALUE

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

6.2.19. @CDB − Selection of a CDBASECADINP allows the access to data of any SOFiSTiK−Database. Of course youneed a description of the contents of the database (cdbase.chm). The syntax hasthree parts. The @CDB selects the file name of the data base:

@CDB filename

selects an arbitrary database filename.CDB. Default is the actual projectdatabase. An explicit definition of this database is however not allowed.

All data within the CDB consists of multiple records with identical struc-tures organised within different 64−Bit indices KWH/KWL. In general eachdata record has a part containing integer numbers and a second one con-taining the floating point data. The description of all structures is given forthe user within the file CBBASE.CHM and for the programs within the fileCDBASE.CDB.

SOFiSTiK Basics

Version 20106−20

6.2.20. @KEY − Access to the CDBASE

@KEY KWH KWL [SEL1 SEL2 SEL3 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. loadcase or section number). Values KWL and SEL1 to SEL6 are preset auto-matically.

For special purpose an optional filtering rule given by up to 6 integer or 4character key values SEL1 to SEL6 may be specified. Key values whichare not important or will be defined with the access−function have to bespecified as −1. The keys correspond to the integer positions of the data-base.

The record index has to exist in the database. You will get an error other-wise. The read position is set to the beginning of the index. If you specifyfor IERR a number of a variable (for example 999), its value will be set toa positive value if the given key exists. If the variable #CDB_IER has beendefined, it will contain the same value.

6.2.21. @() − Access to the CDBASEA record is accessed by the use of an arithmetic function @() as special case ofan arithmetic expression:

@(position+offset) or @(no,position+offset)

reads from the database the next record, which passes the @KEY−filterwhich is modified for the second case by ”no” at the position of the last de-fined 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 thelast selection value of the filter. The value 0 and negative values will there-fore yield the integer values within the selection keys. An access to theindex of an array can be done via ”offset”.

The access function will start at the current position. If you access a valuewith the same or a lower position, CDBASE will read the next record. If theend−of−file condition is encountered an error will occur if you have usedthe form @(position), while for @(nr,position) a loop is used once and thefunction jumps to the beginning.

Basics SOFiSTiK

6−21Version 2010

You may also specify two state variables. If these variables have been de-fined non negative, the result values will be saved there and error mess-ages will not appear:

• CDB_LEN for the actual length of the record

• CDB_IER for the error−flag (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 Iy−value of cross section 5 from the actual project−data-base, you enter:

@KEY SECT_EFF 5LET#5 @(IY)

Example 2:

To use the support forces of node 101 and 102 of load case 12 as loadsyou enter:

@CDB project1@KEY N_DISP 12LOAD 1 PX @(101,PX) PY @(101,PY)LOAD 2 PX @(102,PX) PY @(102,PY)

Example 3:

To use shell forces of the nodes 101 and 102 of group 2 of load case 12you enter:

@CDB project1@KEY QUAD_NFO 12 2 $ Selector Group 2LET#101 @(101,mxx) $ moment m−xxLET#102 @(102,myy) $ moment m−yy

Example 4:

To get all support forces of nodes with last digit 0 as loads you may enter:

SOFiSTiK Basics

Version 20106−22

@CDB project1@KEY N_DISP 12LET#CDB_IER 0LOOP $ ALL RECORDSLET#10 @NR,@PX,@PY,@PZIF (#CDB_IER<2)&(#10<>0) $ END OR HEADDER IF 0==MOD(#10,10) $ LAST DIGIT 0 LOAD #10 PX #11 #12 #13 ENDIFENDIFENDLOOP #CDB_IER<2 $ TO TERMINATE THE LOOP

Example 5:

To get the section number of the beam 101 (As we have to read two differ-ent cases alternate, we can not use the predefined literals):

LET#CDB_IER 0@CDB projekt1@KEY 100 0 −1 −1 −1 −1 $ 4 Integer−KeysLET#NR 0LOOP $ ALL recordsLET#10 @(−3),@(−2) $ 1. and 2. IntegerIF #10 ; LET#NR #10 $ New BEAMELSE $ section of beam IF #NR==101 LET#Q #11 ENDIFENDIFENDLOOP #CDB_IER<2 $ TO TERMINATE THE LOOP

Basics SOFiSTiK

6−23Version 2010

Example 6:

For text elements saved in the database special caution has to be payedfor the fact that we have to distinguish between pure ASCII−text [chr] andunicode−text [str]. In the following the first part reads the CHR−Name of thedesign code with elementary functions, while the second part reading theunicode designation of the material has to use the names of the cdba-se.chm:

@KEY 10 1 $ READ DESIGN CODE AND ACTIONSlet#NT LIT(@7,@8,@9,@10) $ DESIGNATION OF CODElet#A1 LIT(@2) $ NAME OF ACTIONSlet#A2 LIT(@2)let#A3 LIT(@2)

@KEY MAT 1LET#MATTXT LIT(@TITLE)

SOFiSTiK Basics

Version 20106−24

6.3. General Records.

The input consists of blocks. Each input block usually begins with the HEAD linesand ends with an END record. Some programs allow the input of more than oneblock. The analysis is ended in those cases when an empty block (END/END) isfound.

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 valueswith different possibilities, that are selected via PAGE UNII. LIT is given foritems allowing only preddefined literals. Litnn defines input, which can ac-cept free text of up to nn characters. LITnn defines literals which are enfor-ced to upper case.

• The last column shows the default values. Here, the ”−” character meansthat no default value exists, and that the parameter itself is not necessary.On the contrary, a ”!” means that a value must definitely be specified. Fi-nally, a ”*” means that the default values depend on various conditionswhich are explained in the text.

Some records have the same meaning in all of the programs. These are:

Basics SOFiSTiK

6−25Version 2010

6.3.1. HEAD− Title Lines

ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

HEAD

Item Description Unit Default

Title line LIT72 −

Up to 10 title lines can be defined. The first one is reserved for the structure de-scription and can only be defined in the programs AQUA, SOFiMSHA/B/C andin templates of the SOFiSTiK series. This line is imported by all other modulesfrom the database, thus it can not be changed. The rest of the lines can freely bedefined by entering the record HEAD followed by a separation character and anydesired 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 linesmay be specified in SOFiSTiK.DEF via the variables KOPF1, KOPF2 andKOPF3.

6.3.2. END − End of an Input Block

ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

END


End of input or of an input block − −

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

SOFiSTiK Basics

Version 20106−26

6.3.3. TXB − Introducing Text

ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

TXB


Introductory text LIT72 −

6.3.4. TXE − Concluding TextÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

TXE


Closing text LIT72 −

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>. How-ever a picture is not allowed within a <TEXT> ... </TEXT> block.

The TXB/TXE − lines should not be entered between apostrophes. Within the textvariables in the form of #(variable,dd) will be replaced by their current value usingthe format dd.

HTML components may be used within the text. A component starts with a < notfollowed by a blank or another < . Known components will be interpreted, un-known will be discarded. SOFiSTiK programs know about (others will be dis-carded):

<FF> New Page

<LF> Blank Line

 .... Bold

 .... Italic

 .... Underlining

Basics SOFiSTiK

6−27Version 2010

6.3.5. <TEXT> − Text block


<TEXT>


Header of a text block LIT72 −

6.3.6. </TEXT> − End of a text blockÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

</TEXT>


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 willbe appended to the region selected by the last TXB or TXE command. The Textfollowing 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 valuewith a format of “###.##”(total width.decimal digits)Format=6 reserves 6 characters wideFormat=−6 places left adjusted

<EDIT:name,List=str1,str2,str3>$(name)</EDIT>Editable Reference on Parameter valuewith a list box of allowed values

<EDIT:name,List=str1,str2,str3,Update=Yes>$(name)</EDIT>Enforces an update of the templateimmediately after input of data

SOFiSTiK Basics

Version 20106−28

6.3.7. ECHO − Output Control


ECHO


OPT Echo optionThis parameter defines a set of output orcomputing options, to which the recordECHO applies. The actual list of the poss-ible options can be found in the correspon-ding manual.

FULL stands for all output options.

LIT FULL

VAL −1 or OFF no computation 0 or NO no output 1 or YES normal output 2 or FULL extended output 3 or EXTR extreme output

LIT FULL

At the beginning of the program all options for new results are preset to 1. Theoutput parameter for already computed values (e.g. nodal coordinates in analysisprograms) is set to 0. By entering ECHO NODE you can for example assign thevalue FULL to the option NODE. Therefore the default value for VAL will only beactivated if an ECHO record for this option is given. The exact effect of all optionscan be found in the output description of the individual manuals. You should gen-erally note that the shortest possible output is achieved by YES, while a rich out-put is obtained by FULL. By EXTR one achieves the output of values, which areeither useful in further computational steps or can use up a lot of paper. Thus, useof this value should be made with care.

If the user wants to prevent the output of certain results, he must deactivate themexplicitly by NO. If for example one only wants the option REAC set, one mustenter:

ECHO FULL NOECHO REAC

Basics SOFiSTiK

6−29Version 2010

6.3.8. PAGE − Control of Input/Output


PAGE


FIRS

LINEMARG

Number of the first page of the outputNegative entries turn page numbering offNumber of lines per pageColumn number for left margin

−

−−

*

**

LANO

LANI

Output language, if implemented0 German1 English2 French3 Spanish

Input language, if implemented0 German1 English

−

−

*

*

UNIOUNII

System of units for outputSystem of units for input See explanations

−−

**

FORM Format of page header0 single line header1 multiline header2 ZTVK with graphic char. 3 ZTVK without graphic char.4 short header

− *

PRIL Printout level in the output file−2 error messages only−1 warnings as well 0 additional information 1 computing times as well

− 0

PAG Identification of page(e.g. “page II/”

LIT12 *

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

SOFiSTiK Basics

Version 20106−30

meters except the languages and units may be defined in URSULA at the timeof 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.0−97) 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 Page : 9012 Newtown * 12, Software drive, Tel.08144/2725 11 AQUA − General Cross Sections ( 6087) 25.05.95 Title of structure (1st and all further HEAD lines)

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.0−95 Dr.−Eng.Charly Brown page 2 Title of structure (1st head line) date 25.05.95

In the ZTVK Version only the first 48 characters of header lines are used. Thepersistent name of the company can be changed only by SOFiSTiK. However itis possible to change the name for a specific project within the SOFiSTiK−Envi-ronment.

The SOFiSTiK programs strive to present the output in the most suitable engin-eering units. The dimensions used in the database are expressed in SI−units kN,

Basics SOFiSTiK

6−31Version 2010

m, sec. However, other units can also be used for input and output (e.g. N, mmor cm2) as well as a different number of decimals.

The control is implemented through the input parameters UNIA and UNIE. Theconversion of all programs was extensive. It can not be guaranteed therefore thatthis value is used in all subdomains of the programs too. For reasons of con-sistency a change of the units in the input was implemented very cautiously.

Values are composed as grp*8+sgrp (compare SOFISTIK.DIM):

grp 0 modified SI−System(kN,m,MPa) 1 US−System (kip, inch, ksi etc) 2 metric system (N, mm etc.)

sgrp 0 = Standard units or dynamic units 1 = General structural engineering (e.g. cm instead of m) 2 = Steel construction, (e.g. mm instead of m) 3 = Bridge construction, (e.g. MN instead of kN) 4 = Soil Mechanics (e.g. MN instead of kN) 5 = Hydrology 6 = Mechanical engineering (e.g. N instead of kN)

In the file SOFISTIK.DIM all definitions are filed. Under column 7 you can set yourown values. As the file is complemented by SOFiSTiK from time to time, it mightbe more reasonable to ask SOFiSTiK for modifications.

The conversion to US−units follows a convention from 1 July 1959 which has uni-fied American and British definitions:

1 inch = 0.0254 m (precisely!)1 yard= 0.9144 m1 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 CADINPcommand HELP you can enquire the actual dimensions of the input.

SOFiSTiK Basics

Version 20106−32

6.3.9. SIZE − Graphic Format


SIZE


TYPE

SC

WH

Paper sizePositive value landscape formatNegative value portrait format

Scale0 format filling* engineering scale, best pos−

sible for filling the page

Paper widthPaper height

−

−

cmcm

−URS

*

**

MARG Draws a borderNO draws an inner border + scale

here W and H define the sizeof the area to be drawn at(for single sheet plotters andlaser printers)

YES draws a free border aroundthe drawing W and H definethe size of the paper (2cmmargin, otherwise .5cm)

FULL an additional border to cut thedrawing at the outer paperlimits is drawn (for drumplotters)

LIT FULL

FORM Form of the borderSTAN standard frame ZTVK ZTVK−88 frame

LIT *

Basics SOFiSTiK

6−33Version 2010

This record appears within all programs having a graphical output. It defines theoutput format. In general, there are two variations of the task.

• The user selects the paper format either implicitly using TYPE or explicitlyby the width W and the height H. The program can set the scale itself bypicking the largest possible scale with the common values of 1:1, 1:2 and1:5 or their multiples. An explicit setting of the scale SC will be used, iftechnically feasible. Setting SC to 0 results in the largest possible drawingregardless of the scale.

• The user specifies the scale and by setting W and/or H to zero the appropri-ate paper size is automatically chosen. If only one of the two values is setto zero, then the drawing size will be automatically calculated to fit in thesecond 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 for-mat for Hewlett−Packard Plotters instead of the DIN sizes. In this case a frameis created around the picture using the inputs of FORM and MARG. This picturewill printed with program URSULA in exactly this form. In the case of URS orP001...P999 a picture without a frame is created. Then the frame is drawing fromprogram URSULA before printing. URS uses the current URSULA profile. P... se-lects a profile number predetermined with URSULA. A preceding minus sign se-lects the portrait orientation:

URS,−URS The maximum size usable within URSULAP001...P999 The size usable within URSULA from a profile number

A,−A ANSI Paper A (11 x 8.5 inch)B,−B ANSI Paper B (17 x 11 inch)C,−C ANSI Paper C (22 x 17 inch)D,−D ANSI Paper D (34 x 22 inch)

HPA,−HPA Hewlett Packard Paper A (259 x 199 mm)HPB,−HPB Hewlett Packard Paper B (416 x 259 mm)HPC,−HPC Hewlett Packard Paper C (529 x 378 mm)HPD,−HPD Hewlett Packard Paper D (809 x 528 mm)

HP4,−HP4 Hewlett Packard Paper 4 (276 x 193 mm)HP3,−HP3 Hewlett Packard Paper 3 (404 x 276 mm)HP2,−HP2 Hewlett Packard Paper 2 (564 x 366 mm)HP1,−HP1 Hewlett Packard Paper 1 (787 x 564 mm)

SOFiSTiK Basics

Version 20106−34

WIN,−WIN Paper size of current WINDOWS printerMP,−MP Matrix printers with 8 x 12 inch (200 x 287 mm)LP,−LP Laser printers with A4 paper (198.4 x 280 mm)MPW Wider Matrix−printers 14 x 12 inch paper

For these formats the default is MARG NO.

Basics SOFiSTiK

6−35Version 2010

6.4. Generation of Pictures

With the following records true scale sketches may be inserted within the com-ments before or after the analysis. The classical GKS−primitives Polyline, Poly-marker, fill area and text are available. Further there are the generalized Drawingprimitive and a special command to measure distances which provides extendedlabelling possibilities.

6.4.1. <PICT> − Start of a picture


<PICT>


XCMYCMTEXT

Horizontal sizeVertical sizeHeading of picture

cmcm

Lit64

**−

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. GNT − Scale of a pictureÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

GNT


NOSCXMINYMINXMAXYMAXWXMIWYMIWXMAWYMA

Number of transformationDesired ScaleWindow of user−coordinates

Window of workstation (paper space)

−−****

cmcmcmcm

*−−−−−0*0*

A transformation is selected (only NO given) or defined with this record. The pro-gram will automatically select an uniform scaling in all directions. If the userwishes different scalings in X and Y−direction. he has to specify SC < 0 and allfour coordinates of the window. GKS supports three different transformations.

SOFiSTiK Basics

Version 20106−36

6.4.3. GPL − Polyline


GPL


X1Y1X2Y2....X16Y16

Coordinates of Polygon

(Alternate definition of polygons is via mul-tiple records each containing only onesingle vertex X1,Y1. This allows the defini-tion of up to 255 vertices)

****...**

!!

X1Y1...

X15Y15

6.4.4. GPM − PolymarkerÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

GPM


X1Y1X2Y2....X16Y16

Coordinates of Polymarker locations ****...**

!!

X1Y1...

X15Y15

6.4.5. GFA − Fill Area

ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

GFA


X1Y1X2Y2....X16Y16

Coordinates of Fill area

(Alternate definition of polygons is via mul-tiple records each containing only onesingle vertex X1,Y1. This allows the defini-tion of up to 255 vertices)

****...**

!!

X1Y1...

X15Y15

Basics SOFiSTiK

6−37Version 2010

6.4.6. GGDP − Generalized DrawingPrimitive


GGDP


TYPE

X1Y1X2Y2....X15Y15

Type of elementCIRC Full circleARC circular arcVECT centred vectorsVEC1 starting vectorsVEC2 ending vectors

Coordinates orIncrements of coordinates of element

LIT

****

....**

CIRC

!!!!

....−−

The GGDP is a method provided by GKS to create more complex primitives. WithSOFiSTiK these are:

CIRC A full circle with centre at (X1,Y1) and a point on the periphery(X2,Y2). OPT is not used.

RC A circular arc with centre at (X1,Y1) and a periphery from point(X2,Y2) to (X3,Y3). OPT is not used.

VECT A single vector at point (X1,Y1) with the directional components(X2,Y2) or an array of vectors extending along the base line from P1to P3 to P5 etc in the direction P2, P4 P6 etc. VECT will draw thevectors with its centre at the baseline, while VEC1 will put the startingpoint and VEC2 will use the end point with the arrow head at the base-line.

SOFiSTiK Basics

Version 20106−38

6.4.7. GTXT − Text Label


GTXT


XYTEXTVALDIMND

Coordinates of insertion point

Textnumeric valueDimensionNumber of digits

**−*−−

!!−−1*

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

6.4.8. GSCA − DimensioningÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

GSCA


X1Y1X2Y2TEXTVALDIMND

Coordinates of first point

Coordinates of second point

TextNumeric valueDimensionNumber of digits

****−*−−

!!−−1*

GSCA is a special form of labelling. A dimensioning line will be drawn and a textwill be written at the line. The default of the text is the distance between the twopoints, but it may be specified as explicit number and/or a given text. The com-bination of the default distance with a given text requires the text to end with anequal “=” sign. For the shown value a conversion and format according to the SO-FISTIK.DIM may be selected.

Basics SOFiSTiK

6−39Version 2010

6.5. Attributes of Graphic Representations

The drawing elements Line, Mark, Text and Area can have various attributes. Theuser usually specifies all the attributes within the programs with graphical outputby entering bundled numbers. These are constructed according to the followingexpression:

ind = 1000 ⋅ col + 100 ⋅ ibr + ityp

For Windows programs different palettes are foreseen for screens with bright ordark background as well as monochrome or coloured printers. You can changethese definitions via URSULA Options in the Registry for all programs.

The following CADINP−records are only available within the picture definitions<PICT> ... </PICT>. The comments and descriptions of the parameters are validhowever for all other graphical programs as well.

SOFiSTiK Basics

Version 20106−40

6.5.1. GCOL − Colour Selection


GCOL


COLRGB

Pen number or colour nameRed componentGreen componentBlue component

−−−−

1−−−

GCOL selects the colour for all primitives. For COL you have the choice betweenone 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 itsRGB−components.

col = Colour Index 0 = backgroundSTAN 1 = black or white (Pen 1)RED 2 = red (Pen 2)GREE 3 = green (Pen 3)BLUE 4 = blue (Pen 4)YELL 5 = yellow (Pen 5)MAGE 6 = magenta (Pen 6)CYAN 7 = cyan (Pen 7)BROW 8 = brown (Pen 8)

Basics SOFiSTiK

6−41Version 2010

6.5.2. GPLI − Polyline Attributes


GPLI


INDCOLTYPE

WIDTSCAT

Bundled SOFiSTiK−IndexColour (as with GCOL)Line type

SOLI solidDASH dashedDOT dottedDDOT dash−dottedNDAS narrow dashedNDOT narrow dottedNDDO narrow dash dottedWDAS wide dashedWDOT wide dottedWDDO wide dash−dotted

Width factor of lineStyle of dimensioning GSCA

1 inclined small lines2 small circles3 arrow heads

−−/LITLIT

−−

1−−

−2

For Polylines holds for the bundled index:

ind = 1000 ⋅ col + 100 ⋅ widt + type

widt = Line thickness factor 0 = normal thickness1 = thickness times 1.42 = thickness times 2.03 = thickness times 2.84 = thickness times 4.05 = thickness times 5.6etc.

type = line style 1 = continuous2 = medium dashed3 = medium dotted4 = medium dotted dashed5 = tightly dashed

SOFiSTiK Basics

Version 20106−42

6 = tightly dotted7 = tightly dotted dashed8 = sparsely dashed9 = sparsely dotted10 = sparsely dotted dash

Basics SOFiSTiK

6−43Version 2010

6.5.3. GPMI − Polymarker Attributes


GPMI


INDCOLTYPE

SIZE

Bundled SOFiSTiK−IndexColour (as with GCOL)Marker type (Number or Literal)

. + * o XScale factor

−−/LITLIT

−

1−−

−

For Polymarkers hold:

ind = 1000 ⋅ col + 100 ⋅ size + type

size = marker size 0 = normal size1 = size times 1.42 = size times 2.03 = size times 2.84 = size times 4.05 = size times 5.6etc.

type = Mark type 1 = . Point2 = + Plus3 = * Star4 = o Circle5 = x Cross

SOFiSTiK Basics

Version 20106−44

6.5.4. GTXI − Text Attributes


GTXI


INDCOLHBXBYHALI

VALI

PATH

EXPASPACFONT

Bundled SOFiSTiK−IndexColour (as with GCOL)Text heightWriting direction

Horizontal alignmentNORM default of PATHLEFT aligned to the leftCENT centredRIGH aligned to the right

Vertical alignmentNORM default of PATHTOP top of cellCAP top of charactersHALF centre lineBASE writing lineBOTT lower bottom line

Writing directionRIGH to the rightLEFT to the leftUP upwardsDOWN downwards

Expansion factorAdditional spacingFont number

−−/LITcm−−

LIT

LIT

LIT

−−−

1−−10

NORM

NORM

RIGH

1.00.0−

For text the following hold for the bundled index:

ind = 1000 ⋅ col + font

font = Character style installation dependent

Basics SOFiSTiK

6−45Version 2010

6.5.5. GFAI − Fill Area Attributes


GFAI


INDCOLSTYL

TYPE

Bundled SOFiSTiK−IndexColour (as with GCOL)Fill area Style

HOLL HollowSOLI SolidPATT PatternHATC HatchBPAT Pattern with boundaryBHAT Hatch with boundary

Style index

−−/LITLIT

−

1−−

−

For areas (Fill Area) for the bundled index holds:

ind = 1000 ⋅ col + 100 ⋅ styl + type

ibr = Fill Area Style 0 = hollow (only boundary drawn)1 = solid (entire area filled)2 = pattern3 = hatch

type = Fill Area Style Index (only styl =2/3)

The effect of the parameter type is device dependent. Classical vector plotters forexample cannot represent any bit patterns. Pattern 1 corresponds to completelyblank, whereas pattern 2 usually corresponds to a uniform sparse shading, whichgets more dense by increasing numbers. Special patterns are reserved fromtype=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 = vertical / horizontal / vertical+horizontal4 / 5 / 6 = diagonal +45 deg / −45 deg / +45 and −45 deg7−12 = as 1 to 6 dashed13−24 = as 1 to 12 with larger scale25,26 = reinforced concrete27 = earth

SOFiSTiK Basics

Version 20106−46

6.6. Insertion of a Picture

6.6.1. <LINK> − Insertion of a PictureÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

<LINK>


filename.bmp LIT72 −

Pictures with BMP−format can be inserted with <Link> in input files and templa-tes.

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>.

Basics SOFiSTiK

6−47Version 2010

6.7. Parametric Input.

The current version of the input language CADINP allows the definition of stan-dard 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 cross−sectionalarea of the bars. An input for SOFIMSHA could be defined as follows:

HEAD TRUSS$LET#1 12.40 $ SPAN WIDTHLET#2 2.30 $ HEIGHT$NODE 1 0 0 PP (2 4 1) (#1/4 #1/4) 0 5 #1 0 PPNODE 6 #1/4 −#2/2 7 #1/2 −#2 8 3*#1/4 −#2/2TRUS (1 4 1) (1 1) (2 1) NCS 1TRUS 5 1 6 NCS 1 6 6 7 == ; 7 7 8 == ; 8 8 5 ==TRUS (11 13 1) (2 1) (6 1) NCS 2TRUS (14 15 1) (6 2) 3 NCS 2END

More powerful data generation is available using loops. For example, the follow-ing input allows the generation of a series of nodes on a hyperbolic arc:

SOFiSTiK Basics

Version 20106−48

PROG SOFIMSHAHEAD Cooling Tower$ Meridian Hyperbolic equation (r/r0)**2−((z−z0)/zz)**2 = 1$ (r1/r0)**2−(−z0/zz)**2 = 1 => (1/zz)**2$ (r2/r0)**2−((h−z0)/zz)**2 = 1$ parameter:sto#H 160.0 $ Total Heightsto#R0 30.0 $ smallest radiussto#R1 55.0 $ Radius at bottomsto#R2 35.0 $ Radius at toplet#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)**2−1.0)let#m 16 $ subdivision in heightTXB Generation of a hyperbolic cooling towerTXB height radiusTXB 0.0 #(r1,9.1)TXB #(z0,9.1) #(r0,9.1)TXB #(h,8.1) #(r2,9.1)TXBTXB Parameter zz of hyperbolic equation = #(zz,9.3)$let#2 #H/#m $ delta−zLOOP#1 #m+1 ; let#z #1*#2 NODE #1*50+1 #r0*sqr(1.+((#z−#z0)/#zz)**2) 0.0 #zENDLOOP

For the beginner these inputs are likely to be confusing, however, this is a verypowerful possibility which allows to automize frequently happening calculations.Many macros have developed from simple beginnings.

Basics SOFiSTiK

6−49Version 2010

6.8. Compatibility of Data files

Text based input data is suited to be used for long term storage of data, better thanany proprietary binary format. Unfortunately the input syntax is changed sometimes, SOFiSTiK has to consider the readability of the manual, the catch of dataerrors and the compatibility of the data records. Thus we have established the fol-lowing guidelines:

• Input records will be extended most likely at the end of the structure, butif an entry fits in better at an other position (e.g. third coordinate added) itwill be inserted. Especially designations will remain the last entry in mostcases. Thus the user should use the names of the item as a prefix for allextended data, eg.:

NODE 100 10.25 20.00 24.00 FIX PZFor larger data volumes the use of a table is always favourable, the use ofexplicit standard items ’−’ should be avoided. For exported data the dele-tion 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. Althoughwe try to catch as many old data definitions (eg. mm instead of m), the usershould control his data in those cases thoroughly. There are also somecases where a possible literal has the same name as an item or recordname. 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. Thismay be triggered by change of the design codes, a better programminglogic or the demands of our customers. There is no golden way. If one spec-ifies only the minimum range of values, one may reuse the data more eas-ily, but it may happen that a new release will produce different results. Thedefault to select national dependant parameters depending on the settingsof the operating system is a nice feature, but it may create different resultson different computers and should be avoided therefore.

SOFiSTiK Basics

Version 20106−50


Basics SOFiSTiK

7−1Version 2010

7 DEF − Environment Variables.

A lot of parameters for SOFiSTiK programs are defined by the environment vari-ables. A variable has a name usually in capital letters and a string, which can beused 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 theoperating system (My Computer−>Properties−>Extended). In a CMD−Box thisis done via:

SET parameter=Value

In UNIX it is necessary to use shell−commands like:

export parameter

parameter=value Bash, Bourne and Korn shell

setenv parameter value C−shell

As many of these parameters are only needed for individual programs, it makessense to keep these definitions in a configuration file. For SOFiSTiK programsthis file is

SOFISTIK.DEF

In this file all variables for SOFiSTiK−Environment as well as any definitions ofinput macros can be stored (see Chapter 8.2.):

e.g. SOFISTIK_C=49 GRAFSIZE=SIZE −HP 0 HEAD1=New Building Insurance−Company STDMAT=BETO 1 B 35 ; STAH 2 BST 500

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

SOFiSTiK Basics

Version 20107−2

The following table contains the currently known/used values:

Variable Parameters (separated by comma)

possible values

SOFISTiK_NAME alternate user name

SOFISTiK_C nation (International Telefon code)

00 = Generic Europe 01 = United states 49 = Germany 43 = Austria 41 = Switzerland 44 = Great Britain 81 = Nippon 86 = China 91 = India

30 = Greece 31 = Netherlands 32 = Belgium 33 = France 34 = Spain 45 = Danmark 46 = Sweden 47 = Norway 39 = Italy 351 = Portugal352 = Luxembourg353 = Ireland358 = Suomi/Finland

ch_set(character set of computer)

−2 = utf8

Input language 0 = German 1 = English

SOFISTiK_A Headder type in printout 0 = one line 1 = multiple lines 2 = ZTVK grafical 3 = ZTVK standard chars

language of output 0 = deutsch 1 = englisch 2 = französisch 3 = spanisch

level of messages −3 = nothing at all −2 = only error messages −1 = errors and warnings 0 = statistics 1 = computing times

Units of output see SOFISTIK.DIM

Basics SOFiSTiK

7−3Version 2010

Variable possible valuesParameters (separated by comma)

SOFISTIK_P Parameters for LST/ERG files

number of lines per pageNo of columns left marginNo of lines bottom marginNo of lines top margin

68 6 0 0

Type of formfeed 0 = blank lines only 1 = form−feed character 2 = 1H1 (old FORTRAN)

Type of linefeed 0 = default 1 = convert UNIX to WIN

Total of printable columns 82

Pagenumber 0 = default −1 = omit numbers

SOFISTIK_GHSOFISTIK_GW

Size of default Grafic areafor URSULA in mm

Default fits in all versionsof layout, larger

KOPF1KOPF2KOPF3

First Headder LineSecond Headder LineThird Headder Line

SOFISTiK_PRODIR alternate directory for thedatabase and project files

Saves all project fileswithout explicit pathname

SOFISTiK_TMPDIR alternate directory for alltemporary project files

Defaults to SOFISTIK_PRODIR

PSJOBPAR Default Values for PS see Chapter 6.

PSJOBINFO Time & File stamping for PS see Chapter 6.

CDBASEMEM Size of Memory for CDBASE inBytes or MBytes

default: 1MB

CDACCESS CDBASE multitasking feature SINGLE = deactivateNOWAIT = do not wait

if locked (usefull for remote analysis)

SOFiSTiK Basics

Version 20107−4

Variable possible valuesParameters (separated by comma)

CDBASETEMP Directoryname for temporaryscratch files

Using TEMP or TMP if notdefined

CDBASEVER Version of CDBASE format CDBASEVER=400max. 2 GB, compatibel to 97.

CDBASEVER=401as Version 501, butwithout password option

CDBASEVER=403as Version 503, butwithout password option

CDBASEVER=501maximum 256 GB (Default)

CDBASEVER=503maximum 1024 GB

The variables which are described in the above table have to be set in the SOFIS-TIK.DEF at beginning before the first expression in parentheses:

SOFISTIK_C=...SOFISTIK_GH=...SOFISTIK_GW=...SOFISTIK_A=...SOFISTIK_P=...[Layout−1]....

Basics SOFiSTiK

8−1Version 2010

8 Starting an Analysis.

8.1. GeneralitiesEach program expects its input data in a file. The input consists of records, whichhave 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 thiscase the normal procedure is to gather the entire data in one or a few files, andthrough the appropriate records within the data make calls to the respective pro-grams.

Therefore the structure of an input file results in the following scheme:

+PROG AQUAInput data for program AQUA

+PROG SOFIMSHAInput data for program SOFIMSHA

+PROG STAR2Input data for program STAR2, 1st load case

ENDInput data for program STAR2, 2nd load case

END

+SYS COPY *.ERG D:

+PROG WINGInput data for graphics

END

The first line should be a PROG line. Each module can be called as often as de-sired. The order of execution of the programs corresponds to the order of thePROG lines in the file. If −PROG is entered instead of +PROG, the associatedmodule will be omitted. Single modules can also be selected directly.

8.2. #DEFINE − Parameter SubstitutionSPS is further capable of making global replacements in the input file. The declar-ation of text macros must take place before they are used. This is done via a line

SOFiSTiK Basics

Version 20108−2

#define text=name. The name of a text macro consists of up to 10 characterswithout $. The first character of a name of a text macro has to be a letter. The valueof the text macro is a text of arbitrary length. Parameters within an assignmentare not evaluated until the replacement. A redefinition of an assignment is poss-ible.

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 lettershave no influence. The replacement can be recursive. Definitions like$(A$(INDEX)) are allowed.

Example:

$PROG (extension for TEDDY)#define LENGTH=3.70#define WIDTH=30#define HEIGHT=50#define PLATE=50 20 10 80

PROG AQUACONC 1 B 25STEE 1 BST 500SREC 1 $(HEIGHT) $(WIDTH)SREC 2 $(PLATE) ASU 2.3END

PROG SOFIMSHASYST GIRDNODE 1 0.0 0.0 FIX PPNODE 2 $(LENGTH)/2 0.0NODE 3 $(LENGTH)BEAM 1 1 2 1BEAM 2 2 3 1END

Unlike the CADINP variables #() the $() variables are replaced by strings, so wecan insert literals or generation macros.

There are two default parameters, namely $(NAME) containing the primary nameof the output file and $(PROJECT) containing the name of the project. These canbe helpful especially for SYS commands.

Text macros which are not defined in the input file can be set with a SET−record.When the command (e.g. in the environment) is given:

Basics SOFiSTiK

8−3Version 2010

SET SIZE=LP O FORM ZTVK

SPS can insert in all the files the relevant format:

SIZE $(SIZE)

Moreover it is possible to describe global parameters for SPS in a SOFISTIK.DEFfile. This results in a hierarchy of three layers:

Firstly a definition in the input dataSecondly 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 onceat any point in the dataset. A maximum of 256 internal blocks and an unlimitednumber of data blocks in an arbitrary order are allowed. Blocks can be recursivelybuilt in a depth of up to 32 levels.

#DEFINE name Beginning of block name (up to 8 characters)#ENDDEF End of block#UNDEF name Delete a defined block#INCLUDE name Insertion of block name from memory

or file name

Using blocks does not only free the user from copying re−occurring input lines,but also enables the use of subprograms.

Example:

#define SECT$PROG AQUA$ TRAPEZOIDAL CROSS−SECTION PARAMETER BO,BU,HPOLY UPZVERT 1 #1/2 −#3/2 2 #2/2 #3/2CURF 3#enddef

PROG AQUA

SOFiSTiK Basics

Version 20108−4

STEE 1 ST 37SECT 1 ; LET#1 0.60,0.20,0.60#include sectSECT 2 ; LET#1 0.60,0.30,0.60#include sectSECT 3 ; LET#1 0.60,0.30,0.70#include sectEND

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

Basics SOFiSTiK

8−5Version 2010

8.4. #IF − Conditional Input

IF THEN ELSE constructions can be defined. This means that larger input blockscan be inserted and removed, which is more difficult using the IF constructionsin CADINP, and that several program calls can be grouped in one block.

The relevant control lines are familiar to all C−Programmers. In the first columnthe 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 tobe true if it is defined and not empty and not equal to zero. But it might be alsoa comparison $(MODE)==EC or $(MODE)<>EC or $(MEMBERS)>3. Be awarehowever that the comparisons are purely lexically based on strings, adjusted tothe 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 #elsewill 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 .....

SOFiSTiK Basics

Version 20108−6

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

The indentation is only used for readability. In the above example STAR2 is usedfor 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 isgiven as follows:

#DEFINE L1=10.0#DEFINE L2=20.0#DEFINE L3=30.0#DEFINE 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 thetotal analysis. It is summarised under a special program name called TEMPLATE.

Basics SOFiSTiK

8−7Version 2010

The input consists only of text and picture elements combined with arithmetic ex-pressions. But the mechanism is general available for all programs.

Now within URSULA you may change the selected parameters and re−analyzethis given module. This allows other users to benefit from these macros whichmay contain rather complicated treatment, but need only a few problem depend-ant parameters .

8.6. Iteractive Analysis with Multiple Modules.

2nd Order Theory for nonlinear materials is contained in the programsSTAR2/AQB. However, only one method of computation of the reinforcement canbe considered by STAR2. A computation with different methods can be implem-ented by an iteration between AQB and STAR2. The iteration is controlled by theparameter ITER of the record PROG.

PROG STAR2 1st Step for 1st Order TheoryCTRL I Definition of loading casesLC ....ENDPROG AQB ITER parm parm separated by blank spacesBEAM ....; LC.... 1st selection and design definitionULTI ....; NSTR....ENDBEAM ....; LC.... 2nd selection and design definitionULTI ....; NSTR....ENDPROG STAR2 ITER parmHEAD ....CTRL II 1END

The maximum number of iterations to be made is regulated by ITER (e.g. ITER30), default is 20 iterations.

This mechanism has been extended with Release 23 for other combinations ofgeneral modules. To terminate the iteration it is required to specify within the CA-DINP−definition explicitly EXIT_ITERATION.

SOFiSTiK Basics

Version 20108−8

PROG TEMPLATESTO#TARGET 0 ; STO#PARAM 1.0PROG AQUA ITERRCL#PARAM QNR .... Definition of sectuion using #PARAMPROG AQB ITERBEME .... Design and save resultsENDE@KEY / LET# TARGET ... Calculate a target function to

become zeroIF ABS(#TARGET)<0.001 EXIT_ITERATIONELSE STO#PARAM new_target_valueENDIF

8.7. Operating System Commands.

Any desired shell commands can be integrated in an analysis. Parameter sub-stitution 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 command will be executed as in anybatch file, if the last PROGline was active.

+SYS command command will be executed as in anybatch file.

−SYS command command will not be executed, allfollowing *SYS linesdeactivated.

e.g:

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

+SYS wait name.exe parameterWPS is initiated to wait with the processing of the further modulesuntil the active process is finished with ”+SYS −wait name.exe”.

Basics SOFiSTiK

8−9Version 2010

8.8. Job History

In an analysis with many individual programs it can become of importance tomake a reconstruction for the time−history of a problem. Therefore SPS addssome auxiliary information to the generated input files. The information is con-trolled by an environment variable:

SET PSJOBINFO=n

n = 0 no informationn = 1 filename and date (only in data echo)n = 2 like 1, including job number (only in data echo)n = 3 like 2, yet in an additionally generated header

The default is 2. The job number consists of an 8−letter description of the com-puter and a varying number, which is stored in a PSJOBNR file. In a multiuserenvironment PSJOBNR should be put in the current directory, if access conflictshave occurred.

Examples for PSJOBINFO:

PROG AQUA$ Datafile: D:\STATIC\P00\DAT0.DAT (.#01) 14:48:48 25/05/95HEAD .....

PROG AQUA$ Datafile: D:\STATIC\P00\DAT0.DAT (.#01) 25/05/95$ Jobnumber: PC−Nr:17/8700063 14:48:48HEAD .....

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

SOFiSTiK Basics

Version 20108−10

8.9. Start of a Single Program

Sometimes it can occur that one would like to start a program directly. This is gen-erally possible if the input file already contains all parameter replacements. If youwant to create a parsed file from a normal input file, you can do this by using WPSwith

File > Save Parsed File ...

if you want to save the complete parsed fileor alternatively with

File > Save Parsed Module: name ...

if only a single module is required to be parsed. The module selection is done inthe WPS−tree.

Basics SOFiSTiK

8−11Version 2010

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 out-put files. If the name contains blanks, it must be enclosed with ”. project is thename of the data base. In general the same parameters as for SPS are used inparameter. Some extra parameters are added though. For example in controlling,what type of metafile is to be created and whether an existing metafile is ap-pended or deleted.

If one starts an analysis program without using any parameters, the program willstart up by showing its name, version number and the list of the possible para-meters. The user is asked for the name of an input file. An empty input file (or Re-turn key) ends the program immediately. This procedure is helpful in order to testthe integrity of the program. The license and the version of the ERR−file arechecked.

SOFiSTiK Basics

Version 20108−12

8.10. Special Features for Start





(Default: −0).



−b WPS starts in batch mode. The calculation isstarted immediately and at the end the windowis closed automatically.

−e Generates a message window at the end of thecalculation if an error occurs. Makes senseonly in connection with −b or −run. If theparameter −e is not set and the calculationends with an error, no message window is indi-cated. Nevertheless, WPS does not end, so thatthe error can be read in the error protocol.

−close Closes the window after calculating regardlessof whether an error has occurred or not. Makessense only in connection with −b or −run andwithout −e.

−noclose After a calculation the window does not close.Makes sense only in connection with −b or −run.

−z Attaches the result file (name.plb or name.erg)to a perhaps available result file.

−run The calculation starts immediately (e.g. whencalling from Teddy with "quick start").

Basics SOFiSTiK

8−13Version 2010

−run:xx The calculation starts immediately (e.g. whencalling from Teddy with "quick start"). xx isthe number of the PROG line, which is the onlyactive module to be calculated.

−urs:xx Sets the module "PROG module urs: xx" activeand all other inactive.

−cdb:name Name of the CDB (if the name differs from DATname).

SOFiSTiK Basics

Version 20108−14


Basics SOFiSTiK

9−1Version 2010

9 Output.

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 importantmessages about the general operating situation. It will normally only be neededin case of errors or bad performance problems. It contains for example: the star-tup information, version numbers, consumed computing times, information abouterrors, 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 forprinting. This file can also be examined or edited by a text editor or printed as itis. Page numbering is performed automatically by the programs of the SOFiSTiKseries 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.

SOFiSTiK Basics

Version 20109−2

9.3. Printout with URSULA.

9.3.1. GeneralURSULA is a result−viewer, which is easy to use. It is used to accumulate theprintout of all SOFiSTiK programs and to send it to the printing device. URSULAhas a similar layout as the Windows−Explorer and provides the user with variousoptions for designing individual printout, e.g. in the selective choice of the outputvolume (text / graphics) or in the layout design (company logo, footer, etc.). All thegeneral settings (font, page numbers, date, margin, etc.) are defined in the menuSOFiSTiK > Global Options and SOFiSTiK > Project Options (see in the Adminis-tration Manual).

9.3.2. Activation of URSULAA specific check box within WPS (Default in SOFiSTiK > Global Op-tions) has to be activated before URSULA can be used. After ananalysis the printout (with the extension PLB) can be opened via theURSULA icon. The output can be modified according to user prefer-ences. The user−specified settings are stored in a correspondingURS−file and are usually available after a recalculation.

9.3.3. FeaturesSelecting the volume of the printout

The output volume can be configured by the user to his requirements. With thebulb− icon in the URSULA− tree, the printout of the modules is activated or deacti-vated. With the book− icons you can switch on and off the sections. The settingsfor the output volume are saved in the corresponding URS−file and are normallyavailable again after a recalculation. Individual sections can be temporarily moved in the URSULA−tree and thechanges are considered when you print the file. However the changed sequenceis no longer available after a recalculation. Therefore the requested module−order should be defined already in the input file.

Basics SOFiSTiK

9−3Version 2010

Insert table of contents

With Insert > ”Insert Table of Contents” there is generated automatically a tableof contents of the complete printout.For the module− headings in the table of contents, the module text from the UR-SULA− tree is inserted, or the module name if no text is defined. Disabled sectionsare not included. Furthermore, the page number of the printout is added. The set-ting ”Insert Table of Contents” is saved in the URS− file.

SOFiSTiK Basics

Version 20109−4

9.3.4. Support of international character codes (UTF−8)

Starting with Version 2010, all special characters are shown with URSULA. Thereadability of the output result has been significantly improved. In particular, forinstance, 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 loca-tion of the selected printer is displayed.

Output to File

A printing output to a file is also possible. When selecting ”Generate PDF file”, aPDF file created in the current directory with the associated file−name”name.PDF”. No additional Software from Adobe is required.

Basics SOFiSTiK

9−5Version 2010

Special Print Options

There can be printed several smaller pages on one sheet. Temporarily the designof the page number or the date can be changed for printing.

SOFiSTiK Basics

Version 20109−6

9.3.6. Advanced FeaturesZoom handling

Besides the usual zoom functions, a slider is available, and so a fast and continu-ous zooming in the current window is possible. With Ctrl + mouse wheel a system-atical zoom in or out is possible and with Ctrl + mouse drag, a specific zoom win-dow can be opened.

Options of Selection

By URSULA following selection options are supported:

• Line Block

• Column Block

• Table columns

Basics SOFiSTiK

9−7Version 2010

• Individual words

With ”Edit> Copy”, the selected area can be saved in the clipboard. A save in Ex-cel format also is possible (Edit> Copy to Excel, and in Excel Edit> Insert Con-tents).

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. Al-ternatively first highlight a field in the header, now in connection with right−clickmenu > ”Select Column” a full column block can be selected.

SOFiSTiK Basics

Version 20109−8

9.3.7. Functions in control treeSelection 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 right−click−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 acti-vated or deactivated (at the disabled chapters the icon is rotated by 90°) and com-pletely pushed together (in the right−click−menu).

Basics SOFiSTiK

9−9Version 2010

Assistance in troubleshooting

In case of warnings the affected modules and the relevant sections of the printoutare 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 thecorresponding URS file. They are still available when the PLB is opened again.After a recalculation, they will only be available in exceptional cases, because aunique assignment is no longer possible.

SOFiSTiK Basics

Version 20109−10

9.3.8. Special Features for StartFor special cases the user may start the program from a command shell by usingthe following command lines:




(Default: −0).


−t Enforces a text view.

−g Enforces a graphic view.

−r Enforces an automatic refresh (no demand), ifthe PLB has changed.

−stli:AutoCAD− Version

Supports steel list.

−txt:name.txt Creates a text file.

−urs:name.urs Explicit target of an URS−file.

−ssd:_xxx _xxx = List of pseudo extensions for a totalfile. Example: ursula name.plb −ssd: _002;_003; _006 Creates from name_002.plb,name_003.plb and name_006.plb a total PLB.

−plbs:name1.plb; name2.plb

Adds several PLBs to a total file. Example:ursula name.plb −plbs: name1.plb; name2.plbCreates from name.plb, name1.plb and name2.plba total PLB.

Basics SOFiSTiK

9−11Version 2010

9.4. Graphical Output GRAFiX.

9.4.1. General Hints

GRAFiX is a program for the graphical postprocessing of calculations with FiniteElements and frame and girder systems. It allows the graphical representation ofthe most values and information which are saved in the database, e.g. informationabout structures, calculation and design results.

Additionally to the functionality of the predecessor program WinGRAF, there aremore results available for the graphical representation due to another interfaceto the database. Thereby a faster and more variable access on the database va-lues is guaranteed.

9.4.2. Work Flow

The program GRAFiX works with the graphical interface HOOPS−OpenGL. Dueto 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 GUIelements which can be scaled.

The graphical representation of cross sections is possible in the program GRA-FiX.

9.4.3. Structure

Via a multi−document environment several databases which are represented andmanaged then in different windows can be opened simultaneously.

SOFiSTiK Basics

Version 20109−12

load c

ase s

ele

ction

cro

ss s

ection s

ele

ct.

mate

rial/tim

e s

tep

undo

repre

senta

tion s

el.

result t

ree f

or

curr

ent

docum

ent

layer

tree

(layer

per

docum

ent)

text

heig

ht

transpare

ncy

dis

pla

ced s

tructu

re

unit (

vect. length

)

exlo

sio

n r

epre

s.

gra

phic

al are

a

(severa

l docum

ents

possib

le)

Basics SOFiSTiK

10−1Version 2010

10 Troubleshooting.

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

10.1. General Strategy

Please keep in mind the following points in case you encouter some incompre-hensible errors:

• The probability that en error has been caused by wrong input is significantlylarge. The observation of warnings at any stage during the analysis or theinstallation can supply valuable hints.

• All programs, even those of SOFiSTiK, contain errors as long as the areused. They will show up most likely if you are in hurry and start treatingsome completely new application area of the programs. You should there-fore first examine how the program behaves, using small examples. Oneof the most frequent causes of such errors is a misleading interpretationof the manual or the implemented theory.

• If the system was still working yesterday, think about what has changedsince then (new computer, new operating system, other inputs etc.)

• In some cases an error message may not describe the real cause of theerror, although this is highly unlikely. It might occur when the error was notcorrectly detected in a previous module. The programs do not stop at thefirst error they encounter, but try to continue and to detect as much errorsas possible.

• Rather than searching for hours, sent a support request via Email to SOFi-STiK Hotline or your local supporter. Even if you may be charged for exten-sive services, it usually will be more economical as SOFiSTiK has betterpossibilities to locate the error.

SOFiSTiK Basics

Version 201010−2

10.2. Standard Warnings and Error Messages

The story of an analysis is stored in a protocol file of the file type (*.PRT). In allspecial situations (program error or user error) this file must be examined. Theexecution of the analysis is automatically stopped if such an error occurs. Regularerrors or Warnings have the form:

• Warnings, the program prints the message:++++ WARNING NO. nnnnn IN PROGRAM xxxxas 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 xxxxas well as one or more lines of explanation. The analysis continues orstops.

Finally, each program writes the number of warnings and errors in the .PRT−File.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 withprogram 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 importantstrategy to find and eliminate input errors Please delete every ssd−task, structuralelements, program blocks, load cases, etc. which are not involved with your prob-lem. Now you have a small and clear project, which can be checked easily. In al-most every case you will find out where the problem occurs and also you will beable to solve it by yourself.

Please use this strategy also if you can’t find the problem and send your mini-mized project file with your support request via Email to [email protected] .

Basics SOFiSTiK

10−3Version 2010

10.3.1. Problems with Database (*.cdb)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 sol-ution is to reduce the size of the file by splitting and merging the file intoseveral databases with DBINFO. The following CDBASERVER com-mands 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 GBsame 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. Ifonly the locks are not released you may remove them with a special buttonor with the command:

DBINFO projekt,ZIf the file is badly damaged, the best solution is to delete or restore the data-base and repeat the analysis.

• Saving the data base periodically is quite wise especially for working withlarge projects.

10.3.2. Input Error in TEDDY DatafileIn case of a wrong input in the TEDDY file, the program gives you an error mess-age. If you open the URSULA output and go to the ECHO print, the error messageis plotted directly after the incorrect input line. Also the error message gives yousome hints what should be the correct input. This will help you in most cases tofind and eliminate the wrong input.

SOFiSTiK Basics

Version 201010−4

10.3.3. Error in System Generation with SOFiPLUSIf you run into errors while meshing your SOFiPLUS drawing you may use a verysimple algorithm to locate the problem. First mark randomly half of your structureand delete it. Now start the meshing again. If the problem occurs again, mark thenext half of your structure,delete it, mesh again and so on. If the problem doesnot occur, go back and mark the other half of your structure, delete it and meshagain. With this principle of deleting stepwise half of the structure you will mini-mize your system. Probably you will find the error by yourself and can solve it. Ifthe problem is solved you go back to your complete system and solve the problemthere as well.

If you can’t solve the problem please send your minimized drawing to our support.

10.3.4. Error during CalculationNormally we face two major problems in case the analysis will be aborted with anerror message. Either the system is instable or no convergence was found duringa 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 checkthe displacements of the Eigenvalues with the ANIMATOR. Then you will see veryquick, what causes the instability.

Normally the instability problems occur in large 3d systems with lots of hinges andkinematic constraints. Therefore we recommend the following procedure:Create your system Step by Step and avoid to define any hinges and kinematicconstraints in the first Steps. Now define a load case self weight and start the lin-ear analysis. If you get some reasonable results go further on and start to definethe 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. Ifyou 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 can’t find the problem, please send your minimized file to our support.

Non−linear Analysis:The most common problem during a non linear analysis is, that no convergencewill be reached. Either the structure is to weak for the applied loads, or the chosenalgorithm has some numerical problems. In the first case you may change dimen-

Basics SOFiSTiK

10−5Version 2010

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

10.3.5. Problems with Results

The interpretation of the results may cause some questions. Every manual con-tains a chapter ”Theoretical Principles”. Inside this chapter the basics of the de-sign algorithms are explained so that a manual check of the design results will bepossible. In case there are still some questions open, please send a smallexample 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, pleasecontact our support via Email [email protected] . You will find the GeneralTerms of Support Conditions on our website:

http://www.sofistik.com/fileadmin/FILES/sonstiges/Terms and Conditions for SupportSer-vices_01_02_2009.pdf

10.4.1. Support Accessibility

As you know, you may contact us via our SOFiSTiK Online Portal, via E−Mail, viaFax or via phone. In order to work most efficient without any interruption from in-coming phone calls, you can’t contact our supporters directly.

Our primary target is, to help you as soon as possible and to increase our re-sponse quality level continuously.

Most support requests are very complex and can’t be solved in a short time. Forthat we work us into your problems and data files and contact you via E−Mail orphone call. Either we have a solution or we reproduced your problem and can startdirectly into a detailed discussion to find a common solution or at least a workaround.

SOFiSTiK Basics

Version 201010−6

10.4.2. Customer’s Obligation to CooperateIn order to avoid time consuming mails and phone calls, would you please con-sider the following issues in your support requests. This assistance is very import-ant for a fast and direct solution to your support request.

• We always need to know your customer number. For example you will findthe number printed in the html−file of your last support request, or on yourlast maintenance invoice.

• We always need to know the used program versions. For example SOFi-CAD−Detailing version 17.2 with AutoCAD 2008, or SOFiPLUS version17.1 with AutoCAD 2008. Using the FEA package every analysis createsa 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, Win-dows Vista 32 bit, Windows Vista 64 bit, Linux).

• Please note, we are not involved in your project and have no more informa-tion than what you sent to us. Therefore it is very helpful to get condenseddata files and a precise problem description.

• Minimize your drawing or the project input data file. Delete everythingwhich is not necessary to reproduce your problem.

• Please try to describe your problem as precise as possible. Under whichcircumstances does the problem occur? What did you do, which clicks?Example FEA: ”I checked the beam element 2037, x=0.00 m in loadcase2031. I can’t reproduce the amount of reinforcement computed by AQB(Version 13.40−23) = 12.35 cm2. The result of my hand calculation givesme only 8.50 cm2. Please find attached my hand_calculation.pdf. Why arethe results different?”

• Provide us with additional information besides your data files, describeyour workflow, send us scans of your hand calculation, every additional in-formation 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 can’t startworking on your request.

Basics SOFiSTiK

10−7Version 2010

10.4.3. Support Request via SOFiSTiK Online Portal

With a valid maintenance contract you have also the possibility to use our SOFi-STiK 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 higherpriority.

• Access to FAQ−database 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 mainuser can manage his company data, address, contact persons and SOFi-STiK Online user.

For all this reasons we recommend to use this portal. You will find the portal viawww.sofistik.com/support on the left hand side > Links > SOFiSTiK Online (Por-tal). 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 ques-tion. Please reply only for direct questions to the key issue. For additional ques-tions use a new ticket even if you refer to the same project files. This is very import-ant 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 supportrequest with all necessary description and attachments. Go to the menu HELP> SOFiSTiK Hotline

Nevertheless we recommend to use our SOFiSTiK Online Portal

SOFiSTiK Basics

Version 201010−8

10.4.5. Create a Diagnostic.xml FileAll necessary information about installation, licences, program libraries are savedin 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 thefile with the command File > Save as Diagnostic. This file will be created automati-cally if using the command ”SOFiSTiK Hotline” describe above.

Basics SOFiSTiK

10−9Version 2010

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

SOFiSTiK Basics

Version 201010−10


Basics SOFiSTiK

11−1Version 2010

11 Additional Information and Help

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

11.1. InfoportalOn our website www.sofistik.com/Infoportal you may navigate through all sort ofinformation. You may search in our document data base using the categories”Document Type”, ”Product Group”, ”Subject” and ”Application”. A ”Search forKeywords” is also possible. For example most program features of SOFiPLUSare shown in small Tutorial Movies.

SOFiSTiK Basics

Version 201011−2

11.2. CADINP Samples

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

Basics SOFiSTiK

11−3Version 2010

11.3. Forum

Our User Group is open for all registered SOFiSTiK user and a place for dis-cussion. Please send support requests exclusive via Email to [email protected] and do not poste them into the User Group. You will reach our User Group via www.sofsitik.com/user−group.

Documents

Sofistik Basic v.2010