ProCASt

Insert the front cover image in this header, then position and resize it !

ProCAST 2014.0 including Visual-Environment 9.6

Release Notes & Installation Guide

Shot Sleeve Modeling in High Pressure Die Casting

Low Pressure, Investment and Gravity Casting

Images courtesy of: Casati & CMS, Mofopress, Vulcan SFM

Ingot and Continuous Casting

ProCAST 2014.0 including Visual-Environment 9.6

RELEASE NOTES & INSTALLATION GUIDE

The documents and related know-how herein provided by ESI Group subject to contractual conditions are to remain confidential. The CLIENT shall not disclose the documentation and/or related know-how in whole or in part to any third party without the prior written permission of ESI Group.

© 2014 ESI Group. All rights reserved.

February 2014 CL/PRCA/14/01/00/A

RELEASE NOTES & INSTALLATION GUIDE (released: Feb-14)

ProCAST 2014.0 © 2012 ESI Group

FOREWORD

Dear Customer,

We are pleased to provide you with the multi-physics code ProCAST 2014.0 release. We are delivering one DVD containing ProCAST 2014.0 (parallel solvers for Windows (64) and Linux (64) systems) and Visual-Cast 9.6 version (the compatible environment). This version has undergone improved and consolidated product functionalities and contains new features. Please refer to the present release notes and to the Visual on-line user manual for more details about all new capabilities and corrections. In particular, we strongly recommend reading the What's New/Version 2014.0 or VE 9.6 Release Notes sections which detail all. These Release Notes only highlight a few specific developments. The new version supports a multiple rotation / translation approach for modelling continuous casting machine with different curvatures. The thermodynamic engine for material properties computation introduced in ProCAST 2013.5 has been improved by Computherm LLC and enhanced with the introduction and the support of the first Cobalt-based database. Moreover, the latest material databases have been embedded. A new wrap condition provides the ability to define a heat transfer coefficient upon the wrap layer thickness. This version supports the FOAMING injection process. The performance of tetra meshing is greatly improved thanks to a code optimization and multiprocessing. The Viewer allows now the slice and cutoff analysis as well as an export of some results in the native format of the forging product DEFORM. Note that the delivery of version 2014.0/9.6 requires a new FlexLM license file. We wish you a lot of success with this major release. If you have any questions or need further assistance, please do not hesitate to contact your local support team. In the meantime, the ESI Group's casting team remains sincerely yours. ESI GROUP CASTING TEAM

FOREWORD


i


CONTENTS INTRODUCTION

1

VISUAL-CAST

3

Enhancements ----------------------------------------------------------------------------- 3 Bug Fixes ------------------------------------------------------------------------------------ 6 Limitations ----------------------------------------------------------------------------------- 8 ProCAST Solvers 2014.0 Updates ---------------------------------------------------- 9

Main Updates ------------------------------------------------------------------------------9 Improve User Functions Capabilities -------------------------------------------------9 PanEngine for Material Properties Computation -----------------------------------9 CompuTherm Database Updates (Oct 2012 – Oct 2013) --------------------- 10 Other Updates---------------------------------------------------------------------------- 13 Limitations--------------------------------------------------------------------------------- 13

VISUAL-MESH (CAST)

15

VISUAL-VIEWER (CAST)

19

CORE DUMP TRACKER

25

LICENSING SYSTEM

27

Tetra Mesh -------------------------------------------------------------------------------- 15 New Toolbar for 2D Mesh Utilities --------------------------------------------------- 17 Quality and Performance of Surface Shading Improved ----------------------- 17

Enhancements --------------------------------------------------------------------------- 19 Bug Fixes ---------------------------------------------------------------------------------- 21 Known Issues ----------------------------------------------------------------------------- 22 Limitations --------------------------------------------------------------------------------- 22

Types of Licenses ----------------------------------------------------------------------- 27 Feature System -------------------------------------------------------------------------- 27 Context System -------------------------------------------------------------------------- 28 List of Compatible Contexts----------------------------------------------------------- 28

Token System ---------------------------------------------------------------------------- 28 Number of Tokens by Context ------------------------------------------------------- 28 Used Tokens in a Session ------------------------------------------------------------ 30

Synthesis----------------------------------------------------------------------------------- 31 List of Third Party Components Not Included in Either Context or Token -------------------------------------------------------------------------------------- 32 License Strategy Configuration ------------------------------------------------------ 33 License Strategy Manager ------------------------------------------------------------ 35

CONTENTS


ii


INSTALLATION GUIDE

37

Software Installation on Windows --------------------------------------------------- 37 Installation of the Software ------------------------------------------------------------ 37 Installation of the License ------------------------------------------------------------- 37

Software Installation on Linux -------------------------------------------------------- 41 Overview ---------------------------------------------------------------------------------- 41 CD-ROM Mounting Instructions ------------------------------------------------------ 42 Graphical Installation ------------------------------------------------------------------- 42 Installation of the License ------------------------------------------------------------- 46 Customization ---------------------------------------------------------------------------- 53

Software Installation on Linux -------------------------------------------------------- 55 Overview ---------------------------------------------------------------------------------- 55 CD-ROM Mounting Instructions ------------------------------------------------------ 56 Graphical Installation ------------------------------------------------------------------- 56 Installation of the License ------------------------------------------------------------- 60 Customization ---------------------------------------------------------------------------- 66

Getting Started --------------------------------------------------------------------------- 68 Starting the Software ------------------------------------------------------------------- 68 On-line Product Documentation ----------------------------------------------------- 68

AVAILABLE PLATFORMS AND PRE-REQUISITES

69

Product Availability ---------------------------------------------------------------------- 69 Availability of the ProCAST DMP Version----------------------------------------- 70 General Requirements ----------------------------------------------------------------- 71

CONTENTS


1


INTRODUCTION Visual-Environment 9.6 is an update release after VE9.5 to address specific requirements in the following applications: Visual-Cast is the single integrated environment for all your Casting needs. The preprocessor helps in model set-up, aided by definition of physics on topology and tailored process flowchart using integrated Visual-Process. Visual-Cast is also linked to Thermodynamic Databases for the automatic determination of the material properties. Visual-Mesh (Cast) is a complete meshing tool for Casting and other volume based applications. This supports a multi-model environment with model explorer and powerful display controls. It facilitates import of CAD and mesh data from various sources, repair CAD geometry, assembly of volumes, generation of surface mesh, validation and correction of surface mesh and finally generation of volume meshes. Visual-Viewer (Cast) is the visualization and plotting tool that helps in analyzing ProCAST and QuikCAST results data within an uniform interface. It performs automated tasks and generates customized reports, thereby increasing engineer productivity.

INTRODUCTION Enhancements


3


VISUAL-CAST ENHANCEMENTS •

Support for multiple rotation / translation for continuous casting simulation. It allows to model curved continuous casting machine with different curvatures. To activate new multi-radius accordion calculation, set “Accordion Reference” to “Backward” in Accordion Process Condition database.

•

Support of the newly proposed Material Co Based Alloy thermodynamic database in Material DB Editor.

VISUAL-CAST Enhancements



•

To support FOAMING injection process with ProCAST: o Density and Viscosity F (time) and User functions are introduced. o For Density, Gas concentration model is supported.

•

A QuikCAST Demonstrator is now supported. It allows to run basic QuickCAST cases from Visual-Cast. Please contact your local support team for more information. Number of digits for Interfaces and Boundary Conditions can now be managed from the option menu.

•


4


•

5


Wrap provides ability to define a heat transfer coefficient depending on thickness. In addition to heat transfer BC, a curve which defines a factor to the heat transfer based on thickness of wrap is added.



