Installation.ins

8/13/2019 Installation.ins

1/24

SACS

SACSStructural Analysis System Installation

Release 5: Revision 8

SACSStructural Analysis

System Installation

RELEASE 5

USERS MANUAL

ENGINEERING DYNAMICS, INC.

2113 38TH STREET

KENNER, LOUISIANA 70065-3500

U.S.A.

No part of this document may be

reproduced in any form, in an

electronic retrieval system or

otherwise, without the prior

written permission of the publisher.

Copyright 2005 by

ENGINEERING DYNAMICS, INC.

Printed in U.S.A.


2/24

SACS


Release 5: Revision 8


3/24

SACS


i Release 5: Revision 8

TABLE OF CONTENTS

1.0 SYSTEM OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.1 SYSTEM REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.2 USER INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.3 SYSTEM TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.3.1 Local System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

1.3.2 Network System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

1.4 SECURITY KEY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

1.4.1 Single User Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

1.4.2 Network Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

1.5 INSTALLATION TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

1.5.1 Local Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

1.5.2 Network Server Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

1.5.2.1 Remote Analysis Server Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.5.3 Network User (Client) Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.5.3.1 Remote Analysis Client Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.5.4 Network Key Server Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.6 ON-LINE DOCUMENTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.6.1 Adobe Acrobat Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.6.2 Adobe Acrobat Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2.0 SACSSYSTEM INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.1 INITIAL INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.1.1 User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.1.2 Installation Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.1.3 Security Key Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.1.3.1 Network User (Client) Key Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.1.3.2 Key Server Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.1.4 Remote Analysis Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.1.4.1 Remote Analysis Client Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.1.4.2 Remote Analysis Server Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.1.5 Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.1.6 Review Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.1.7 System Default Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.1.8 Restarting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.2 POST INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.2.1 Modify Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.2.2 Repair Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.2.3 Remove Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.3 MANUAL PROCEDURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.3.1 Installing Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.3.1.1 Program Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.3.1.2 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.3.1.3 SACSAcrobat Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.3.1.4 Local Key Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.3.2 Restarting the Key Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.0 USING THE SACSSYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3.1 UPDATING THE SECURITY KEY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16


4/24

SACS


ii Release 5: Revision 8

3.2 CONFIGURING THE SACSSYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3.3 SACSKEY SERVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3.4 INSTALLATION TEST DEMOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3.4.1 Demo Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17


5/24

SACS


1 Release 5: Revision 8

1.0 SYSTEM OVERVIEW

1.1 SYSTEM REQUIREMENTS

To execute the SACS

Structural Analysis System suite of programs on a PC, thefollowing minimum hardware configuration is recommended:

Pentium4 or higher central processing unit(CPU).

512 megabytes (Mb) of RAM

WindowsXP Professional or Windows2000 Professional.

Minimum 1 Gb of free hard disk space.

128 Mb RAM or greater video card with 800x600 or higher video resolution.

USB/Parallel port for software key (transparent to external devices).

DVD/CD-ROM drive (for installation and documentation only).

Note: The system performance is a function of the model size and theamount of available resources. For optimal performance, availableRAM should not fall below 50% of the total amount of RAM present.The following equation can be used to determine the amount of freeRAM required for a particular model to be used in the interactiveprogram modules:

RAM in Mb = 20+[(Joints*40) + (Elements*200) + (Loads*305)] / 106

Network Server and Network Client Installations require the following:

TCP/IP.

100BaseTX Ethernet Network interface card.

Local Area Network.

Note: The SACSsystem supports Local Area Networks only. For optimal

performance, all users of the SACSNetwork Key and the SACS

Key

Server should reside on the same Ethernet segment. Wide AreaNetworks (networks where the Server and User are separated by a

BRIDGE, ROUTER, remote access connection, or other WAN enablingdevice) are not supported.

Network Client Installations with the Remote Analysis Client option have additional

requirements as follows:

SACSSite Licensed key.

WindowsXP Professional or Windows2000 Professional.

Network Server Installations with the Remote Analysis Server option have additional

requirements as follows:

SACSSite Licensed key.

WindowsXP Professional, Windows2000 or WindowsServer 2003.

1.2 USER INFORMATION

