Release note
Contents
1. Figure 3 6 2 Content of file folder after running script run all 3 7 Example 4 Using the SED editor to modify master input files In the previous example the input to USFOS was composed by some common files special files and in all cases the content of the files were pre defined In the current example another and even more flexible solution 1s chosen Instead of assembling pieces of input the content of the input file s are modified prior to the analysis As the modification should be performed in a batch run a batch editor is necessary The UNIX shell on both UNIX workstations and the NutCracker UNIX shell on Win NT offers the SED editor the Stream EDitor The operation needed from the stream editor is the REPLACE or SUBSTITUTE command where one character string should be replaced by another The cryptic UNIX command is wrapped into a file which here is named substitute Table 3 7 1 and which 1s used as follows Substitute string 1 string 2 FileName In all connections where string occur on the specified file it s replaced by string 2 The SED editor is case sensitive differs between upper and lower case characters Quotes must be used if blank character s occur in the strings sed 1 s 1 82 g 3 gt subst string temp mv subst string temp 3 Table 3 7 1 Script substitute which utilises the SED editor for substituting strings Release Notes USFOS version 7 7 SI2. Release Notes USFOS version 7 7 SINTEF 2000 04 01 SINTER FETITSTSTETSETETTRTRTRSTESTSTETTRTRTETVEATASTRATH THRTRTRTTRTTTRTRTETETTTTTTTTTTY Author Tore Holmas SINTEF Group Norway Date 2000 03 18 HHH HHH HH HHH HHH HHH Hee HHA Hea HHA Hea Raa Rea aa EA PE IE test Se WOM then echo pub dr dr di di di dio di di dir di di di dir do di di dir dir di di di di di di dir di dir di di di di di dir di di di di dir di di dir di di di di di di di d echo a Tt echo 5 Creates the directory Label oe echo a creates a copy of usfos control file and gk echo ai adds necessary NONSTRU commands ak echo a can echo Assumes structural file on model stru fem echo a P echo Results are stored on file SSCRATCH res cai echo a P echo 2 Usage elmdel Label elemli elem2 elem3 echo ai Pu echo 7 a Prec March 2000 echo ooo ooo oo oe oe oe e e 0 A A A A A A A A A A A A A A AR AR AR AG AR AG MR BG RGB XR G XB G MAG MAG Xx X T else echo m m echo Creates directory i941 zi mkdir icu Ol cd Pw od count 1 for i do if Wrest count gE mr then echo Processing Element ms Rie ar if test ooount eq T2 then Heading echo di gt nonstru elem fem echo 4 gt gt nonstru_elem fem echo Nonstructural Members sew gt gt nonstru elem fem echo gt gt nonstru elem fem echo di gt gt n
3. etc In cases where many USFOS analyses should be performed well organising of both input and output files is important There should be no doubt about what was the parameters used for Release Notes USFOS version 7 7 SINTEF 2000 04 01 SINTER 6 this particular result plot and so on It is highly recommended to not use one input file set which is modified over and over again until all cases are run because Q Possible confusion about input parameters used a Difficult to repeat the analyses after a time a Requires manual editing before each new run impossible to automate It s better to plan and organise the USFOS analysis in a way that makes it possible to ultimately perform hundreds of analyses using only one magic command One solution among several is using UNIX scripts and the following sections will describe this solution USFOS even on Windows NT runs in a UNIX environment and all procedures described in the sections below are running on all computer platforms However some differences may occur f ex C TEMP on PC and tmp on standard UNIX The next sections will deal with use of UNIX commands typed in from the keyboard in the old fashion way It s therefor worth spending some minutes adjusting the UNIX command prompt window 3 2 Adjusting the UNIX korn shell window Before you start using the UNIX korn shell it S recommended to modify slightly the layout Figure 3 2 1 shows the default window with
4. members of the actual group The groups are referred to In connection with assigning properties to elements which will ease the input reduce the amount of input lines In xfos its possible to include exclude groups in the structural image Edit Clip Group Elements are defined members of a group using the GROUPDEF command The element may be identified through Element ID All elements referring to given material ID s All elements referring go given cross section geometry ID s All elements members of existing groups Ooo DL The actual way of defining the elements is specified using the parameters Elem Mat Geo or Group as shown in Table 4 1 1 r ID List GroupDef 10 20 30 GroupDef 1 GroupDef 5 GroupDef 88881 88 Table 4 1 1 Defining element groups using of the GROUPDEF command If wanted extra nodes could be defined members of an actual group and the command egroupnod is used for this purpose see Table 4 1 2 This command is used in connection with guiding loads from non structural members towards kept structural nodes T Group ID Nodes GroupNod 888 70 80 90 Table 4 1 2 Assigning extra nodes to a group using the GROUPNOD command Release Notes USFOS version 7 7 SINTEF 2000 04 01 SINTER 24 4 2 Model repair Creating an accurate structural model is time consuming and costly and it 1s therefor normal to use existing models rather than
5. nodes to Element group NONSTRU Nonstructural members Extended input STRUCTEL Structrual members override NONSTRU LIN ELEM Linear elastic elements CHJOINT Extended input Release Notes USFOS version 7 7 SINTEF 2000 04 01
6. 1 SINTER 10 3 4 Example I Fixed USFOS input file names The simplest example on a UNIX script which saves you for tediously typing is a file with name gol containing following SUSFOS_HOME bin usfos 15 lt lt ENDIN head stru load res ENDIN Table 3 4 1 Content of script file eol with 3 fixed USFOS input files Explanation The variable USFOS HOME is set during installation of USFOS on both UNIX and NT computers It contains the file path of the root of the actual USFOS version By prefixing the variable name with the contents of the variable name becomes available for use in connection with any UNIX command USFOS_HOME bin usfos is the address to the USFOS code and by adding 15 after the file name a workspace of 15 mill is required The lt lt ENDIN defines that the usual screen input output is given between in the lines between ENDIN and ENDIN The name ENDIN is an arbitrarily chosen name of the label In a usual USFOS run it s first asked for the control file name prefix which here is set to head Further it s asked for the structural and load files which here are stru and load respectively Finally USFOS asks for the result file prefix which 1s set to res By typing gol USFOS will start use the input files head fem stru fem and load fem and store the results in files with prefix res All input files must be located on the same director
7. 6 10106 10107 19105 15111 15106 20110 10113 10360 10111 15185 15112 15107 10112 19103 20095 20096 15114 15113 20097 15191 20099 20098 16607 16407 16307 16207 16107 10365 10243 17607 10367 10118 10114 10116 20111 10122 20124 16213 16214 16109 16110 16209 16114 16210 16112 17509 17510 17511 16614 16612 16613 17512 17612 17613 17614 17610 17514 17609 16609 16314 16410 163913 16309 16310 16312 16412 16512 16514 16510 16413 16414 10121 10120 19102 16617 16616 15189 17517 15115 16516 16416 16417 16317 16517 15108 16216 10123 10125 10126 17617 17616 16117 16116 16218 16119 16318 16118 16618 20085 17619 17618 16519 20122 16418 20112 16518 17620 16120 16420 16320 16620 16220 10127 19101 GroupDef 3000 Geo Pipes 10102 10104 10105 10106 10107 10109 IQIIS TOTIS 10128 10130 10131 20072 20113 20114 19109 20075 20076 20077 20073 20074 20080 20080 20082 10185 10186 10102 10253 16202 16402 17502 17602 10114 10365 10183 GroupDef 16319 Geo 16319 GroupDef 16219 Geo 16219 SPECIFY Groups 1000 2000 and 3000 NonStructural NonStru Group 1000 2000 3000 Table 4 2 2 Shrinking model using the GROUPDEF and NONSTRU commands If the definition of the bounding surface the gbound command is left out for general sections default values are used and a warning is printed see Table 3 5 2 The default values are shown in the same table Release Notes USFOS version 7 7 SINTEF 2000 04 01 26 Warning GBOUND specified for General Default Warning G
8. BOUND specified for General Default Warning GBOUND specified for General Default Warning GBOUND specified for General Default GBOUND 10101 0 8 LeU 0 6 1 0 Table 4 2 3 Default Gbound data assigned to general beams When element groups are defined the contents of the different groups are listed in the out file see Table 4 2 4 In the actual example group no 000 is defined through geometry ID s and the specified ID s are listed first similar if the group was defined through material ID s Next the elements which are members of group no 1000 are listed and finally all nodal point to which the element are connected to are listed GROUP DEFINITIONS GROUP label Geometry Group no Contains following Geometries 10101 10228 10229 10230 10231 10251 10252 10352 15198 FILII 16106 16129 17935 17600 17634 5001 5002 5003 5004 5005 5006 5007 5008 5009 5010 5011 5012 5013 5014 5015 5016 5017 5018 5019 5020 5021 5022 5023 5024 2025 5026 2027 50268 5029 5030 5031 5032 5033 5034 5035 5036 78614 78615 755507 755508 726550 726551 726500 726501 54531 54837 54942 54943 54859 Table 4 2 4 Print of group data geometries elements and nodes on the out file The example shown in Figure 4 2 3 represents a first stage in a model repair procedure The entire structure is still structural but members are grouped as specified above By using the Edit Clip Group command in xfos it s possible to visuali
9. Dir 30deg and T 16s Release Notes USFOS version 7 7 SINTEF 2000 04 01 19 SINTER 20 3 8 Example 5 Procedure for element removal redundancy analysis The final example solves following problem a Remove the structural members one by one a Use the same structural file and control file a Save the results from the analyses in separate file folders Figure 3 8 1 shows the content of the example folder before and after running the actual scripts The scripts are organised in the etc folder while the structural model is stored in the model folder The content of the script files are described in Table 3 8 1 Table 3 8 2 and Table 3 8 4 Contents of Example 5 Element Remowal Contents of Example 5 Element Remowal Elem 1 Elem De Elem 03 Elem l4 Elem 15 Elem 05 06 and 1 Elem DB Elem D Elem 18 Elem 09 Elem 10 J Elem 11 Elem 12 and 13 Jete J model Contents of madel Contents of etc aa head fem load fem a stru fem a run_usfos ka subst one in substitute Figure 3 8 1 Files Folders before and after running the script Define varible SCRATCH directory for Raf file storing export SCRATCH tmp scratch Local Dir Element to remove elmdel Elem Ql 01 elmdel Elem 02 02 elmdel elmdel elmdel elmdel elmdel elmdel elmdel elmdel elmdel elmdel elmdel Table 3 8 1 Script file run all Elem 03 Elem 04 Elem 05 Elem 06 Elem 07 El
10. ELEMENT REMOVAL REDUNDANCY ANALYSIS e 20 4 23 dL CROLUP DERINITION oo oo oo 23 L2GRED o E A 24 4 3 JOINT CLASSIFICATION MSL JOINT CHARACTERISTICS 0 28 5 NEW MODIFIED INPUT IDENTIFIERS cccccccccccccccccccccccccccccccccccccccccccccccscccccccccccccees 31 This memo contains project information and preliminary results as a basis for final report s SINTEF accepts no responsibility of this memo and no part of it may be copied SINTER 2 1 Introduction The current version of USFOS version 7 7 2000 04 01 is the intermediate release of the 99 OO user group development period The current release with date 2000 04 01 contains following a CD ROM a Updates of User s Manual a Release Notes this MEMO 2 Contents of CD ROM 2 1 Overview The CD contains documentation examples and new versions of the program codes and the organisation is described in Figure 2 1 1 Both UNIX and NT solutions are collected in the same CD Contents of LIsfas 7 7 Document J Examples PC J Examples UNIX Frogrammers_File_Editor_PFE Lstos_for_Dec_Alpha JUstfos_ for HP Usfos for IBM E Ustos_for_Linux Lsfos for Sol LIsfas for Windows MT 4 0 Figure 2 1 1 Contents of CD ROM 2 2 New versions of the program codes Under each file folder f ex Usros for Windows NTA 0 two folders bin and etc are located The bin fold
11. NTEF 2000 04 01 SINTER 16 With the powerful substitute script available following operations should be done a Create only one master USFOS control file which should be used for all cases a Use one structural file Q Run USFOS wave analysis for 8 different wave current conditions As indicated in Figure 3 7 1 some files are present before the analyses are performed and some are created during the analysis executing the scripts defined in this section Contents of model Case H 20 0 Dir 00 0 T 18 0 Case_H 20 0_Dir 30 0_T 16 0 Case_H 20 0_Dir 60 0_T 16 0 Case_H 20 0_Dir 90 0_T 16 0 Case_H 24 0_Dir 00 0_T 20 0 Case_H 24 0_Dir 30 0_T 20 0 a Master_Heactile a stru ferm Case _H 24 0_Dir 60 0_T 20 0 These files folders are These files folders are Case H 24 0 Dir 90 0 T 20 0 present before running present after running the scripts run all Figure 3 7 1 Files Folders before and after running the scripts Master Headfile Table 3 7 2 The file 1s an ordinary control file for USFOS but some parameters are not yet set Instead the parameters are represented by arbitrarily chosen key words In the actual study the wave height direction and period should be varied and the keyword for the wave height is WAVEH the keyword for direction is DIRECT and the keyword for wave period is PERIOD Script file g0 Table 3 7 3 The first operation in the script is creating a directory using the mkdir command and a
12. OS and save results in unique directories SUSFOS HOME bin usfos 15 ENDIN head model stru Case H 1 Dir 2 T 3 res ENDIN Move head fem into actual Case Dir for backup purpose mv head fem Case_H S1_Dir S2_T S3 Table 3 7 3 Script file go Release Notes USFOS version 7 7 SINTEF 2000 04 01 17 SINTER 18 Script file run all Table 3 7 4 The script file run_all starts go 8 times with different input parameters Wave Height Wave Curr Direction Period Z0 0 00 0 Os 20 30 16 20 60 LOs 20 90 16 24 00 zs 24 SU 20 60 90 End of Script run_all Table 3 7 4 Script file run all USFOS Extreme Wave Height 20 0 Dir 00 0 T Progressive Collapse Analysis JACKET model SINTEF 2000 T v r Define Wave T v lt type gt H Period Direction Phase Surf_Lev Depth WAVEDATA Stoke 20 0 16 0 00 0 0 0 0 0 100 Speed Direction Surf Lev Depth Profile CURRENT 2 00 0 0 0 100 0 0 Table 3 7 5 USFOS control file modified by the SED editor After all 8 cases are run 8 new directories are created see Figure 3 7 1 containing the modified head fem and the analysis results Figure 3 7 2 shows results from one of the 8 analyses and NOTE that the member imperfections command CINIDEF are applied automatically according to the actual wave load direction which here is 30 Release Notes USFOS version 7 7 SINTEF 2000 04 01 SINTER Figure 3 7 2 Case with H 20m
13. SINTER 0 Lm www sintef no Release Notes USFOS Version 7 7 Address SINTEF group MARINTEK Structural Engineering FOR YOUR INFORMATION AS AGREED FOR YOUR ATTENTION COMMENTS ARE INVITED Box 4125 Valentinlyst 7450 Trondheim SW Norwa Members of USFOS user group Location Otto Nielsens vei 10 Tel 47 7359 5611 Fax 47 7359 2660 FILE CODE CLASSIFICATION Open PROJECT NO DATE PERSON RESPONSIBLE AUTHOR NUMBER OF PAGES 700030 2000 04 01 Tore Holmas 31 Release notes USFOS 7 7 April 2000 Contents 1 INTRODUCTION 0 O 2 2 CONTENTS OF CD ROM sssesesesesesesesesesesecscseseseseseseseseseseoscsoseseseseseseseseseseoscsesesesesesesesesesesssscseseseseseses 2 2 2 2 2 NEW VERSIONS OF THE PROGRAM CODES reete sesso sesse sese sesse testes e saos 2 NA 4 PN MEE DV DuC RTT 4 3 EFFICIENT USE OF USFOS ce eee eee eee eee eee eee tees eee se sees sese eeseese eese eese ses esee i see i i eese ses eese seeee 5 So 0 0 5 3 2 ADJUSTING THE UNIX KORN SHELL WINDOW Ne 6 33 SOME UND COMMAND S ooo oo oo oo iex UmPN IE PR D Pn MD DUAE ED E pe bnc DE 9 3 4 EXAMPLE 1 FIXED USFOS INPUT FILE NAMES Ne 10 3 5 EXAMPLE 2 VARYING USFOS INPUT FILE NAMES pp 11 3 6 EXAMPLE 3 ASSEMBLING INPUT FILES BEFORE USFOS ANALYSIS csccesececceccecceccesceccesccuccsccuscscesceecs 13 3 7 EXAMPLE 4 USING THE SED EDITOR TO MODIFY MASTER INPUT FILES eere ener enne 15 3 8 EXAMPLE 5 PROCEDURE FOR
14. create new Existing models in most cases are created for linear design analysis Figure 4 2 1 Large Challange for Non Linear Analysis Seldom existing models are created with non linear analysis in mind and substantial work has to be done before it s suited for non linear problems As computers are getting faster the model size may increase correspondingly But modification of models means in practice manual work and the bigger models the more man hours have to be spent in order to repair the linear model A few years ago a typical jacket structural model consisted of 500 1000 members Today the same structure is represented by 5000 10000 members An increasing part of the model is non structural members introduced of different reasons in the linear analysis see Figure 4 2 1 for typical example If possible the original structural model should become read only and an intelligent filter should transfer the linear model into a model accepted by the non linear tool see Figure 4 2 2 Original Linear Model Intelligent filter Shrinked correct model accepted by the non linear tool read only Figure 4 2 2 Preferred Model Repair solution Often the original linear model will not run at all the analysis fails due to lack of boundary conditions etc To be able to inspect the structure 1n XFOS the use of the dynamic load procedure is a useful intermediate solut
15. em 08 Elem 09 Elem 10 Hlem 11 Elem 12 Elem 05 and 13 Q6 and 12 Release Notes USFOS version 7 7 03 04 05 06 07 08 09 10 11 12 5 End of Run All SINTEF 2000 04 01 SINTER 21 The run_postfos script runs POSTFOS and creates the default history table using the define history and print history commands Similar scripts could be created for extracting nodal displacements of selected nodes element forces etc SUSFOS_HOME bin usfos lt lt ENDIN SUSFOS_HOME bin postfos lt lt ENDIN head stru 1 load SSCRATCH res define hist ENDIN pr2nt nrsbs JJ Table 3 8 2 Scrips run usfos and run postfos Figure 3 8 2 shows the content of one automatically created file folder named Elem 01 which contains the global history created by POSTFOS the log files from the analysis and the different input and output files Table 3 8 3 shows the content of the file nonstru_elem fem which 1s created by the script for two cases To the left the case where element number 1 should become non structural and to the right the case where elements 5 6 and 12 should be removed Contents af Elem 01 Global_Histary a nonstru_elem fern postfos n res status text amp run a strufem Figure 3 8 2 Files created automatically in folder Elem 01 NONSTRU Element NONSTRU Element d NONSTRU Element NONSTRU Element Table 3 8 3 Automatically created files containing the NONSTRU comand
16. er contains the program code while the etc folder contains set up files Release Notes USFOS version 7 7 SINTEF 2000 04 01 SINTER Contents of Ustos_for Windows MT 4 0 WR EU File Folder j azps exe Application etc note gnuplot exe 4339KB Application a gnuplot x11 exe AEB Application 1 mbox exe TOORB Application a posthos exe 1 036KB Application struman exe 1 266KB Application r usfos exe 2821KB Application A bh PS EN 43KB Application A whos ere 2 431KB Application Figure 2 2 1 Program Code located in bin folder aa posthos inca Ej nerd B usfas cshrc i jn ustas Eshre a tos n fos zapas merga B zayas mrcro Figure 2 2 2 Files in etc folder NT to the left and UNIX to the right Installation on UNIX Create a root directory for USFOS the new USFOS HOME directory Copy the actual bin and etc directories to USFOS HOME Copy the Examples UNIX and Document directories to USFOS HOME Define the USFOS HOME variable in the USFOS cshrc USFOS kshrc files Ooo vo Em h h pone d OCUMEr t etc examples Figure 2 2 3 Contents of USFOS_HOME folder after installation Release Notes USFOS version 7 7 SINTEF 2000 04 01 SINTER 4 Installation on Windows NT 4 0 a Copy the new exe files located in the bin folder to the existing USFOS_HOME bin folder a Copy the new postfos inca file
17. hord Chord l ID i rule l diameter thickness yield SUE 7 i MSL mean 1 080E 01 4 500E 03 2 780Ep 22 rc HOC 10096 K capacity I Brace Angle Conn X Facing Gap i Axial MipB MopB ID deg Type brace i Cap4Qtf Cap Qf ap 9 10096 Y capacity I Fg l 4 6011 97 K 5 016 4 122E 05 2 584E 04 973E 04 Ii 3 Y 3 877E 05 2 584E 04 973E 04 1 100 gt 4 114E 05 2 584E 04 973E 04 1 1 5 60 K 4 016 3 jie 2 P YTE Combined i Fg 7 I s Oo o T 1 00 1 00 Pee ot oem I 1 1 I l 1 1 I capacity su Table 4 3 2 Print from the MSL routines on the res out file Release Notes USFOS version 7 7 SINTEF 2000 04 01 Load kN 30 Pu Figure 4 3 1 2D K frame Rigid plastic ISO Ultiguide MSL 700 500 H i am Lee 400 500 peel gd een 300 A e e T Load kN p MM EM CQ A a TT CD OO OO T NO Cc Oo T s y Rigid joints Er Rigid plastic rcu E ISO Ultiguide MSL Test 0 20 40 60 80 100 0 10 20 30 40 Deformation mm Deformation mm OO OO T ED Figure 4 3 2 2D K frame Load deformation curves Release Notes USFOS version 7 7 SINTEF 2000 04 01 SINTER 31 5 New modified input identifiers Since last main release 7 6 following input identifiers are added extended GROUPDEF Define Element Group GROUPNOD Add
18. ion MSL joint characteristics This write up is a preliminary description of the implementation of MSL joint formulation in USFOS for use with the B release of the new feature The MSL equations are implemented with ductility limits and post rupture unloading for tension loading but with no ductility limits for compression loading Joint failure in tension invokes the FRACTURE option in USFOS Joint utilisation will be visualised by colour fringes in Xfos The following shows the input required to include MSL joint characteristics in the analysis of a 2D K frame The input is described in more detail below JNT FORM Q beam stub 1 P delta spring J3 plasticity model JNTCLASS Q OFF i 0 interval for re classification nodex Choral Chord2 Can Rule CapLevel GammaQf CHJOINT 7 6 7 0 MSL mean PET Table 4 3 1 USFOS control input activating MSL joint classification Comparison between the USFOS analysis and alternative joint models and tests results are presented in Figure 4 3 2 Release Notes USFOS version 7 7 SINTEF 2000 04 01 20 SINTER Each time joint re classification 1s performed the following information is printed to the out file Load step 1 60 JOIN TI 2D K F RAME progressive collapse analysis div of Structural Engineering Specified capacity USFOS load Combination no 1 Load step no 60 MED Load level 462 0683 Joint ident e ie M l NODE it Capacity i Chord C
19. ion see Table 4 2 1 In an early modelling stage the gravity loading is sufficient load to ensure that all elements are connected boundary conditions correct etc Release Notes USFOS version 7 7 SINTEF 2000 04 01 25 0 025 OL Od LoadHist TimeHist Points 0 0 1 1 1000 1 Table 4 2 1 Using dynamic load procedure Table 4 2 2 shows the group definition used on a real example and it s here defined 5 groups which all use geometry ID s to identify the elements The general cross sections and the small diameter pipes D 300mm are grouped because elements referring to those beams are the typical secondary members which should be removed from the analysis model When the groups are defined one single NONSTRU command will remove all the members of the actual groups from the analysis model but loads are kept Specify Groups Which should become nonstructural Type GroupDef 1000 Geom j GenBeams 10101 10228 10229 10231 10251 10352 15198 15199 16106 16129 16193 16195 16196 16198 16199 16206 16229 16293 16294 16296 16297 16299 16306 16329 16393 16394 160395 16397 16398 16406 16429 16493 16494 16495 16496 16498 16499 16529 16593 16594 T6395 T6996 L60397 16599 16606 16693 16694 16695 16696 16697 16698 17529 17592 17594 17597 17598 17606 17629 17693 17695 17696 17698 17535 17600 17634 GroupDef 2000 Geo Pipes 1 19107 19108 16202 16302 10253 16102 17502 17602 16502 16602 10102 10104 15110 19106 1518
20. le folder Lines staring with the sign 1s comment lines and may appear anywhere in the script file except between lt lt ENDIN and ENDIN It is recommended to use comments both in scripts and in the USFOS input files Firstly the cp command is used to copy the main structure to the file stru fem Next the selected support structure is appended to the stru fem using the cat gt gt command Similar is done for the load file assembly Release Notes USFOS version 7 7 SINTEF 2000 04 01 SINTER A unique directory for each case is created using the mkdir command and the directory name with prefix Case_ contains information about both support and load USFOS is started with 15 mill and results are saved in the actual Case directory using the result file prefix res for all cases the directory contains information about the different cases Finally the actual stru fem and load fem are moved into the actual Case directory using the mv command Note that if only directory name is defined in connection with the mv command the file name will be unchanged in the new directory just moved cp loa Main_Load cat loa s2 mkdir Case 1 2 head Stru load Case 1 2 res ENDIN mv stru fem Case 1 2 mv load fem Case 1 2 EOF gt gt load fem load fem SUSFOS HOME bin usfos 15 ENDIN Copy Main Structure into file stru fem and add selected support Copy Main Load into file load fem a
21. ll 3 parameters wave height direction and period are included in the directory name Next the nearly complete USFOS control file named Master Headfile and located 1n directory model is copied into the file head fem on current directory The script for substituting named substitute is used three times for replacing the keywords with the actual parameter values Then USFOS is run and the same structural file stru fem is used for all cases Results are saved on the actual Case directory and result prefix is res When USFOS 1s finished the manipulated head fem is moved into the actual Case directory see Table 3 7 5 for example on modified head file Release Notes USFOS version 7 7 SINTEF 2000 04 01 USFOS Extreme Wave Height WAVEH Dir DIRECT T PERIOD Progressive Collapse Analysis JACKET model SINTEF 2000 Define Wave type H Period Direction Phase Surf Lev Depth WAVEDATA Stoke WAVEH PERIOD DIRECI 0 0 0 0 100 Speed Direction Surf Lev Depth Profile CURRENT 2 DIRECT 0 0 100 0 0 20 0 100 0 Script for assembling USFOS input and run USFOS Usage go Wave Height Direction Period Create Directory Copy Master control file into the current head file model Master Headfile head fem Substitute the string WAVEH with the first script parameter 1 substitute WAVEH head fem ag Similar for pat 2 amp 3 substitute DIRECT head fem Substitute PERIOD head fem Run USF
22. located in the etc folder to the existing USFOS_HOME etc folder a Copy the Examples PC and Document folders to the existing USFOS_HOME NOTE If USFOS has never been installed on NT before please contact SINTEF For all systems a Copy the file USFOS key delivered on a separate diskette to the actual USFOS_HOME etc directory 2 3 Manual The User s manual is updated and paper copies of the actual pages are delivered In addition the most important part of the manual the Input Description Usros UM 06 is available for on line reading using f ex Adobe Acrobat Reader or any other PDF readers Contents of Document File Folder Adobe Acrobat Adobe Acrobat Adobe Acrobat Adobe Acrobat Adobe Acrobat Adobe Acrobat Adobe Acrobat Adobe Acrobat A free PDF reader is available on www adobe com 2 4 Examples Approx 50 examples are given under the Examples directories The contents of the UNIX and PC examples are identical the only reason for having two folders is due to computer compatibility UNIX and PC represent the files differently The input files are located in separate folders one example per folder see Figure 2 4 1 In each folder following files are found Head fem USFOS control parameters Release Notes USFOS version 7 7 SINTEF 2000 04 01 SINTER 5 Stru fem Structure and load description in either SESAM o
23. lors Window Preview Screen Buffer Size Width Height Height Window Position Lett Top Iv Let system position window OK Cancel Help Figure 3 2 4 Defining window layout Release Notes USFOS version 7 7 SINTEF 2000 04 01 Figure 3 2 5 Selecting permanent modification of the short cut The UNIX window will from now on look like the one in Figure 3 2 6 with two scroll bars and it s resizable and a comfortable colour Figure 3 2 6 The modified NutC window with scroll bar Release Notes USFOS version 7 7 SINTEF 2000 04 01 SINTER 9 3 3 Some UNIX commands The procedures described in the examples below require that the users knows some UNIX commands and in the following a brief summary of the commands used in the scripts is given Description Copy one file into another Rename a file or directory dump the content of a file to screen dump the content of file 1 into file 2 dump content of filel behind existing content of file 2 append create a directory folder change directory directory path one level up directory path two levels up directory path one level up and one down Environmental variable with name NAME Show me the content of the environmental variable whit name NAME Stream Editor Delete file s Delete directory List files List all files with extension fem Table 3 3 1 UNIX commands overview Release Notes USFOS version 7 7 SINTEF 2000 04 0
24. nd add selected load ae a ny en te dA Ns PP TP PEN MM Script for assembling USFOS input and run USFOS e Usage go parli Dato parl Support Structure par2 Load definition A cp str Main_Structure stru fem cat str sl gt gt stru fem E Run USFOS and save results in unique directories Create Directory Move stru fem and load fem into actual Case_Dir for backup purpose Table 3 6 1 Content of script file go which assembles input files amp runs USFOS Support go Spring Support go Spring Support_ 1 go Spring Support 1 go Spring Support_ 2 go Spring Support 2 go Spring Support z Loa Nodel Load Node3 Load Node5 Load Nodel Load Node3 Load Nodeb5 Load Table 3 6 2 Content of script file run all which executes the script go After the script run all is completed 6 new file folders directories are created see Figure 3 6 2 All directories contain the actual assembled input stru and load the result files res Release Notes USFOS version 7 7 SINTEF 2000 04 01 15 File Folder File Folder File FEM File File Case Spring Supporn 1 Madel Load File Folder Case Spring Supporn 1 Made3 Load File Folder Case Spring Supporn 1 Made5 Load File Folder Case Spring Supporn 2 Madel Load File Folder Case Spring Support 2 Made3 Load File Folder Case Spring Support 2 Made5 Load File Folder
25. onstru elem fem echo Type i gt gt nonstru elem fem fi Add to file echo NONSTRU Element or gt gt nonstru elem fem if test count eg S then Tail echo i gt gt nonstru elem fem echo E QO E zi gt gt nonstru elem fem fi By Update counter count expr count X done Eps ee Pe TUS T LT echo Grabbing USFOS master control file from model cp model head fem echo Adds nonstru commands i cat nonstru elem fem gt gt head fem echo Creates Case identifier S1 on head fem d etc substitute CASEID S1 head fem echo Grabbing USFOS stru amp load file from model cp model stru fem cp model load fem echo and start USFOS i etc run_usfos gt run log echo and POSTFOS s etc run postfos SSCRATCH res gt gt run log echo m m echo Saves Global History on current directory di echo m m echo m m echo m m echo m m mv SSCRATCH res pri Global History mv SSCRATCH res status text E Table 3 8 4 Script file elmdel Release Notes USFOS version 7 7 SINTEF 2000 04 01 22 SINTER 23 4 New Features 4 1 Group definition a Groups are introduced in the latest USFOS version 7 7 a A group is identified by its ID which is a number up to 8 digits a Elements become members of groups and the same element may participate in several groups a The nodal points to which the elements are attached becomes
26. pt was executed In may cases only a small fraction of the entire input is different from one case to another Instead of making lots of copies of near 100 equal files the key in this example 1s to show how the input files could be composed by common information some special information Common information Q Control file head fem QO Main structure located in str Main Strucutre a Main load located in loa Main Load Special information Q Support Structure str spring Support 1 and _2 Q Special Load l loa Nodei_Load Contents of Example_3_Assembling_Files File Folder File Folder FEM File File File Figure 3 6 1 Content of file folder before running script run all The idea 1s as follows a Use the control file head fem in all cases a Compose a structural file consisting of the common Main_Structure and the special support and assemble the complete structural model in the file stru fem a Compose a load file which should consist of the common load file Main Load and the special nodal load and collect all load info in the file load fem a Create a new unique directory below current directory for each case with informative name reflecting the actual case a Run USFOS an save stru and load files result files on the actual directory Q Create script go for running on case and run all for running all 6 combinations In Table 3 6 1 the script with name go 1s described in detail as lt appears In the examp
27. r UFO file format In some cases both SESAM and UFO formats are given for the same example and then the stru file has a postfix u for UFO and s for SESAM Any of the two variants stru_u fem or stru s fem should produce the same results The USFOS control parameters are unaffected by the file format used to describe the structure and loads See also Chapter 3 Contents of Examples PC beam S grup C scripts wave cnl J calumn CJ grup 2 E small wave jac coroload J grup wav J ssh cantilever wave maexwav damp 1 3 joint E ssh col i B zayas damp 2 Joint API spri Jssh col pipe Jdyn drap C Joint amp PI spri crack Cd ssh jac dyn_eig Joint_User_Spri E strain_fract 1 dyn exp tri shall 1 dyn imp tri shall 2 J dn impl Jti shell joint dyn impe B tri_ shall Iaad J dyn_quak E psi_ H Unit Check etc psi E User Spri Figure 2 4 1 Example folders available for UNIX and NT PC Contents of scripts Example 1 Fixed Mameaes File Folder J Example 2 Variable_Names File Folder C Example 3 amp ssemhling Files File Falder Example 4 Modifying Master Input File Folder LJ Example 5 Redundancy Analysis File Falder Figure 2 4 2 Contents of Script folder available for UNIX and NT PC 3 Efficient use of USFOS 3 1 General Seldom only one USFOS analysis is performed for a given problem The more typical use is repeated runs due to several load cases parametric sensibility study model change
28. se the different groups include exclude The image to the right shows the full model and by excluding all groups as seen in the Specify Clip Group menu the image to the right appears If the NONSTRU command in Table 4 2 2 is activated note that the passives the command only the elements in the image to the right remains structural but loads are attracted on the full structure image to the left Release Notes USFOS version 7 7 SINTEF 2000 04 01 21 gt lt Specify Clip Group Geometry Group no 1000 Geometry Group no 2000 Geometry Group no 3000 Geometry Group no 16319 Geometry Group no 16219 LII A sea Is EU deron cud E ipis c pmo i 5 La C Include matching element s y Exclude matching element s EENG qe E 7 v i Mig De tt s m b Specify Clip Group Geometry Group no 1000 Geometry Group no 2000 Geometry Group no 3000 Geometry Group no 16219 C Include matching element s Exclude matching element s Ok EXER Figure 4 2 3 Edit Clip Group Useful USFOS commands for the model repair work Q GROUPDEF i Define element groups a GROUPNOD i Add nodes to groups guide loads towards nodes O NONSTRU Define elements nonstructural QO STRUCTEL Define elements structural override NONSTRU for some elem Q LIN ELEM Define element linear elastic with and without elastic buckling Release Notes USFOS version 7 7 SINTEF 2000 04 01 SINTER 28 4 3 Joint classificat
29. third variant of the fixed name script g03 indicates a first try to organise an analysis series involving several versions of the structural file f ex intact and damaged and several loads f ex nw J00yr nw 1000yr sw IO00yr sw 1000yr etc This leads to the next example which will give an example on how a slight modified go3 could be used for many different analyses 3 5 Example 2 Varying USFOS input file names The fixed name script go3 described above is slight modified Instead of defining the file names 100 some of the file name is substituted by the keywords 1 and 2 It s possible to give input parameters to UNIX scrips and 1 is parameter no 1 2 is parameter no 2 etc SUSFOS HOME bin usfos 15 ENDIN Head S51 2 model 1_stru sed loads OZ Di temp res S152 ENDIN Table 3 5 1 Content of script file go with varying input file names By typing go intact nw I00yr the same analysis as described under example 1 go3 will be performed Release Notes USFOS version 7 7 SINTEF 2000 04 01 SINTER 12 The 1 variable will be expanded to intact inside the script and 2 will be expanded to nw l00yr which gives the actual file names Control file head_intact_nw_10Oyr Struct file model intact_stru Load file loads nw 100 yr Result file D temp res intact nw 100yr A script file may not only refer to UNIX commands it s possible to refer to other script files as
30. well This leads to next level in script programming defining a top level script which refers to user defined script s If f ex one analysis series should consist of a number of different structural conditions different load directions and conditions the following script named rum all would run through all 16 cases without need for any human interference i Rt th th hd a Script for running 2 structural conditions 4 load directions and a 2 load conditions Totally 2x4x2 16 cases m SE L E a E E E Structure Load go intact nw_100 go intact sw 100 go intact se 100 go intact ne 100 go intact nw 10000 go intact sw_10000 go intact se 10000 go intact ne 10000 go damaged nw 100 go damaged sw 100 go damaged se 100 go damaged ne 100 go damaged nw 10000 go damaged sw 10000 go damaged se 10000 go damaged ne 10000 End of S rint File Table 3 5 2 Content of level 2 script file run all which refers to go Release Notes USFOS version 7 7 SINTEF 2000 04 01 SINTER 13 3 6 Example 3 Assembling input files before USFOS analysis In the previous examples all input files were complete before the scri
31. white text an black background and with size 24 lines 80 columns To modify the window point on the blue top frame of the window and press the right hand button The menu Figure 3 2 2 appears Figure 3 2 1 The default NutCracker Window layout estore Move Size Minimize Maximize Close Edit Properties c3 Figure 3 2 2 Menu Release Notes USFOS version 7 7 SINTEF 2000 04 01 SINTER Select Properties and the select colors menu shown in Figure 3 2 3 appears Select screen text and screen background among the indicated colours The light grey background together with black text is a good combination UNIX Properties X Options Font Layout Colors C Screen Text Selected Color Values Screen Background Red po 4 C Popup Text Green tb C Popup Background Blue p 4 03 01 92 a3 n1 92 OK Cancel Help Figure 3 2 3 Defining screen and text colour The default window has no screen buffer has no scroll bar but the buffer sizes In vertical number of lines and horizontal number of columns are possible to specify under the layout menu see Figure 3 2 4 Type in or us the arrow the actual sizes which here is set to 132 2048 The window size when it pops up is set to 80 40 When the OK button is pressed the menu shown in Figure 3 2 5 appears Select Modify Shortcut to save the settings permanently UNIX Properties Xx Options Font Layout Co
32. y as the script file gol and results are stored in the same directory As USFOS accepts input from one two or 3 files it s possible to leave up to two file names blank as shown in Table 3 4 2 where the load file is left out SUSFOS HOME bin usfos 15 ENDIN head stru res ENDIN Table 3 4 2 Content of script file go2 with only head and stru input files Release Notes USFOS version 7 7 SINTEF 2000 04 01 SINTER E It is possible to access files located on other directories than the directory where the script go is located and started from Table 3 4 3 describes the case where some files are located on different directories SUSFOS HOME bin usfos 15 ENDIN head intact nw 100yr model intact_stru loads nw_100yr D temp res intact nw 100yr ENDIN Table 3 4 3 Content of script file 903 with input files located on different directories In this case the control file head intact nw 100yr fem is located on same directory as the script file and where the script is started from The structural file stru fem 1s located in the directory model which is located on same level besides the current directory and the file is named intact stru fem The load file ls located on an other directory also on same level as the other two with name loads in a file with name nw J00yr fem The results are saved on the D disc on a directory named temp and file res nw 100 raf The
Download Pdf Manuals
Related Search