6


BUG FIXES • • • • • • • • • • • • • • • • • • • •

•

VISUAL-CAST Bug Fixes

iHTC depending on temperature was not working properly. This is now fixed. User function was not compiled when solver was launched without opening the case. This is corrected. CAFE model running will now write _mica.d when CAFE option is ON in the Volume Manager. In older versions this was controlled by option in Preference panel. If an element for a given alloy is not supported by Pan-Engine and MICRO, Data Checks and solver run will give a warning that such elements are ignored. Defining temperature in already defined velocity Process Condition was giving bad results. This is now corrected. You can now define units in the Rotation and Revolution Process condition. In Start Simulation / Options / Option 2, when using -V for verbose, was not working. This is now fixed. User functions defined in Velocity and Mass Source was not considered during solver run. This is now fixed. Run-List in Start Simulation was not working properly. This is now corrected. "Compute Weight" option is grayed out from right-click menu in volume manager, if volume type is not set. If JUNCTION is > 0 and FREESF 2, a warning is generated in Data Checks. A warning is also given when the job is submitted. In COINC interface, if alloy is slave and interface heat condition is defined as a function of temperature, a warning is generated in Data Checks. Pouring Cup Control parameters like height, box information are remembered. Interface group names are now based on the volume names. This makes the naming clear to the users. User functions associated to mechanical properties for stress analysis are now well taken into account. Computation of weight was not proper with different units. It is now corrected. When material is defined with specific heat, latent heat and Enthalpy properties, Enthalpy is given the preference. The specific heat and latent heat properties are deleted. In some cases when you import models saved in Visual-Cast 8.6, Enthalpy data defined in material was lost. This is fixed. Generic Workflow -> Stop Criterion panel was not updated from Simulation Parameters correctly. This is now corrected. When creating symmetry Process Condition on a Mile case after the creation of the Mile / Accordion Process Condition, a gap was seen at the accordion when viewing results. This is due to erase of nodes on symmetry planes of accordion / Mile. This is fixed. The stress Secant Thermal expansion input was wrong for Low-Carbon AISI 1008 in the public database. This is corrected.


• •

7


In Extract/Mapping GUI, the extracted temperature field is displayed with user selected temperature unit in 'Preferences' GUI. Die coating effect is now well taken into account while computing effective heat transfer at interfaces.

VISUAL-CAST Bug Fixes


8


LIMITATIONS •

• • • • • • • • • • • • •

VISUAL-CAST Limitations

The following are not supported in d.dat reading. o 2D Model - Loading will terminate in this case. o Extract of initial condition - Will continue to load, so it can be extract manually after loading such files using “Extract/Mapping” right click menu on volumes in explorer. o Reading d.dat files of ProCAST version below 2008.1 - Will continue to load. It allows checking and making necessary changes if required in GUI. Extraction/Mapping functionality is not supported for MILE cases. To run solver from "Start Simulation" GUI, the solver path must have solver version number. Ex. 2013.5 or 2013.0, etc. This path should not have any "." in the path other than version number. Loading d.dat files with special characters in material name may sometime fail in LINUX versions. Workaround: Edit such files and rename material by removing special characters. For defining "Run List" in "Start Simulation" having user functions, selected cases should belong to same drive. In "Start Simulation" -hostlist can be specified only in option1. In "Start Simulation" on Windows platform, avoid specifying both -hostlist in option1 and hostfile together. When several files are appended to the existing model, volume should be checked for unique name. Unique volume names should be maintained in order to update regions correctly. If mold and alloy are connected by a line of common nodes instead of interfaces, solver will throw error when launched. Workaround: Create COINC nodes at these locations in Visual-Mesh. Die Coating process conditions defined in Visual-Cast 9.0 are not properly loaded in Visual-Cast 9.6. In such files Die Coating process conditions should be re-assigned. Frequencies defined Ex. TFREQ, VFREQ cannot be changed when calling "Restart". Workaround: Use extract and define new TFREQ and VFREQ. User functions should be defined always in CGS units. .sm files (Ex. with enclosures for radiation problems) should be appended to the existing model only after loading/appending other files. The Stress calculations are not supported in new multi-radius accordion calculations.


9


PROCAST SOLVERS 2014.0 UPDATES Main Updates • •

• •

The EBFEM discretization method, introduced in ProCAST 2013.0, extended in 2013.5 has been improved in term of accuracy, robustness and speed. A first version (Beta) of EBFEM technique for temperature advection is accessible in 2014.0. It may help for some specific advanced scenarios. Aim of this is to improve reliability and speed of the whole solver. Activation can be done setting NMETHODT to 0. Solver architecture has been revisited and simplified for preparing the casting Solution to the next level of global solution. Historical UI (precast, meshcast, …) have been now fully decommissioned. Continuous casting solution have been improved and enhanced with new capabilities. ProCAST can now handle multi radius and multi geometric conditions definition (combination of translation / rotation driven by start and end time) to better reflect industrial process and needs. This can be defined using Visual-Cast as using new user functions (func_rotationangle.c and func_rotationaxis.c)

Improve User Functions Capabilities •

•

External compute function (func_externalcompute.c) which allows getting value of the main fields (e.g. temperature, fraction of solid, velocities ...) at any location of the model at the main time of the resolution, has been rewrite for a better handling of DMP capabilities. Export user defined results directly from UF through writeusf: ProCAST can export specific results using an *.usf file (ESI format). This file is automatically read into Visual without any additional development or configuration. It allows user to create new results, advanced results and analyze them directly into Visual-Viewer (Cast).

PanEngine for Material Properties Computation The new engine introduced in ProCAST 2013.5 has been improved by Computherm and enhanced with introduction and support in ProCAST of the PanCo DB. PanEngine edited by the company CompuTherm LLC, calculates multi-component thermodynamics and phase equilibrium with the following functions: • •

Global optimization for automatically finding the stable phase equilibria Automatic search for liquidus surface, and calculation of liquidus slope and partition coefficient

VISUAL-CAST ProCAST Solvers 2014.0 Updates


• •

10


Calculation of thermodynamic factor and mobility Solidification simulation with Scheil and Lever-Rule as well as with a Back Diffusion model (ESI Proprietary).

CompuTherm Database Updates (Oct 2012 – Oct 2013) PanAl2013 1. The Al-Ti system was modified The Al-Ti intermetallic phases were found to form when carrying out Scheil simulation of Al alloys with the addition of Ti. This problem was caused due to the use of the same fcc Al reference state for the intermetallic phases: Al3Ti, AlTi3 and AlTi, which made these intermetallic phases equally stable as the FCC_A1 phase at the Al end. This problem is fixed by giving an extra 100J to the reference state of Al for these phases. 2. The Al-Cu-Mg-Zn system was updated based on the work of [98Buh]. The ternary phase T-Al6CuMg4 was described using the CEF model (Mg)26(Al,Mg)6(Al,Cu,Mg)48(Al)1 and combined with the AlMgZn_tao phase. The new phase name is T. References: [98Buh] T. Buhler, S.G. Fries, P.J. Spencer, H.L. Lukas, J. Phase Equilibria, 19 (4) (1998), pp. 317-333.

PanCo2013 1. The C element was added to the database All the newly formed binaries: Al-C, Co-C, Cr-C, Fe-C, Mo-C, Ni-C, Re-C, Ta-C, and W-C, were modeled. 2. The B element was added to the database All the newly formed binaries: Al-B, C-B, Co-B, Cr-B, Fe-B, Mo-B, Ni-B, Re-B, Ta-B, and W-B, were modeled. 3. The Pt element was added to the database All the newly formed binaries: Al-Pt, B-Pt, C-Pt, Co-Pt, Cr-Pt, Fe-Pt, Mo-Pt, Ni-Pt, RePt, Ta-Pt, and W-Pt, were modeled.

