Download / Install Overview

This page is the start­ing point for those who want to (a) down­load LST soft­ware prod­ucts for the first time, or (b) up­grade their ex­ist­ing in­stal­la­tions.

Table of Contents

1. Soft­ware Prod­ucts and Doc­u­men­ta­tion
   Con­tains a brief de­scrip­tion of the main LST soft­ware prod­ucts, with links to down­load pages for in­di­vid­ual prod­ucts. The in­di­vid­ual down­load pages con­tain in­stal­la­tion notes, and oth­er in­for­ma­tion about sup­port­ed plat­forms.
2. Prod­uct Li­cens­ing
   Con­tains a brief overview of li­cens­ing. There are links to in­for­ma­tion about:
   • How to re­quest a li­cense from LST
   • How to in­stall or up­grade net­work li­cens­es
3. Con­fig­ur­ing LS-DY­NA to Ac­cess Li­cens­es
   De­scribes how to con­fig­ure LS-DY­NA to ac­cess net­work and/­or node-locked li­cens­es.

1. Software Products and Documentation

These are the LST soft­ware prod­ucts and doc­u­men­ta­tion avail­able for down­load from this site.

• LST Man­u­als: old and new man­u­als can be down­loaded from this page.
• LS-DY­NA: all LS-DY­NA ex­e­cuta­bles can be found on this page.
• LSTC Bar­ri­er, Dum­my and Tire Mod­els: bar­ri­er, dum­my, and tire mod­els pro­vid­ed at no charge to LS-DY­NA cus­tomers
• LS-Pre­Post: an ad­vanced in­ter­ac­tive pro­gram for prepar­ing in­put da­ta for LS-DY­NA and pro­cess­ing re­sults from LS-DY­NA analy­ses.
• LS-OPT: a stand­alone De­sign Op­ti­miza­tion and Prob­a­bilis­tic Analy­sis pack­age with an in­ter­face to LS-DY­NA.
• LS-TaSC: (Topol­o­gy and Shape Com­pu­ta­tion) a tool for the topol­o­gy op­ti­miza­tion of non-lin­ear prob­lems in­volv­ing dy­nam­ic loads and con­tact con­di­tions.

Each of these com­po­nents must be down­loaded and in­stalled sep­a­rate­ly. LST pro­vides high­ly-op­ti­mized ver­sions of LS-DY­NA, tuned for a large va­ri­ety of hard­ware and op­er­at­ing sys­tems. For this rea­son, many builds of LS-DY­NA func­tion cor­rect­ly on­ly for a nar­row range of hard­ware and OS. So it is crit­i­cal­ly im­por­tant that users down­load a build of LS-DY­NA which most close­ly match­es their own hard­ware/­OS com­bi­na­tion.

2. Product Licensing (Network and Node-Locked)

LS-DY­NA is li­censed ac­cord­ing to how many cores on which the soft­ware may run at once. For ex­am­ple, an 8-core li­cense al­lows any of the fol­low­ing sce­nar­ios (and more):

• The user runs one job in par­al­lel on 8 cores;
• The user runs two jobs in par­al­lel on 4 cores each;
• The user runs up to 8 jobs on a sin­gle core.

Li­cens­ing schemes for LS-DY­NA:

1. Node-Locked Li­cense
   Per­mits the use of LS-DY­NA on a sin­gle ma­chine on­ly (or on a lim­it­ed num­ber of ma­chines). Please con­tact you sales rep­re­sen­ta­tive or chan­nel part­ner if you have ques­tions about the avail­abil­i­ty of node­locked li­cens­es.
2. Net­work Li­cense
   Per­mits the use of LS-DY­NA on all sup­port­ed plat­forms, up to a to­tal num­ber of li­censed cores. The LSTC Li­cense Serv­er must be run on a Unix, Lin­ux, So­laris, or Mi­crosoft Win­dows ma­chine. All ver­sions of LS-DY­NA con­nect through the lo­cal net­work to the LSTC Li­cense Serv­er in or­der to ob­tain per­mis­sion to run. When the max­i­mum num­ber of li­cens­es is ex­ceed­ed, LS-DY­NA is ei­ther placed in a queue to wait for the first avail­able li­cense, or LS-DY­NA ex­its ac­cord­ing to the user’s pref­er­ence.

License HOWTO Documents

1. In­stall a New Net­work Li­cense
   Unix/­Lin­ux/­So­laris /­ Mi­crosoft Win­dows
2. Up­grade Net­work Li­cens­es and/­or Li­cense Man­ag­er Soft­ware
   Unix/­Lin­ux/­So­laris /­ Mi­crosoft Win­dows.

3. Configuring LS-DYNA to Access Licenses

Accessing Network Licenses under Unix/Linux/Solaris

En­vi­ron­ment Vari­able Set­tings

LS-DY­NA can ob­tain a net­work li­cense from an LSTC Li­cense Serv­er us­ing en­vi­ron­ment vari­ables. En­vi­ron­ment vari­ables are spec­i­fied in dif­fer­ent ways, de­pend­ing on the user lo­gon shell:

  C-SHELL (csh or tc­sh)
      setenv VAR­NAME 'val­ue'
  Unix SHELL (sh or bash) or KO­RN SHELL (ksh)
      VAR­NAME='val­ue' 
      ex­port VAR­NAME