Each installation requires user information such as name, company and an installation

Serial ID provided with the installation CD.

1.3 SYSTEM TYPE

The SACSStructural Analysis System may be installed as a local system or as a

networked system. Installation requires full administrative rights on the computer/domain

to which the system is being installed.


6/24

SACS



1.3.1 Local System

A Local system is a system where the SACSsuite is located on the local computer and

is only available for use on that computer. It requires a security key on the local computer

or access to a network security key.

1.3.2 Network System

A Network system is a system available for use by any computer attached to the local

area network. The SACSprograms may be located on the network server or on the local

computer. It requires that a network security key be attached to a computer on the

network or that a single user security key be attached on the local computer.

1.4 SECURITY KEY

The SACSStructural Analysis System system requires that a SACSkey be attached to

a USB or parallel port. The key is transparent to any other device connected to the port.

1.4.1 Single User Key

A Single User Key allows the SACSsystem to be executed on the local machine only.

These keys, designated by serial numbers beginning with the letters EDI and ending

with the letter S, must be attached to the local machines USB or parallel port.

Note: The single user key must be the first device attached to themachines USB or parallel port. Only one NetSentinel-C key may beattached to a specific parallel port.

1.4.2 Network Key

Network keys allow the SACSsystem to be executed by any computer attached to the

network. These keys, designated by serial numbers beginning with the letters EDI and

ending with the letter N, may be attached to any machine connected to the network.

Note: The machine to which the network key is attached must contain thekey security software and the network key must be the first deviceattached to the machines parallel port. Although any number ofNetSentinel-C keys may be connected to a network, only oneNetSentinel-C key may be attached to a specific parallel port.

1.5 INSTALLATION TYPE

Four types of SACSSystem installations may be performed; Local, Network server,

Network User (Client) or License Key server.

1.5.1 Local Installation

The Local Installation is used to install the SACSsuite on the local machine. It requires

that a single user key be attached to the local computer or that a network key be attached

to either the local computer or to a computer on the network.

1.5.2 Network Server Installation

The Network Server Installation is used to install the SACSprograms and optionally the

key security software on computer to be used as a network server.


7/24

SACS



Note: The network server system will be available to any computer on thenetwork.

1.5.2.1 Remote Analysis Server Option

The SACSRemote Analysis Server option is used to setup the server as a RemoteAnalysis Server. This enables clients with the Remote Analysis Client option to use the

CPU of the server for analysis execution. This option is only available with Site Licensed

network systems.

1.5.3 Network User (Client) Installation

The Network User Installation is used to install the SACSsystem configuration files and

local components on a machine which is attached to a Windowsnetwork. This system

requires that a single user key be attached to the local computer or that a network key be

attached to either the local computer or to a computer on the network.

Note: The network user installation is typical for client computers

attached to the network.

1.5.3.1 Remote Analysis Client Option

The SACSRemote Analysis Client option is used to setup the computer as a Remote

Analysis Client. This enables the computer to use the CPU of the Remote Analysis

Server for analysis execution. This option is only available with Site Licensed network

systems.

1.5.4 Network Key Server Installation

The Key Server Installation is used to install the key security software on the machine

that is to be used as the key server on a Windowsnetwork. The key security software

must be installed on the computer to which the key is attached.

For Windowskey server machines, the installation must be performed on the computer

to which the key will be attached.

1.6 ON-LINE DOCUMENTATION

On-line documentation is available in Adobe PDF format. Accessing the SACS

documentation requires a SACSkey, Adobe Acrobat and the SACSplug-in for the

Acrobat reader. The documentation files require ~100 Mb of disk space and may be

installed on a network server, on the local computer or may be accessed directly from the

CD.

Note: Acrobat Reader and the SACS

plug-in must be installed on thelocal computer regardless of the location of the documentationfiles. The plug-in installation is included as part of the EnableLocal Viewing option.

1.6.1 Adobe Acrobat Reader

An Adobe Acrobat Reader installation is included as part of the SACSinstallation. By

default, Acrobat Reader is installed if the Enable Local Viewing option is selected and a

previously installed version of Acrobat Reader is not detected.


8/24

SACS



Note: The setup program can only install Adobe Acrobat Reader on thelocal computer on which the installation program is running.

1.6.2 Adobe Acrobat Plug-in

The SACSplug-in for the Acrobat reader is installed as part of the documentationinstallation if a previously installed version of Adobe Acrobat is found or is installed as

part of the SACSinstallation.

Note: If a new version of Adobe Acrobat is installed after the SACS

installation, the plug-in must be installed again using the RepairPost Installation facility.


9/24

SACS



2.0 SACSSYSTEM INSTALLATION

The SACSRelease installation CD contains the full SACSStructural Analysis System.

The installation program has two modes; initial installation mode and post installation

mode.

Initial Installation -allows for the initial installation of the SACSsystem, including

SACSprogram modules, SACSsystem files, SACSon-line document PDF files and

the Adobe Acrobat plug-in required to access the documentation on-line.

Post Installation-allows for modifying, repairing or removing an existing installation.

Installation and use of a Local system requires either a single user key attached to the

parallel port on the local computer or access to a network key while Network systems

require that a security key be attached to any computer on the local network.

2.1 INITIAL INSTALLATION

To install the SACSsystem, insert the CD and type drive:SETUP (where drive: is the

CD-ROM drive letter).

2.1.1 User Information

Upon beginning the installation, user information such as name, company name and the

Serial ID provided as part of the release shipment must be entered. The Serial ID must be

entered exactly as it appears in order to continue.


10/24

SACS



2.1.2 Installation Type

Select the type of installation.

Check the Install Online Manuals check box if the on-line documentation PDF files areto be installed. Check the Enable Local Viewing check box to install the SACSplug-in

and install Acrobat Reader if not already installed.

2.1.3 Security Key Details

Network User (Client) and Key Server installations require specification of security key

details. Security details are required for a Network Server installation if key server

software is to be installed as part of the network server setup. Local installations require

no security key details.

2.1.3.1 Network User (Client) Key Name

For Network User (Client) Installations, a network key configured as part of a previously

installed Key Server or a Network Server installation will be accessed by the SACS

system.

Enter the number of the SACSnetwork key to be accessed. This number beginning with

EDI, ends with the letter N and may be found on the key.


11/24

SACS



2.1.3.2 Key Server Operating System

The Key Server Installation and the Network Server Installation with the Install Key

Server option installs the SACSSecurity Key software on the machine that is to beused as the security key server.

For Windowskey server machines, the installation must be performed on the computer

to which the key will be attached. For Novell 4.11 key servers however, the installation

pushes the key server software to a Novell 4.11 server from a client machine.

Select the key server operating system on the Operating System dialog.

2.1.4 Remote Analysis Option

Site licensed network keys allow for remote analysis capabilities where the CPU of an

analysis server machine can be used to perform analyses launched from a client machine.

2.1.4.1 Remote Analysis Client Option

The SACSRemote Analysis Client option is used to setup the computer as a Remote

Analysis Client enabling the computer to use the CPU of the Remote Analysis Server for

analysis execution. The Remote Analysis Client capabilities can be installed as part of the

Network User (Client) Installation by picking the Install Remote Analysis option.


12/24

SACS



2.1.4.2 Remote Analysis Server Option

The SACSRemote Analysis Server option is used to setup the computer as a RemoteAnalysis server enabling the client computers to use the CPU of the Remote Analysis

Server for analysis execution. The Remote Analysis Server capabilities can be installed

as part of the Network Server Installation by picking the Install Remote Analysis

option.

After the network server installation copies files to the server, Remote Analysis Server

account information is required in order to configure the Remote Analysis Server.

Note: The Remote Analysis Server account must have administrativeprivilege on the server machine and have full write privilege tothe local directory where the remote analyses will be executed.

Choose the account from the Account name list box to use an existing account.


13/24

SACS



Choose the Create New Account button to add a local account. Enter the user name and

password for the account to be created.


14/24

SACS



2.1.5 Destination

Specify the destination of the selected components. The Local Folder pertains to any

components and configuration files required on the local machine, while the Programfolder pertains to the location of the SACSprogram modules and other system files. The

Documentation Folder specifies the location of the online documentation PDF files.

Note: Some of the destination folders may not appear if they are notapplicable for the type of installation selected.

2.1.6 Review Settings

Prior to installing the SACSprogram modules, the setup program checks your system

configuration and shows current installation settings. Click the Back button to change

settings or the Next button to start copying files.


15/24

SACS



2.1.7 System Default Settings


16/24

SACS



The setup program can configure default settings for analysis units, section library and

joint coordinate method.

2.1.8 Restarting

After the installation is complete, the computer must be restarted before the SACS

system can be used. Select the appropriate restart option then click Finish to complete the

installation.


17/24

SACS



2.2 POST INSTALLATION

Once initial installation has been completed, post installation or maintenance options are

available by rerunning the installation program. Maintenance options include Modify,

Repair and Remove capabilities.

2.2.1 Modify Option

The modify option allows the user to install or uninstall selected components of the

SACSsystem. To use the Modify option, select the Modify radio button then click the

Next button.


18/24

SACS



Select the system components to be installed by checking box next to the component.

Clear the check box next to components that are to be uninstalled.

2.2.2 Repair Option

The Repair option allows the user to reinstall all programs using the settings from the

previous installation. To use the Repair option, select the Repair radio button then click

the Next button.

2.2.3 Remove Option

Select the Remove radio button to remove all installed components.

Note: The Remove option does not uninstall components from Novell Serverinstallations. To uninstall the SACS

program system from a Novell

Server, delete the SACSprogram directory from the server.

2.3 MANUAL PROCEDURES

Components of the SACSsystem may require manual intervention in some situations in

order to install. The following section details instructions for manual installation.


19/24

SACS



2.3.1 Installing Components

2.3.1.1 Program Modules

Program modules and required components can be reinstalled using the Modify postinstallation feature and selecting the desired modules.

2.3.1.2 Documentation

Documentation in the form of PDF files can be accessed directly from the CD, from a

network drive or from the local hard drive. The document PDF files can be reinstalled

using the Modify post installation feature or manually by copying the files directly from

the Installation CD. To install manually:

Copy the files *.pdf from the system/docs directory on the SACSCD to

sacs_local_directory\docs where sacs_local_directoryis the local SACS5.2

directory (i.e. Program Files\SACS52).

Note: In order to access the documentation the SACSplug-in isrequired.

2.3.1.3 SACSAcrobat Plug-in

Viewing SACSdocumentation requires the presence of the SACSsecurity key and the

key plug-in. To install the plug-in manually:

Copy the file sacs60.api from the SACSCD system\docs\plug_ins directory

to the Adobe plug_ins directory.

Note: Typically, the Adobe plug_ins directory is located inC:\Acrobat3\Reader\ for Acrobat Reader 3, C:\ProgramFiles\Adobe\Acrobat x.0\Reader\ for Acrobat Reader x.0 orC:\Program Files\Adobe\Acrobat x.0\Acrobat\ for Acrobat Writer.

2.3.1.4 Local Key Drivers

Local security key drivers are required for SACSto communicate with a key attached to

the local parallel port or USB port. To install the security key drivers manually:

Launch the application setup.exe from the system\spro directory on the

SACSinstallation CD.

Follow the on screen instructions to install the driver.

Restart the computer to activate the driver.

2.3.2 Restarting the Key Service

For machines running Windows2000/XP, the key service cannot be stopped without

first unloading the service. The following steps are required to restart the service: Unload the service by typing nssrvice /u at the command prompt.

Reboot the computer.

Launch the application startkey.exe from the SACSlocal directory (i.e.

Program Files\SACS52).


20/24

SACS



3.0 USING THE SACSSYSTEM

3.1 UPDATING THE SECURITY KEY

Executing the SACS

system requires a SACS

security key authorized for this or asubsequent release of the SACSsystem. Security keys can be updated using security

codes provided by EDI.

The SACSsystem Executive can be used to update keys provided an update key code

file is available. To update the key, place it on the parallel port and launch the Executive.

Select the Update Key button and pick the file containing the key codes.

After the key has been updated, click the Retry button to launch the SACSsystem

Executive.

3.2 CONFIGURING THE SACSSYSTEM

To configure the SACSsystem or to execute any of the SACSprograms, start the

SACSsystem Executive by double clicking on the SACSExecutive icon. This is the

graphical interface to the system that controls all interactive, batch, print and plot

executions along with system configuration. The basic system settings are found under

the Settings menu option. Please refer to the SACSExecutive Manual for more details.

3.3 SACSKEY SERVER

For network installations, any computer attached to the network may be used as the key

server provided that the key security software is running on the machine. If the key ismoved to a different machine, the key security software must be deactivated or

uninstalled from the original server. The key security software must then be installed on

the new key server.

3.4 INSTALLATION TEST DEMOS

A series of installation test and verification demonstrations are contained on the

installation CD. These demonstration cases should be used to ensure that the system has

been installed successfully.


21/24

SACS



The following is a list of the available demonstration cases:

DEMO1 Seastate, SACS IV, Joint Can, Fatigue and MTO

DEMO2 Seastate, Dynpac, and Dynamic Response (Earthquake)

DEMO3 Seastate, PSI and Joint CanDEMO4 Seastate, Dynpac, Wave Response (Deterministic)

DEMO5 Launch

DEMO6 Flotation

DEMO7 Tow

DEMO8 SACS IV Gap element analysis

DEMO9 SACS IV Superelements

DEMO10 Large Deflection - Static

DEMO11 Rigid Analysis

DEMO12 Dynpac, Wave Response (Random)

DEMO13 SACS to WAMIT and SACS to MORA

DEMO14 Collapse

To execute a demonstration case, execute the run file (.RUN) included with the data files

from the File/Run feature or the SACSDemo Utility in the Executive. The output print

file contains the results of each execution for the latest release of the programs. It is

recommended to run the demonstration data files through the newly installed programs to

confirm the installation is complete before the programs are used on a production basis.

3.4.1 Demo Details

The following details the files used in each demonstration case.

DEMO 1: Standard Static Analysis

SACINP.DM1 - Seastate and SACS IV data

JCNINP.DM1 - Joint Can data

FTGINP.DM1 - Fatigue data

MTOINP.DM1 - Material Take Off data

SACLST.DM1.std - Output listing of Seastate, SACS IV and Joint Can run

MTOLST.DM1.std - Output listing of Material Take Off run

SACDM1.RUN - SACS run file

MTODM1.RUN - Material Take Off run file

DEMO 2: Earthquake Analysis

SEAINP.DM2 - Seastate and SACS IV data

DYNINP.DM2 - Dynpac data

DYRINP.DM2 - Earthquake data

DYNLST.DM2.std - Output listing for Dynpac analysis

DYRLST.DM2.std - Output listing for Earthquake analysis

DYNDM2.RUN - Dynpac run file

DYRDM2.RUN - Earthquake run file

DEMO 3: Pile/Structure Interaction

SACINP.DM3 - SACS IV data

PSIINP.DM3 - PSI data

JCNINP.DM3 - Joint Can data


22/24

SACS



PILINP.DM3 - Single Pile data

PSILST.DM3.std - Output listing for PSI and Joint Can run

PSINPF.DM3.std - Neutral Picture file (contains plots, use Prevue)

PILLST.DM3.std - Output listing for single Pile run

PSIDM3.RUN - PSI run filePILDM3.RUN - Pile run file

DEMO 4: Deterministic Wave Response

SACINP.DM4 - Seastate (Hydrodynamic modeling), SACS data

DYNINP.DM4 - Dynpac data

SEAINP.DM4 - Seastate data (Wave generation)

WVRINP.DM4 - Wave Response data

DYNLST.DM4.std - Output listing for complete run

WVRLST.DM4.std - Output listing for complete run

WVRNPF.DM4.std - Neutral Picture file (contains plots, use Prevue)

DYNDM4.RUN - Dynpac run file

WVRDM4.RUN - Wave Response run file

DEMO 5: Launch of Jacket from Barge


LNHINP.DM5 - Launch data

LNHLST.DM5.std - Output listing for complete run