PanFe2013 1. The Mo-Ni-Ti ternary system was updated Two binaries: Ni-Ti and Ti-Mo were updated. The Mo-Ni-Ti ternary was updated based on the work of K. Santhy (Intermetallics 18 2010, 1713-1721) 2. The Al-Fe-Ni ternary system was updated



11


The Al-Fe binary was updated. The ordered Bcc_B2 phase was included and described as order-disorder two parts. The Al-Ni was updated based on the work of (J Alloy Compd. 247 1997, 20-30). Both the L12 and Bcc_B2 were described as order-disorder two parts. The Al-Fe-Ni ternary was updated based on the work of (Acta Mater. 57 (2009) 5234-5341) 3. The Al-Ni-Ti ternary system was remodeled The ternary H_L21 (Ni2TiAl) phase was added according to the published work: Intermetallics 7 1999, 1347-1359. 4. The Fe-Ni-Ti ternary system was updated The Fe-Ti binary FeTi (Cp2) was combined with B2 phase based on the published work of on Calphad 33 2009, 109-123. 5. The Fe-Al-Ti ternary system was remodeled The ternary L21 phase was added to the database based on the work of Intermetallics 14 2006, 1291-1303. 6. The Fe-Si binary system was updated This binary system was remodeled based on the work of CALPHAD, 34, 2010, 405– 414. 7. The Fe-Mn-C ternary system was updated This system was updated using the newly published work of CALPHAD, 35, 2011, 479-491. New phase-equilibrium data are available. The previous one was based on the work of [90Huang] Metall. Trans. A 21A (1990) 2115-2123. 8. The Fe-Mn-Nb-C quaternary system was updated This system was remodeled based on the work of (CALPHAD, 39, 2012, 62-69). Additionally to better take into account for the light elements in some steel alloy families used in continuous casting, the following parameters were modified or added: • •

The temperature dependent terms for some of the associates, such as G(Liquid, CrS), and G(Liquid, MnS), are modified, so that they are less stable at low temperature, while still keeping the binary phase diagram correct; Ternary interaction terms between associates and metals, such as G(Liquid,Cr,Mn1S1;0), G(Liquid,Mn1S1,Ni;0), G(Liquid,Cr1S1,Ni;0), were added to make the topology of Liquid in the ternary systems correct.

PanMg2013 Improvements in PanMg2013 compared to the previous version PanMg2012 focused on extended modeling depth in descriptions concerning mutual interactions of components in multicomponent alloys, without adding new components. Key improvements include: 1. Gas phase description is implemented



12


With thermodynamic descriptions of atomic and molecular species formed from all the 21 components, enabling pressure dependent phase equilibrium calculations. For liquidus projection calculations it is generally recommended to suspend the gas phase. 2. Thorough revision of all phase names in the database following strict and consistent rules set for stoichiometric and solution phases. A complete list of phase names in PanMg2013 compared to PanMg2012 is provided on demand, e.g. ALMG_GAMMA → Al12Mg17. In addition, chemical symbols are converted from all upper case to intuitive case sensitive spelling (MG → Mg), also in all the phase names (AL18MG3MN2 → Al18Mg3Mn2). Together with the new assignment of "phase category" the readability and recognition of the actual phases in Pandat labeling and legends is significantly enhanced. 3. Four substantially improved binary system descriptions 4. Four substantially improved ternary system descriptions 5. A large number of solid solution phases with ternary and higher composition are unified from separate phase descriptions to a unique phase description comprising phases with the same crystal structure. That has resulted in a decrease (!) of the number of assessed phases from 445 to 442 phases, whereas the modeling depth was significantly improved. That enables more realistic calculations involving multicomponent alloy systems.

PanNi2013 1. The description for the Al-Co-Ni-W quaternary was improved Model parameters for this quaternary were re-optimized according to experimental data for Cobalt alloys. This quaternary is now consistent with the one in the PanCo2013 database. 2. The L12, gamma_double_prime, Delta, Eta, Liquid phases are remodeled Model parameters for these phases were remodeled/improved to get better fit for solvus and liquidus temperatures, focusing on Ni-718, RR1000 and MC series, mainly the Ti, Nb, Ta and W related interaction parameters; 3. End member parameters (missing/unreasonable) to B2 and other phases (such as Mu and Sigma phases) were added and some interaction parameters were modified accordingly.

PanTi2013 1. The lattice stability of BCC-Ti was modified for self-consistency G(BCC-Ti) reset to SGTE, previously it is SGTE+0.072*T from Ref: Cr-Ti-V, J. Phase Equilibrium, 2002, 23(4), 310-328. 2. BCC_A2 (beta phase) and HCP_A3 (alpha phase) were remodeled



13


Model parameters for these two phases were re-optimized to develop better fit of the beta transus temperatures for Ti64, Ti662, Ti1023, Ti6242, Ti6246 and other Ti-alloys, mainly by reducing the impact of Oxygen and increasing the impact of Nitrogen. 3. The Mo-C, Mo-Si, Sn-Ti, Mo-Ti-C and Al-Sn-Ti systems were remodeled These binary and ternary systems were remodeled and the C,H,N,O interaction parameters re-optimized to get a better fit of the beta transus temperatures for IMI550, IMI551, IMI679, UNS-R54560/Ti-5522 and UNS-R58210.

Other Updates • •

“Out of core” capabilities using MUMPS for stress solver is now fully available. It allows to switch automatically to “out of core” capabilities when direct solver request more memories than RAM available. For MiLe case, MICRO and TTTMIC are now available.

Limitations • • • • •

RDEBUG has not yet been parallelized. Avoid combination of THERMAL 2 and MICRO. For pressure inlet driven cases like Lost Foam it is recommended to reduce the convergence parameter PCONVTOL to 1e-04 for better convergence. New fluid flow does not yet support the cases with Accordion. For ductile iron, it is advised to ignore P and S components which could prevent to compute ferrite and pearlite phase.



15


VISUAL-MESH (CAST) Tetra Mesh •

Performance of tetra meshing is greatly improved with multi-processing. o Option to specify the number of processors to be used is provided. o The improvement is around 40 % for single processor. It is around 60% and more, with multiple processors.

VISUAL-MESH (CAST) ProCAST Solvers 2014.0 Updates


16


Performance improvement for the model with 289454 nodes and 586369 elements:



17


New Toolbar for 2D Mesh Utilities •

A new toolbar containing generally used 2D mesh utilities is provided, for quick access.

Quality and Performance of Surface Shading Improved



19


VISUAL-VIEWER (CAST) ENHANCEMENTS •

•

•

In Metallurgical Tools panel, the Temperature unit in which values are to be entered is displayed. This unit is same as that set in "Tools-> Result Unit Conversion". If temperature value is entered and is submitted for generating the result, the unit in which it is entered is remembered. Subsequent changes in temperature unit will change the value accordingly. Now Slice and Cutoff can be viewed simultaneously. This can be achieved through Cutoff panel. Here, the Slice check button has to be set ON. This will enable the button for posting Slice panel, in which the slice plane can be defined.

Mesh, stress, temperature and porosity results can now be exported in the *.KEY DEFORM native format. DEFORM is a forging software developed by Scientific Forming Technologies Corporation (SFTC).

