Release Notes for POLYFLOW 3.

11
Fluent Inc.
March 16, 2007

Introduction
The POLYFLOW 3.11 release contains enhancements and defect fixes. Enhancements
are listed in Section 2 of this document. Defect fixes are listed in Section 3 of this
document. Known limitations are listed in Section 4.
An up-to-date list of known and fixed defects in this release is accessible from our
online User Services Center (www.fluentusers.com) in the Release Information
section under POLYFLOW 3.11 Product Information.

New Features in POLYFLOW 3.11

New features added in POLYFLOW 3.11 are listed below.
Solver
Pre-processors solver are now influent (time or evolution step fails if a
pre-processor fails)
Upwinding in energy equation for non-isothermal viscoelastic flows is activated when SU is used for stresses
New decoupling strategy for temperature when contact is involved
Models
Simplified viscoelastic model for extrusion (PFLM)
Leonov viscoelastic model for filled rubber
Simple thermo-mechanical analysis after cooling for blow molding and
thermoforming

 Boundary / Initial Condition

More eligible parameters for creation of templates:
inflation pressure
initial temperature, thickness and concentration
CR46912: Improvement of non-conformal boundary conditions (important reduction of required memory)
New boundary condition for species transport: connected boundaries
New calculation method for slipping in MST
Mesh
Miscellaneous adaptive meshing enhancements:
Adaptive Remeshing can now allow a size function along a boundary
that does not depend on the boundary curvature
Improvement of contact detection after adaptive remeshing
Coordinates of previous time step are used as the initialization for
contact after adaptive remeshing:.
CR44512: Progressive volume correction for transient simulations
involving adaptive remeshing in order to avoid the mold erosion
Mapping of fluid points in contact with a mold on the surface of the
mold
Improvement in handling the contact time in case of adaptive remeshing
Addition of all boundaries as canditates for definition of local size
function (adaptive meshing)
Integration of TGrid4.0 for adaptive meshing
1D PMesh can be defined in Gambit
Improved elasticity based remeshing
Parallel Processing
Correction of User Defined Function handling in the solver in parallel
User Interface
POLYMAN: creation of a backup file when saving the *.prj file
A Sub-model can now be defined on subdomains

 Data Import and Export

Creation of a 3D mesh file from a deformed shell; the final calculated
thickness is used to created the 3rd dimension of the 3D mesh.
POLYSTAT: Exportation of trajectories as .fvp files compatible with FieldView
Improvement of the FieldView export of fields defined only on a boundary
Creation of a csv.end file after thickness optimization
Automatic creation of CURVE files is disabled. A new .p3rc keyword for
POLYDATA, allows to reactivate it if necessary
Miscellaneous
Stopping criteria for time/evolution run
CR 51770: 5 tasks can be defined in a POLYDATA session
CR43172, CR46912: One contact time field is generated per contact problem
CR51554: free jet stabilization for Improved Elastic Remeshing
CR51224: evolution on rotation speed was missing in 2.5D axi

Defects Fixed in this Release

The following defects were fixed in POLYFLOW 3.11:
No pressure imposed on moving contact points anymore (CR43934)
Crash POLYDATA (in XFUNCC/84) when the user switches from a multiramp
function to another one (CR52508 - Bug fix)
Crash in POLYDATA after transforming a Generalized Newtonian sub-task
into a viscoelastic one (CR49322 - Bug fix)
POLYMAN hanged while trying to open a different project (CR46748 Bug fix)
Sorting of experimental data is necessary in polyfit (CR48505)
Correction for decoupling temperature for blow molding (CR49400)
Proper calculation of the Volume of liquid post-processor in axi-symmetric
(CR44065)
Sub-model on velocity in 2.5D axisymmetric configuration (CR42698)

Known Limitations in POLYFLOW 3.11

POLYMAN: a running simulation cannot be stopped under Windows 64
POLYMAN: on some platforms, a find upwards in the listing is ineffective
POLYMAN: on some platforms, a new mesh created in POLYFUSE does not
appear in the MeshRepository. It must be imported manually.
POLYMAN: under Linux, the Getting Started can not be opened if there is no
correct association between the MIME type html and a working application.
In such a case, the association must created by the user.
POLYDATA: a material data file cannot be loaded if its pathname is longer
than 78 characters
POLYDATA: problems when the number of input files is greater than 49 for a
Mixing task.
A mesh file cannot contain more than 30 subdomains.
Non-manifold POLYMESH entities cannot be imported into Fieldview