LNHNPF.DM5.std - Neutral Picture file (contains plots, use Prevue)

LNHDM5.RUN - Launch run file

DEMO 6: Upending Analysis


FLTINP.DM6 - Flotation data

FLTLST.DM6.std - Output listing for complete runFLTNPF.DM6.std - Neutral Picture file (contains plots, use Prevue)

FLTDM6.RUN - Flotation run file

DEMO 7: Jacket Tow Analysis


TOWINP.DM7 - Tow data

TOWLST.DM7.std - Output listing for complete run

TOWDM7.RUN - Tow run file

DEMO 8: Gap Element Analysis


GAPINP.DM8 - Gap dataSACLST.DM8.std - Output listing for SACS IV and Gap run

SACDM8.RUN - Gap run file

DEMO 9: Superelement Analysis

SACINPDK.DM9 - SACS IV Deck Superelement

SACINPTP.DM9 - SACS IV Top Superelement

SACINPBT.DM9 - SACS IV Bottom main model

SACLSTDK.DM9.std - Output listing for SE creation of deck

SACLSTTP.DM9.std - Output listing for SE creation of top


23/24

SACS



SUBLSTMR.DM9.std - Output listing for Merging DECK and TOP SEs

SACLSTBT.DM9.std - Output listing for Main Structure analysis BOTTOM

model with DECK and TOP SEs added:

SUBLSTET.DM9.std - Output listing for expansion of TOP SE

SUBLSTED.DM9.std - Output listing for expansion of DECK SESACD9DK.RUN - SACS IV Deck Superelement run file

SACD9TP.RUN - SACS IV Top Superelement run file

SUBD9MR.RUN - Superelement Element Merge run file

SACD9BT.RUN - SACS IV main model run file

SUBD9ET.RUN - Expand Top Superelement run file

SUBD9ED.RUN - Expand Deck Superelement run file

DEMO 10: Large Deflection Analysis

SEAINP.D10 - Seastate and SACS IV data

SACLST.D10 - Output listing for SACS and Large Deflection run

SACD10.RUN - Large Deflection run file

DEMO 11: Rigid Analysis

SEAINP.D11 - SACS IV data

DYNINP.D11 - Dynpac data

RGDINP.D11 - Rigid data

DYNLST.D11.std - Output listing for Dynpac run

RGDLST.D11.std - Output listing for Rigid run

DYND11.RUN - Dynpac run file

RGDD11.RUN - Rigid run file

DEMO 12: Random Wave Analysis

SACINP.D12 - SACS IV data

DYNINP.D12 - Dynpac dataSEAINP.D12 - Seastate data (Wave generation)

WVRINP.D12 - Random Wave Response data

DYNLST.D12.std - Output listing for Dynpac run

WVRLST.D12.std - Output listing for Random Wave Response run

WVRNPF.D12.std - Neutral Picture file (contains plots, use Prevue)

DYND12.RUN - Dynpac run file

WVRD12.RUN - Wave Response run file


24/24

SACS


DEMO 13: MORA and WAMIT Interface

SACINP.D13 - SACS IV data

MORA Analysis:

S2MINP.D13 - SACS to MORA input data

M2SINP.LOD - MORA to SACS input data for load generationS2MLST.D13.std - SACS to MORA Output Listing File

S2MD13.RUN - SACS to MORA run file

WAMIT Analysis:

S2WINP.D13 - SACS to WAMIT input data

W2SINP.LOD - WAMIT to SACS input data for load generation

W2SINP.RAO - WAMIT to SACS input data for RAO generation

S2WLST.D13.std - SACS to WAMIT Output Listing File

S2WNPF.D13.std - Neutral Picture file (contains plots, use Prevue)

S2WD13.RUN - SACS to WAMIT run file

DEMO 14: Collapse AnalysisSACINP.D14 - SACS IV data

CLPINP.D14 - Collapse input data

SACLST.D14.std - SACS Output Listing File

CLPLST.D14.std - Output Listing for Collapse

SACD14.RUN - Collapse run file

Date post:	04-Jun-2018
Category:	Documents
Upload:	anuj3936
View:	213 times
Download:	0 times

Installation.ins

Documents