VISUAL-VIEWER (CAST) Enhancements


•

20

Curve statistics for better information on plotted curves

VISUAL-VIEWER (CAST) Enhancements



21


BUG FIXES • • •

• • • • • • • • •

There was an error in display of model with two mirror symmetry. This is now fixed. If you had set min/max values in Spectrum GUI, changing the start or end step in Animation Control GUI would reset these values. This is now fixed. There was an issue in volume management with respect to QuikCAST and APM results. If number of volumes selected for loading when opening .MCO file does not correspond to number of volumes selected for computation in APM, the APM results were not displayed properly. This is now fixed. When post-processing voids results for QuickCAST calculation (filling and solidification), the final result is kept to the final step (the step where it reaches the stop filling criteria). Closing set-up window in post-processing used to close contour panel. This is now corrected. If Options->Mold Result is OFF, Cutoff display was not proper. This is now fixed. You can now modify scale of Isochrones. In Cristal, if you select the option "Simulation Data", the generated data was empty. This is now corrected. In the Calculation monitor panel, precision of Time Step and Simulated Time has been changed for better readability. Entity info on APM results were not displayed properly. This is now fixed. While working with one window mode and two window mode, sometimes the contour was lost. This is now fixed. For APM results, unit was not properly handled in Cutoff mode. This is now corrected.

VISUAL-VIEWER (CAST) Bug Fixes


22


KNOWN ISSUES • •

• • • • •

•

Updating APM results during solver run may sometimes crash the application. If you select 'View' > Home Page when a model is active, the Contour dialog still remains. If you select a different result, when the model is displayed, the contour colors will not be correct. Workaround: This can be corrected by selecting the result again or by posting the Spectrum dialog. If more than one Principal stress is selected for display as vectors, its maximum value will not be displayed properly in the legend. If units are changed in the cut-off mode, contours will not be displayed properly. You are advised to change it in the snapshot mode and then switch to cut-off mode. During copying and pasting of model from one window or page to another, the image may not be displayed as expected. Workaround: The model is displayed properly on pressing 'F', i.e. fitting the model within the window. During CAFE result display, sometimes model is not refreshed. Workaround: Click on model window and rotate. In deform export, coincident and equivalent interfaces are detected using ff.unf file. If this file is not present, then exported file will not be proper. It is then recommended to export only the final single part to be imported into DEFORM rather than the whole model, as DEFORM manages interface differently. In case of Profile plotting for dynamic models like MILE, the profile created at one step, will give wrong result if plotted at some other step.

LIMITATIONS • • • • • • • •

Template does not support calculated particles, free surface / point XY-plotting. Entity Selector may become inactive in some situations. To activate it again, activate the model window and press Escape key. Volume of porosity computation is linked to the mesh size; consequently, this is an approximated value. For QuikCAST models, tilt and explode cannot be applied simultaneously. Exporting the evolution curves plotted has a problem. If the curve names are not present in the "Page/File View" tab, then exporting two or more curves by pressing Control key and right clicking will give error. Stress tensors are not displayed on mold. To view solver calculation status in "Calculation Monitoring" GUI, the solver path must have solver version number. Ex. 2013.5 or 2013.0, etc. Misrun is caused by a combined effect of viscosity and permeability. The risk indicator is not applicable to thixo casting since the metal at inlet is already in the mushy zone.

VISUAL-VIEWER (CAST) Known Issues


•

23


Unit conversion is not supported for "Temperature gradient" results. It is always displayed in K/cm units.

VISUAL-VIEWER (CAST) Limitations


25


CORE DUMP TRACKER You can register any crash that occurs while you are working with Visual-Environment through the Core Dump Tracker utility. This utility is available on Windows systems only. Whenever the application crashes, you will see the following dialog box:

•

Click on ‘Send Error Report’ to send the report and close both the dialog box and the application.

•

Click on ‘Don’t Send’ to close the dialog box and the application without sending a report.

•

Click on ‘View Report Details…’ to check details of the report that will be sent. You will see the following dialog listing out the files that will be sent.

CORE DUMP TRACKER Limitations


26


•

By default, the check box to send additional files is OFF and only the files marked with a ‘*’ against their name will be sent.

•

To send the additional files, check the box ON.

Please note that the session file is not sent by default. You can also set the following variables in the VisualEnvrc.bat file residing in your ‘Site’ folder to customize the settings: •

If you wish to send your session file, add the following line: set VHOST_COREDUMPTRACKERFILES_ENABLE=1

•

If you do not want to use the Core Dump Tracker, add the following line: set VHOST_COREDUMPTRACKER_ENABLE=0

We enlist your help to improve your experience with Visual-Environment by sending us a report through this utility. We assure you that the information you send us will be used only to solve the reported problem and confidentiality of the information will be fully maintained.

CORE DUMP TRACKER Limitations


27


LICENSING SYSTEM TYPES OF LICENSES Three different types of licenses exist: •

FEATURE: Licenses based on features (previous system).

•

CONTEXT: Licenses based on contexts count. o VISUAL_CONTEXT1: One context can be used.

o VISUAL_CONTEXT2: Two contexts can be used simultaneously. o VISUAL_CONTEXT3: Three or more contexts can be used simultaneously.

•

TOKEN: Licenses based on tokens count. o Each context is converted in VISUAL_TOKEN tokens.

o Usage of contexts increases the number of tokens requested.

In all cases, a VISUAL_BASE seat is required to launch Visual-Environment.

FEATURE SYSTEM •

It is the previous licensing system.

•

To add flexibility, two strategies to check out the features are proposed. o On Init: The features are requested during the initialization phase.

o On Fly: The features are requested during the usage, when entering the contexts. •

Not available contexts (no licenses) are now grayed in Context bar and Context Manager.

•

VISUAL_BASE seat required to launch VE.

LICENSING SYSTEM Types of Licenses


28


CONTEXT SYSTEM •

This system is based on the number of contexts to be used.

•

There are three options: o VISUAL_CONTEXT1: One context can be used.

o VISUAL_CONTEXT2: Two contexts can be used simultaneously. o VISUAL_CONTEXT3: Three or more contexts can be used simultaneously.

•

Selected contexts can be managed and modified during the session using the Context Manager in the Context bar.

•

Third-party options are not converted in contexts and require standard features.

•


List of Compatible Contexts All contexts except: •

Visual-Seal

•

Visual-Process Builder

TOKEN SYSTEM •

This system is based on the usage of VISUAL_TOKEN tokens.

•

Each context is converted in tokens.

•

Depending of the usage, tokens are requested. o The number of tokens really used is computed in a way to limit the maximum number of tokens used in a single session (maximum of 12 tokens per session).

•

Third-party options are not converted in tokens and require standard features.

•


Number of Tokens by Context All contexts check out 6 tokens except: •

Visual-Mesh: 4 tokens

LICENSING SYSTEM Context System


29


•

VisualDSS: 2 tokens

•

Visual-Seal: not available in Tokens mode

•

Visual-SDK : not available in Tokens mode

LICENSING SYSTEM Token System


30


Used Tokens in a Session

•

From 0 to 6 tokens (first context): Full “tokens price”.

•

From 6 to 18 tokens (second and third contexts): Half “tokens price”.

•

More than 18 tokens (Three and more contexts): No more tokens taken.

•

One VISUAL_BASE seat by session.

LICENSING SYSTEM Token System


31


SYNTHESIS Compatibility of applications versus strategy: Application name

FEATURE

CONTEXT TOKENS

Visual-Process Executive

VISUAL_PROCESS_EXECUTIVE

6

Visual-Mesh

VISUAL_MESH

4

Visual-Viewer

VISUAL_VIEWER

6

Visual-OPT

VISUAL_OPT

6

VisualDSS

VISUAL_COMPOSER

2

Visual-Seal

VISUAL_SEAL

Visual-Crash PAM

VISUAL_CRASH_PAM

6

Visual-Crash DYNA

VISUAL_CRASH_DYNA

6

Visual-Crash RAD

VISUAL_CRASH_RAD

6

Visual-Safe

VISUAL_SAFE

6

Visual-Safe MAD

VISUAL_SAFE_MAD

6

Visual-Shock

VISUAL_HVI

6

Visual-MEDYSA

VISUAL_MEDYSA

6

Visual-Life NASTRAN

VISUAL_LIFE_NASTRAN

6

Visual-SYSTUS

VISUAL_SYSTUS

6

Visual-CEM

VISUAL_CEM

6

Visual-VTM

VISUAL_RAYON

6

Visual-Cast

VISUAL_CAST

6

Visual-Local Model Advisor

VISUAL_LMA

6

Visual-Weld

VISUAL_WELD

6

Visual-Heat Treatment

VISUAL_HT

6

Visual-Materials (Composites)

VISUAL_COMPOSITES

6

Visual-Distortion

VISUAL_DISTORTION

6

Visual-FORM

VISUAL_FORM

6

Visual-CFD

VISUAL_CFD

6

Visual-SDK

VISUAL_PROCESS_BUILDER

LICENSING SYSTEM Synthesis


32


LIST OF THIRD PARTY COMPONENTS NOT INCLUDED IN EITHER CONTEXT OR TOKEN •

The Visual-Environment seat: o VISUAL_BASE

•

The CAD converters: o VISUAL_CATIA (import CATIA V4 files)

o VISUAL_CATIAV5 (import CATIA V5 files) o VISUAL_UNIGRAPHICS (import UG files)

o VISUAL_PARASOLID (import Parasolid files) o VISUAL_INTEROP_STEP (import Step files)

o VISUAL_INTEROP_PROE (import Pro Engineer files) •

Thermal properties calculation in Visual-CAST

•

COMPUTHERM_AL

•

COMPUTHERM_NI

•

COMPUTHERM_FE

•

COMPUTHERM_TI

•

COMPUTHERM_MG

•

COMPUTHERM_CU

•

Other tools: o VISUAL_VKI (to read NASTRAN op2 files)

o VISUAL_RADPAM

o VISUAL_FULLSTS/VISUAL_ALLSTS (for Morphing)

o VISUAL_WISETEX (for Wisetex)

o STAMP2G_IOLIB (for psp2erf in StampTools)

o CRIPTE_BASE (for CRIPTE Tools)

LICENSING SYSTEM List of Third Party Components Not Included in Either Context or Token


33


LICENSE STRATEGY CONFIGURATION License checkout strategy that will be used by the application is determined in the following order: •

The first level of checks is made at the license file level (Enterprise level). o If ‘USER_INFO’ is specified in the license file, this information will be used to detect the license strategy. o This field is managed by the client and not by ESI’s licensing team. It is one of the very rare modifications that the client is allowed to make in the license file.

•

The second level checks are made at the ‘Site’ installation directory level (Enterprise level). o If the ‘checkout_strategy.cfg’ file exists in the Site installation directory, this shared configuration is used instead of the configuration stored in User Local Data. o This can be very useful in a ‘network’ installation configuration.

•

The last level of check is at the End User level.

LICENSING SYSTEM License Strategy Configuration


34


o At this level, if a 'checkout_strategy.cfg' is available under 'User local data', it will be used. o Else, the application decides which license strategy to use based on the information available in the license file. In this case, no 'checkout_strategy.cfg' file is written.

LICENSING SYSTEM License Strategy Configuration


35


LICENSE STRATEGY MANAGER License strategy manager is a tool that allows you to check the available options for license strategy. You can also redefine the license strategy to be used by the application, overriding the decision made by the application. If needed, you can invoke this tool through the desktop shortcut 'Licensing Strategy' on Windows or by keying in ' -strategy' on Linux systems. The following dialog will be posted.

•

Important Note: By default, 'Tokens' is switched on in this dialog. After posting this dialog, if you select OK, a 'checkout_strategy.cfg' file will be saved with this strategy and the application will attempt to use this strategy henceforth.

•

License Type: Choice between the 3 strategies: o FEATURE

Features based strategy.

o TOKEN

Tokens strategy using VISUAL_TOKEN.

o CONTEXT

•

Checkout strategy: In FEATURE strategy, choice of the checkout option: o ON_INIT o ON_FLY

•

Contexts based strategy using VISUAL_CONTEXT.

To check out the features On Initialization. To check out the features On Fly when using the context.

Contexts: In CONTEXT strategy, choice of the option: o CONTEXT1 To use 1 Context.

o CONTEXT2 To use 2 Contexts simultaneously.

o CONTEXT3 To use 3 Contexts and more simultaneously.

LICENSING SYSTEM License Strategy Manager


•

36


Options: Activate a log file to analyze the licenses usage during a session: o LOGFILE

Create log file. The file is stored with the session file.

o Log is also activated when setting FLEXLM_DIAGNOSTICS variable. •

Check the license strategies and license file or server: o Features OK A VISUAL_BASE seat is available (license system OK). o Contexts OK VISUAL_CONTEXT are available. o Tokens OK

Some VISUAL_TOKEN are available.

•

Usage gives a detailed list of users.

•

Defaults: Reset to default (FEATURE ON_FLY).

LICENSING SYSTEM License Strategy Manager


37


INSTALLATION GUIDE SOFTWARE INSTALLATION ON WINDOWS Installation of the Software Insert the CD-ROM into the disc drive. Follow the procedure described below depending if autorun is enabled on your computer.

Autorun is enabled on your computer The ProCAST installation should start automatically. The InstallShield Wizard dialog box is displayed and then you should simply follow the instructions.

Autorun is disabled on your computer Open a Windows Explorer window, click on your CD-ROM drive icon. Double click on the Setup.exe file, located in the ProCAST20140_Windows directory, to start the software installation. The InstallShield Wizard dialog box is displayed and then you should simply follow the instructions.

When the software installation is completed, the ProCAST product will be available in the Start/Programs/ESI group menu or in the ESI Group icon folder on the desktop.

Installation of the License Before starting the license installation you should obtain a valid license file. Note that the ProCAST software is version protected and compiled with FLEXnet version 11.11.1. License files delivered for the previous ProCAST versions are not valid with this version of the software, except if your license does already contain the 2014 label. It is highly recommended to upgrade an existing license server with the FLEXnet Licensing Utilities v11.11.1.1 which is delivered in this installation. System information must be retrieved before you can request your FLEXnet license files if required: -

For each PC machine that will be running ProCAST, execute

-

Select System Settings tab

c:\flexlm\lmtools.exe

INSTALLATION GUIDE Software Installation on Windows


-

38


Send all the information on the left part (Hostid Settings) to your local ESI support representative with the “Save HOSTID Info to file” option.

Once you have received your(s) license file(s), it/they must be moved to the appropriate directory c:\flexlm on each machine with the file name pam_lmd.lic.

Starting the FLEXnet License Server The FLEXnet license server installation must be done with administrator privileges. Once the ProCAST installation is completed, your pam_lmd.lic file must be moved to the appropriate directory, updated and the FLEXnet license server started. To move and update the license file:

-

Move pam_lmd.lic to the directory c:\flexlm

-

Using any usual text editor, edit pam_lmd.lic and adapt the SERVER/VENDOR lines if necessary

To start the license server: -

Execute c:\flexlm\lmtools.exe



39


-

Select the Service/License file tab and select Configuration using Services

-

Select the Configure Services tab, adjust parameters as below and click the Save Service button



-

40


Select the Start/Stop/Reread tab and click the Start Server button

After completing these installation steps, you may start using ProCAST. Additional specific FLEXnet documentation is also provided with the software on the installation CD-ROM.



41


SOFTWARE INSTALLATION ON LINUX Overview To install the ProCAST product on Linux platforms, two installation procedures are available: -

paminst-gui.sh

graphical User Interface script,

paminst.sh

command line script.

Both procedures perform the following tasks: 1. Install the software : ·

Copy from the CD-ROM all the software files to the chosen location.

2. License management : ·

Install the license file,

·

Start the license daemons lmgrd and pam_lmd if needed,

·

Install the license daemon startup scripts*.

3. Customization : ·

Set up the ESI Group software environment for each current user.

Tasks 2 and 3 can be performed later if the user does not want to do them immediately. After the installation, the files installed on the hard disk are organized in a directory tree as indicated below: Head Directory

this is referenced as PAMHOME Installation Scripts...

MODULE 1

Executables, other files...

Version1_COMMON Ressource files

MODULE 2


Examples

Version1_platformOS1 Version1_platformOS2 Version2_platformOS1 Executables

Executables

LICENSES

Examples files, test cases...

Executables

License file

platformOS1

Deamon and tool files

DOC

Electronic documentation

platformOS2


*

Sufficient privileges may be required by the system during the installation of ESI Software products. Although no system library is updated in the process, sufficient privileges will be needed to mount the CD-ROM and to install the boot files to start the license server.

INSTALLATION GUIDE Software Installation on Linux


42


CD-ROM Mounting Instructions Insert the CD-ROM into the CD-ROM drive. Follow the CD mounting and dismounting instructions in the table below. When the installation is done, don’t forget to quit the directory /cdrom before ejecting the CD-ROM from the drive. PLATFORM

MOUNTING

SPECIFIC INSTRUCTIONS

DISMOUNTING

PC Windows

Automatic

-

-

PC Linux

Automatic

-

eject

# symbol is the SCSI Id number of the CD-ROM drive Device names in italics are site dependent

Graphical Installation System requirement: The installation through graphical user interface is available on Linux. In order to use the graphical installation, you need an X compliant window system available on your display. You must position the DISPLAY environment variable for display on the current screen, and if necessary allow this display using an appropriate xhost command on the display host. You also need about 15 Mb of free space in /tmp, in order to store graphical tools temporarily. To start the graphical software installation script, go to the /cdrom directory then type the following command: ./INSTALL.SH

To complete the installation follow the instructions displayed in blue color in the dialog boxes presented by the installation tool. After the graphical tools are loaded in /tmp, the main dialog box window appears:



43


Main Dialog Box Window

-

Click the Install software button. It will highlight the Next button to continue.

-

Click the Next button to continue the software installation.

-

Click the Cancel button to abort/exit the software installation.



44


Installation directory dialog box window

This dialog box is used to specify the installation directory. By default, the text field of the installation directory is filled with the previous pathname of ESI Group software installation directory if any. Two possibilities are available to select a new software installation location on the system: a. Click on and fill the text field with a valid pathname directory (read, write, execute permissions are required), or b. Click the Browse button to select another software installation location (see Directory selector dialog box for using it). -

Click the Next button when you are satisfied with the software installation directory selected.

-

Click the Previous button to go back to the main dialog box of the software installation.



45


Package Selection:

Package Selection Window

This dialog box is used to select all the software package(s). -

Select all the platform package(s) you wish to download on the system by clicking on the toggle(s) then click the Next button to continue. Note that, if not already done, the flexnet_v11.11.1 package should also be installed for all platforms.

A scrolled window is displayed showing the downloading of files. When the downloading is finished, the Close button will be highlighted. -

Click Close to continue.



46


The main dialog box window appears again to perform the next steps, the license installation and/or Customization of the software environment. -

Click the Exit button if you wish to perform the License installation and software customization later.

-

Click the License management button to install the license. A license file is needed to perform this task. For more detail, please and see the Installation of the license section.

-

Click the Define environment button to customize the software environment. For more detail, please see the Customization section.

Installation of the License Before starting the license installation you should copy the new or updated FLEXnet license file provided by ESI Group representatives in the following directory PAMHOME/licenses with the filename pam_lmd.temp. Note that the ProCAST software is version protected and compiled with FLEXnet version 11.11.1. License files delivered for the previous ProCAST versions are not valid



47


with this version of the software, except if your license does already contain the 2014 label. It is highly recommended to upgrade any existing license server with the latest version of the FLEXnet Licensing Utilities v11.11.1.1 which comes with this installation. The installation of the license should be performed on the system where the license server will run. To start the graphical license installation script, go to the software installation directory and type the following command: ./paminst-gui.sh

lic or ./paminst-gui.sh

install_lic

After the graphical tools are loaded in /tmp, the following assistant window appears:

Follow the instructions displayed in blue color.

Get host id. Button -

Click the Get host id button to get the information (Operating System, hostname, hostid) of the system needed for license server installation (floating license) or standalone license (node-locked license). It will display the following window:



48


Important remark on Linux i686 or x86_64 based distributions: The FLEXnet Toolkit can only run on LSB3 (Linux Standard BaseTM) compliant Linux distributions. The “LSB3 OS Compliant” detail must display “Yes” otherwise your Linux distribution cannot run a license server with this latest version of the FLEXnet Toolkit. Check that the following package is installed on the station: •

RedHat Based Operating Systems: For RedHat, CentOS, Oracle Linux, Fedora …: package redhat-lsb How to check installation: rpm -q redhat-lsb How to install it (as root or with sudo): yum install redhat-lsb

•

SUSE Based Operating Systems: For SUSE Entreprise, openSUSE …: package lsb How to check installation: rpm -q lsb How to install it (as root or with sudo): yast2 -i lsb

•

Debian Based Operating Systems: For Debian, Ubuntu …: package lsb How to check installation: dpkg-query -l lsb



49


How to install it (as root or with sudo): apt-get install lsb

License directory selection: By default, the Install licenses directory under directory: text field is filled with the pathname of the previous software installation directory. -

Click the Browse button to redefine the pathname of the software installation directory.

Note:

·

The specified directory in the text field should contain a licenses subdirectory with write permission to highlight the Next button.

-

Click the Next button when the installation directory pathname is selected. The license file is installed in the right location and the following dialog box appears:

-

Click the Get another license file button to select a new license file.



-

50


Click the OK button to find the new license file on the local disk. A new file browser window appears.

By default the file filter is set for find PAM license file. -

Select the new license file then click the Open button to validate the selection.

A small window pops up displaying the checking result of the selected license file with the host id.

The dialog box of license file selection will be displayed again and filled with information corresponding to the selected license file.



-

51


Click on Apply changes to new file and then on Save new file as current button.

The new license file is installed and the Next button is activated to continue. -

Click the Next button to start the license daemons.



-

52


Click the Start daemon now as current user button to start the daemon.

Additional specific FLEXnet documentation is also provided with the software on the installation CD-ROM.



53


Customization The ESI Group software installation script paminst.sh can be used for customization.

This customization is done with pamcust.sh which can also be used separately. To perform the customization separately: -

Log in on the machine on which you want to perform the customizations,

-

Change directory to the $PAMHOME directory where the installation has been done,

-

Type ./pamcust.sh and follow the instructions.

The customization script creates definitions to allow access to the ProCAST executables and configuration files for all users or for selected users, depending on the method selected. The software configuration is defined in the following files: -

psi.Cenv for csh and derivatives,

-

psi.Kenv for ksh and derivatives,

-

Psi.Baenv for bash.

Note that sh is not supported, due to its lack of functionality necessary for ESI Group products. We recommend sh users to migrate to ksh which preserves sh syntax and habits. The customization procedure will automatically update the .cshrc, .profile or .bash_profile files accordingly, as shown below.



54


C Shell - .cshrc file

### ESI-Group begin ### # # ESI-Group Software environment # setenv PAMHOME /home/ppg/ESIGroup setenv PAMENV $PAMHOME/env-‘uname’ if ( -r $PAMENV/psi.Cenv ) then source $PAMENV/psi.Cenv endif ### ESI-Group end ###

Korn Shell - .profile

### ESI-Group begin ### # # ESI-Group Software environment # PAMHOME=/home/ppg/ESIGroup; export PAMHOME PAMENV=$PAMHOME/env-‘uname’; export PAMENV if [ -r $PAMENV/psi.Cenv ]; then . $PAMENV/psi.Kenv fi ENV=${ENV:””} if [ -z “$ENV” ]; then ENV=$HOME/.kshrc; export ENV fi ### ESI-Group end ###

Bourne Again Shell -

### ESI-Group begin ### # # ESI-Group Software environment # PAMHOME=/home/ppg/ESIGroup; export PAMHOME PAMENV=$PAMHOME/env-‘uname’; export PAMENV if [ -r $PAMENV/psi.Baenv ]; then . $PAMENV/psi.Baenv fi if [ -z “$BASH_ENV” ]; then BASH_ENV=$HOME/.bashrc; export BASH_ENV fi ### ESI-Group end ###

.bash_profile

The same procedure must be repeated for the customization of each candidate user.



55


SOFTWARE INSTALLATION ON LINUX Overview To install the ProCAST product on Linux platforms, two installation procedures are available: -

paminst-gui.sh

graphical User Interface script,

paminst.sh

command line script.

Both procedures perform the following tasks: 4. Install the software : ·

Copy from the CD-ROM all the software files to the chosen location.

5. License management : ·

Install the license file,

·

Start the license daemons lmgrd and pam_lmd if needed,

·

Install the license daemon startup scripts*.

6. Customization : ·

Set up the ESI Group software environment for each current user.

Tasks 2 and 3 can be performed later if the user does not want to do them immediately. After the installation, the files installed on the hard disk are organized in a directory tree as indicated below: Head Directory

this is referenced as PAMHOME Installation Scripts...

MODULE 1


Version1_COMMON Ressource files

MODULE 2


Examples

Version1_platformOS1 Version1_platformOS2 Version2_platformOS1 Executables

Executables

LICENSES

Examples files, test cases...

Executables

License file

platformOS1


DOC

Electronic documentation

platformOS2


*

Sufficient privileges may be required by the system during the installation of ESI Software products. Although no system library is updated in the process, sufficient privileges will be needed to mount the CD-ROM and to install the boot files to start the license server.



56


CD-ROM Mounting Instructions Insert the CD-ROM into the CD-ROM drive. Follow the CD mounting and dismounting instructions in the table below. When the installation is done, don’t forget to quit the directory /cdrom before ejecting the CD-ROM from the drive. PLATFORM

MOUNTING

SPECIFIC INSTRUCTIONS

DISMOUNTING

PC Windows

Automatic

-

-

PC Linux

Automatic

-

eject

# symbol is the SCSI Id number of the CD-ROM drive Device names in italics are site dependent

Graphical Installation System requirement: The installation through graphical user interface is available on Linux. In order to use the graphical installation, you need an X compliant window system available on your display. You must position the DISPLAY environment variable for display on the current screen, and if necessary allow this display using an appropriate xhost command on the display host. You also need about 15 Mb of free space in /tmp, in order to store graphical tools temporarily. To start the graphical software installation script, go to the /cdrom directory then type the following command: ./INSTALL.SH

To complete the installation follow the instructions displayed in blue color in the dialog boxes presented by the installation tool. After the graphical tools are loaded in /tmp, the main dialog box window appears:



57


Main Dialog Box Window

-

Click the Install software button. It will highlight the Next button to continue.

-

Click the Next button to continue the software installation.

-

Click the Cancel button to abort/exit the software installation.



58


Installation directory dialog box window

This dialog box is used to specify the installation directory. By default, the text field of the installation directory is filled with the previous pathname of ESI Group software installation directory if any. Two possibilities are available to select a new software installation location on the system: c. Click on and fill the text field with a valid pathname directory (read, write, execute permissions are required), or d. Click the Browse button to select another software installation location (see Directory selector dialog box for using it). -

Click the Next button when you are satisfied with the software installation directory selected.

-

Click the Previous button to go back to the main dialog box of the software installation.



59


Package Selection:

Package Selection Window

This dialog box is used to select all the software package(s). -

Select all the platform package(s) you wish to download on the system by clicking on the toggle(s) then click the Next button to continue. Note that, if not already done, the flexnet_v11.11.1 package should also be installed for all platforms.

A scrolled window is displayed showing the downloading of files. When the downloading is finished, the Close button will be highlighted. -

Click Close to continue.



60


The main dialog box window appears again to perform the next steps, the license installation and/or Customization of the software environment. -

Click the Exit button if you wish to perform the License installation and software customization later.

-

Click the License management button to install the license. A license file is needed to perform this task. For more detail, please and see the Installation of the license section.

-

Click the Define environment button to customize the software environment. For more detail, please see the Customization section.

Installation of the License Before starting the license installation you should copy the new or updated FLEXnet license file provided by ESI Group representatives in the following directory PAMHOME/licenses with the filename pam_lmd.temp. Note that the ProCAST software is version protected and compiled with FLEXnet version 11.6.1. License files delivered for the previous ProCAST versions are not valid



61


with this version of the software, except if your license does already contain the 2013 label. It is highly recommended to upgrade any existing license server with the latest version of the FLEXnet Licensing Utilities v11.11.1.1 which comes with this installation. The installation of the license should be performed on the system where the license server will run. To start the graphical license installation script, go to the software installation directory and type the following command: ./paminst-gui.sh

lic or ./paminst-gui.sh

install_lic

After the graphical tools are loaded in /tmp, the following assistant window appears:

Follow the instructions displayed in blue color.

Get host id. Button -

Click the Get host id button to get the information (Operating System, hostname, hostid) of the system needed for license server installation (floating license) or standalone license (node-locked license). It will display the following window:



62


Important remark on Linux i686 or x86_64 based distributions: The FLEXnet Toolkit can only run on LSB3 (Linux Standard BaseTM) compliant Linux distributions. The “LSB3 OS Compliant” detail must display “Yes” otherwise your Linux distribution cannot run a license server with this latest version of the FLEXnet Toolkit. Check that the following package is installed on the station: •

RedHat Based Operating Systems: For RedHat, CentOS, Oracle Linux, Fedora …: package redhat-lsb How to check installation: rpm -q redhat-lsb How to install it (as root or with sudo): yum install redhat-lsb

•

SUSE Based Operating Systems: For SUSE Entreprise, openSUSE …: package lsb How to check installation: rpm -q lsb How to install it (as root or with sudo): yast2 -i lsb

•

Debian Based Operating Systems: For Debian, Ubuntu …: package lsb How to check installation: dpkg-query -l lsb How to install it (as root or with sudo): apt-get install lsb



63


License directory selection: By default, the Install licenses directory under directory: text field is filled with the pathname of the previous software installation directory. -

Click the Browse button to redefine the pathname of the software installation directory.

Note:

·

The specified directory in the text field should contain a licenses subdirectory with write permission to highlight the Next button.

-

Click the Next button when the installation directory pathname is selected. The license file is installed in the right location and the following dialog box appears:

-

Click the Get another license file button to select a new license file.



-

64


Click the OK button to find the new license file on the local disk. A new file browser window appears.

By default the file filter is set for find PAM license file. -

Select the new license file then click the Open button to validate the selection.

A small window pops up displaying the checking result of the selected license file with the host id.

The dialog box of license file selection will be displayed again and filled with information corresponding to the selected license file.



-

65


Click on Apply changes to new file and then on Save new file as current button.

The new license file is installed and the Next button is activated to continue. -

Click the Next button to start the license daemons.



-

66


Click the Start daemon now as current user button to start the daemon.

Additional specific FLEXnet documentation is also provided with the software on the installation CD-ROM.

Customization The ESI Group software installation script paminst.sh can be used for customization.

This customization is done with pamcust.sh which can also be used separately. To perform the customization separately: -

Log in on the machine on which you want to perform the customizations,

-

Change directory to the $PAMHOME directory where the installation has been done,

-

Type ./pamcust.sh and follow the instructions.

The customization script creates definitions to allow access to the ProCAST executables and configuration files for all users or for selected users, depending on the method selected. The software configuration is defined in the following files: -

psi.Cenv for csh and derivatives,

-

psi.Kenv for ksh and derivatives,

-

Psi.Baenv for bash.

Note that sh is not supported, due to its lack of functionality necessary for ESI Group products. We recommend sh users to migrate to ksh which preserves sh syntax and habits.



67


The customization procedure will automatically update the .cshrc, .profile or .bash_profile files accordingly, as shown below. C Shell - .cshrc file

### ESI-Group begin ### # # ESI-Group Software environment # setenv PAMHOME /home/ppg/ESIGroup setenv PAMENV $PAMHOME/env-‘uname’ if ( -r $PAMENV/psi.Cenv ) then source $PAMENV/psi.Cenv endif ### ESI-Group end ###

Korn Shell - .profile

### ESI-Group begin ### # # ESI-Group Software environment # PAMHOME=/home/ppg/ESIGroup; export PAMHOME PAMENV=$PAMHOME/env-‘uname’; export PAMENV if [ -r $PAMENV/psi.Cenv ]; then . $PAMENV/psi.Kenv fi ENV=${ENV:””} if [ -z “$ENV” ]; then ENV=$HOME/.kshrc; export ENV fi ### ESI-Group end ###

Bourne Again Shell .bash_profile

### ESI-Group begin ### # # ESI-Group Software environment # PAMHOME=/home/ppg/ESIGroup; export PAMHOME PAMENV=$PAMHOME/env-‘uname’; export PAMENV if [ -r $PAMENV/psi.Baenv ]; then . $PAMENV/psi.Baenv fi if [ -z “$BASH_ENV” ]; then BASH_ENV=$HOME/.bashrc; export BASH_ENV fi ### ESI-Group end ###

The same procedure must be repeated for the customization of each candidate user.



68


GETTING STARTED Starting the Software For Windows platforms: When the software is installed on Windows, a file folder named ESI Group is automatically created on the computer Desktop. Inside this folder, "ProCAST 2014.0" with “Visual-Cast 9.6” icon is present. A double click on the corresponding icon will automatically start the software manager, respectively the new environment and give access to the different product modules.

For Linux platforms: The installation procedure includes a customization procedure. The customization script creates definitions to allow access to the different executables and configuration files for all users or for selected users, depending on the method chosen. After a complete and successful product installation, necessary environment variables and aliases are automatically defined to start different product modules. Type the following commands for a direct access: -

datacast , procast and procastdmp for the solvers,

-

vcast for the pre-processor Visual-Cast.

Note that access to previous versions of ProCAST is possible with modified aliases. For instance, type procast135 / vcast90 for ProCAST 2014.0

On-line Product Documentation On-line product documentation is available for most ProCAST features. One manual is provided with the standard installation: the ProCAST User’s Guide. This Manual provides extensive information to guide users through the different modules of ProCAST, to explain the use of different software features as well as to give technical information on models and algorithms. Refer to the User Manual and in particular to the What’s New / Version 2014.0 section for detailed information on all new and improved product features.

INSTALLATION GUIDE Getting Started


69


AVAILABLE PLATFORMS AND PRE-REQUISITES PRODUCT AVAILABILITY ProCAST has currently been tested and validated on the following hardware platforms: Solver & Visual Environment: Vendor

Processor

OS

Windows

Intel / AMD

Windows XP SP3

Linux

Intel / AMD

Redhat EL5 & 6

Windows 7 & 8

Memory addressing 64 bits 64 bits

Refer to the Visual Environment product documentation and in particular to the VisualEnvironment-9.0_InstallationGuide.pdf document for detailed information on hardware requirements. Remarks:

·

The ProCAST 2014.0 package requires the installation of the VisualEnvironment 9.6 version (not 9.0).

AVAILABLE PLATFORMS AND PRE-REQUISITES Product Availability


70


AVAILABILITY OF THE ProCAST DMP VERSION Since this version only the DMP code is delivered as the standard version of ProCAST. The PCMPI: Message Passing Interface version 8.2.1 on Linux and Windows are used and required runtime libraries are included in the software package. The PETSc: Portable, Extensible Toolkit for Scientific Computation (Copyright 19952004, University of Chicago) version 3.3-p3 is used on all platforms and required runtime libraries are included in the software package when appropriate. The ParMetis version 3.1.1 is used on all platforms for dynamic domain partitioning and required runtime libraries are included in the software package when appropriate.

AVAILABLE PLATFORMS AND PRE-REQUISITES Availability of the ProCAST DMP Version


71


GENERAL REQUIREMENTS In the list below, some global recommendations are given for running ProCAST on the various platforms. Please consult with the local ESI Group support for more information. -

A minimum of 8 Gb (ideally 16Gb) of memory is required to operate the software. More memory is however recommended for large industrial applications.

-

OpenGL hardware graphic accelerator is highly recommended. Screen resolution should be set to at least 1280*1024 with small fonts selected.

-

3.0 GB disk (free) space required in the Program Files folder for complete installation

-

Consult the information provided in the installation directory $PAMHOME/info/README_ProCAST_2014.0 for a complete list of run time libraries and pre-requisites corresponding to each platform.

-

For access to on-line documentation, Firefox (or equivalent) is required on all Linux platforms.

-

For optimal graphics performance on Windows platforms, the installation of the latest graphics drivers and NVIDIA for optimized rendering is recommended.

-

3 button mouse is required (middle mouse button required for dynamic rotations in graphics window with Visual-Cast).

-

ProCAST 2014.0 requires the installation of the Visual-Environment 9.6 version.

-

On Linux and Windows platforms, the icc compiler version 12.1 is used for the solver compilation.

-

To compile User functions, the following compilers should be available on the target platform: ·

Windows : Microsoft Visual C++ 2008 Express Edition

·

Linux : Intel icc compiler version 12.1 or gcc compiler version 3.2.3

AVAILABLE PLATFORMS AND PRE-REQUISITES General Requirements

Insert the back cover image in this header, then position and resize it !

ProCASt

Recommend Documents