To use a net­work li­cense on­ly, set the en­vi­ron­ment vari­able LSTC_­LI­CENSE to ‘net­work’

    setenv LSTC_­LI­CENSE net­work

You must al­so spec­i­fy the host or IP ad­dress of the ma­chine where the li­cense serv­er is run­ning us­ing the LSTC_­LI­CENSE_­SERV­ER en­vi­ron­ment vari­able. The prop­er set­ting of this vari­able de­pends on whether or not you are us­ing the de­fault port for the li­cense serv­er, and whether you are us­ing a sin­gle li­cense serv­er, or a re­dun­dant tri­ad serv­er.

  1. SIN­GLE SERV­ER US­ING DE­FAULT PORT
        setenv LSTC_­LI­CENSE_­SERV­ER host_­or_­ip
  2. SIN­GLE SERV­ER US­ING OTH­ER PORT 'port'
        setenv LSTC_­LI­CENSE_­SERV­ER port@host_­or_­ip
  3. RE­DUN­DANT SERV­ER US­ING STAN­DARD PORTS
        setenv LSTC_­LI­CENSE_­SERV­ER '(serv­er1 serv­er2 serv­er3)'
  4. RE­DUN­DANT SERV­ER US­ING OTH­ER PORTS
        setenv LSTC_­LI­CENSE_­SERV­ER '(port1@serv­er1 port2@serv­er2 port3@serv­er3)'

Sin­gle quotes are re­quired for re­dun­dant servers in or­der to avoid mis­in­ter­pre­ta­tion of paren­the­ses. There are oth­er meth­ods for spec­i­fy­ing the li­cense serv­er, but set­ting these en­vi­ron­ment vari­ables over­rides all oth­er meth­ods.

LSTC_­FILE Li­cense File Di­rec­tives

LS-DY­NA can read serv­er in­for­ma­tion from a file named LSTC_­FILE. The best way to do this is to cre­ate/­ed­it a file named LSTC_­FILE in the same di­rec­to­ry as the LS-DY­NA ex­e­cutable. Add these lines to LSTC_­FILE

 #LI­CENSE_­TYPE: net­work
 #LI­CENSE_­SERV­ER: host_­or_­ip

DO NOT en­close host_­or_­ip with sin­gle quotes. As in the case of EN­VI­RON­MENT VARI­ABLES (above), there are four pos­si­ble ways to spec­i­fy ‘#LI­CENSE_­SERVER’. The ‘#’ char­ac­ter must ap­pear in the first col­umn of the line, with no space be­tween ‘#’ and LI­CENSE_­TYPE or LI­CENSE_­SERV­ER. The ef­fect of these lines is the same as set­ting the en­vi­ron­ment vari­ables

    setenv LSTC_­LI­CENSE net­work
    setenv LSTC_­LI­CENSE_­SERV­ER host_­or_­ip

Keep in mind that you can over­ride any set­tings found in LSTC_­FILE by di­rect­ly set­ting the en­vi­ron­ment vari­ables LSTC_­LI­CENSE and LSTC_­LI­CENSE_­SERV­ER. This is use­ful to know in cas­es where LSTC_­FILE con­tains in­cor­rect in­for­ma­tion, but you can­not change the file be­cause of per­mis­sion is­sues.

WARN­ING: Some text ed­i­tors do not au­to­mat­i­cal­ly cre­ate files with com­plete lines. Use “vi LSTC_­FILE” to check this. If you see [noe­ol] at the bot­tom of the vi win­dow, then there is no fi­nal end-of-line char­ac­ter in the file. If that hap­pens, then type “:wq” in vi to write the file and quit. Vi will add the prop­er eol char­ac­ter.

NOTE: If LSTC_­FILE is found in ‘/­usr/­lo­cal/­lstc’, then that file will be used in­stead, re­gard­less of whether or not a file named LSTC_­FILE is found with the LS-DY­NA ex­e­cutable. We no longer rec­om­mend plac­ing LSTC_­FILE in ‘/­usr/­lo­cal/­lstc’.

NOTE: If the LSTC_­FILE en­vi­ron­ment vari­able is set to a file name, then $LSTC_FILE is used instead of any file named LSTC_FILE found with the LS-DYNA executable. We recommend that you not set the LSTC_FILE environment variable, unless absolutely necessary.

Set­ting the LSTC_­FILE en­vi­ron­ment vari­able may be nec­es­sary if, for some rea­son, LSTC_­FILE can­not be found when placed with the ex­e­cutable. Then you must set the LSTC_­FILE en­vi­ron­ment vari­able to the ab­solute path­name of the file LSTC_­FILE. This should not hap­pen un­der or­di­nary cir­cum­stances.

Accessing Network Licenses under Microsoft Windows

1. Open the LS-DY­NA Man­ag­er Pro­gram
2. Se­lect Set LS-DY­NA ENV. Vari­ables from the Env Vari­ables menu
3. In the di­a­log that ap­pears, se­lect Net­work for the Li­cense Type
4. Spec­i­fy the name of the ma­chine run­ning the LSTC Li­cense Serv­er (if the serv­er is run­ning on the lo­cal ma­chine, en­ter lo­cal­host in the Net­work Li­cense Man­ag­er field)

The gen­er­al for­mat for the Net­work Li­cense Man­ag­er field varies ac­cord­ing to the type of serv­er con­fig­u­ra­tion you have: