COMSOL Release Notes
COMSOL Release Notes
COMSOL Release Notes
Release Notes
COMSOL Multiphysics Release Notes
© 1998–2017 COMSOL
Protected by U.S. Patents listed on www.comsol.com/patents, and U.S. Patents 7,519,518; 7,596,474;
7,623,991; 8,219,373; 8,457,932; 8,954,302; 9,098,106; 9,146,652; 9,323,503; 9,372,673; and
9,454,625. Patents pending.
This Documentation and the Programs described herein are furnished under the COMSOL Software License
Agreement (www.comsol.com/comsol-license-agreement) and may be used or copied only under the terms
of the license agreement.
Support for implementation of the ODB++® Format was provided by Mentor Graphics Corporation
pursuant to the ODB++ Solutions Development Partnership General Terms and Conditions. ODB++ is a
trademark of Mentor Graphics Corporation.
COMSOL, the COMSOL logo, COMSOL Multiphysics, Capture the Concept, COMSOL Desktop,
LiveLink, and COMSOL Server are either registered trademarks or trademarks of COMSOL AB. All other
trademarks are the property of their respective owners, and COMSOL AB and its subsidiaries and products
are not affiliated with, endorsed by, sponsored by, or supported by those trademark owners. For a list of such
trademark owners, see www.comsol.com/trademarks.
Version: COMSOL 5.3
Contact Information
Visit the Contact COMSOL page at www.comsol.com/contact to submit general
inquiries, contact Technical Support, or search for an address and phone number. You can
also visit the Worldwide Sales Offices page at www.comsol.com/contact/offices for
address and contact information.
If you need to contact Support, an online request form is located at the COMSOL Access
page at www.comsol.com/support/case. Other useful links include:
COMSOL Multiphysics 10
General New Functionality . . . . . . . . . . . . . . . . . . . 10
New Functionality in the Application Builder . . . . . . . . . . . . 10
New Functionality in COMSOL Server . . . . . . . . . . . . . . 12
New and Improved General Functionality in COMSOL Multiphysics . . . 13
New Geometry and Mesh Functionality . . . . . . . . . . . . . . 15
New and Updated Operators, Functions, and Definitions . . . . . . . 18
New Functionality in Studies and Solvers . . . . . . . . . . . . . . 18
New and Improved Results and Visualization Functionality . . . . . . . 20
®
New Java API Methods . . . . . . . . . . . . . . . . . . . . 22
General Backward Compatibility Considerations . . . . . . . . . . . 23
Backward Compatibility with Version 5.2a . . . . . . . . . . . . . 23
Backward Compatibility with Version 5.2 . . . . . . . . . . . . . . 24
Backward Compatibility with Version 5.1 . . . . . . . . . . . . . . 25
Backward Compatibility with Version 5.0 . . . . . . . . . . . . . . 25
Backward Compatibility with Version 4.4 . . . . . . . . . . . . . . 26
Backward Compatibility with Version 4.3b . . . . . . . . . . . . . 27
Backward Compatibility with Version 4.3a . . . . . . . . . . . . . 29
Backward Compatibility with Version 4.3 . . . . . . . . . . . . . . 30
AC/DC Module 32
New Functionality in Version 5.3 . . . . . . . . . . . . . . . . . 32
New and Updated Application in Version 5.3 . . . . . . . . . . . . 32
Backward Compatibility with Version 5.2 and older . . . . . . . . . . 33
Backward Compatibility with Version 5.0 and older . . . . . . . . . . 33
Acoustics Module 35
New Functionality in Version 5.3 . . . . . . . . . . . . . . . . . 35
Backward Compatibility with Version 5.2 . . . . . . . . . . . . . . 35
Backward Compatibility with Version 5.1 . . . . . . . . . . . . . . 36
Backward Compatibility with Version 4.3a and Older . . . . . . . . . 36
Backward Compatibility with Version 4.3 . . . . . . . . . . . . . . 36
CONTENTS |3
Batteries & Fuel Cells Module 37
New Functionality in Version 5.3 . . . . . . . . . . . . . . . . . 37
Backward Compatibility with Previous Versions . . . . . . . . . . . 39
CFD Module 43
New Functionality in Version 5.3 . . . . . . . . . . . . . . . . . 43
New Models in Version 5.3 . . . . . . . . . . . . . . . . . . . 44
Backward Compatibility with Version 5.0 . . . . . . . . . . . . . . 44
Backward Compatibility with Version 4.4 . . . . . . . . . . . . . . 45
Backward Compatibility with Version 4.3b . . . . . . . . . . . . . 46
Backward Compatibility with Version 4.3a . . . . . . . . . . . . . 46
Backward Compatibility with Version 4.3 . . . . . . . . . . . . . . 47
Corrosion Module 57
New Functionality in Version 5.3 . . . . . . . . . . . . . . . . . 57
New and Updated Models in Version 5.2a . . . . . . . . . . . . . 58
Backward Compatibility with Earlier Versions . . . . . . . . . . . . 58
4 | CONTENTS
Electrochemistry Module 60
New Functionality in Version 5.3 . . . . . . . . . . . . . . . . . 60
Backward Compatibility with Previous Versions . . . . . . . . . . . 61
Electrodeposition Module 62
New Functionality in Version 5.3 . . . . . . . . . . . . . . . . . 62
Backward Compatibility with Previous Versions . . . . . . . . . . . 63
Fatigue Module 64
New Functionality in Version 5.3 . . . . . . . . . . . . . . . . . 64
Geomechanics Module 66
New Functionality in Version 5.3 . . . . . . . . . . . . . . . . . 66
MEMS Module 86
New Functionality in Version 5.3 . . . . . . . . . . . . . . . . . 86
Backward Compatibility with Version 5.2 . . . . . . . . . . . . . . 86
Backward Compatibility with Version 4.3b . . . . . . . . . . . . . 86
Microfluidics Module 87
Backward Compatibility with Version 4.3a . . . . . . . . . . . . . 87
Backward Compatibility with Version 4.3 . . . . . . . . . . . . . . 87
CONTENTS |5
Molecular Flow Module 88
New Functionality in Version 5.3 . . . . . . . . . . . . . . . . . 88
Backward Compatibility with Version 5.0 and Earlier . . . . . . . . . 88
Optimization Module 93
New Functionality in Version 5.3 . . . . . . . . . . . . . . . . . 93
Backward Compatibility with Version 4.3a . . . . . . . . . . . . . 93
6 | CONTENTS
Backward Compatibility with Version 5.0 . . . . . . . . . . . . . 106
RF Module 108
New Functionality in Version 5.3 . . . . . . . . . . . . . . . . 108
New and Updated Models and Applications in Version 5.3 . . . . . . 109
Backward Compatibility with Version 4.3a . . . . . . . . . . . . 110
CONTENTS |7
LiveLink™ for Excel® 127
Supported Versions . . . . . . . . . . . . . . . . . . . . . 127
New Functionality in Version 5.3 . . . . . . . . . . . . . . . . 127
8 | CONTENTS
1
Release Notes
9
COMSOL Multiphysics
General New Functionality
P R E F E R E N C E S TA K E N F R O M P R E V I O U S VE R S I O N
By default, the installation of version 5.3 reuses most preference settings from the
previous installation, so that you do not need to redo changes to the factory settings
for your specific preferences.
• You can now create application methods, for use in applications like in earlier
versions, and model methods, which are new in this version. Model methods can be
used in the Model Builder as a complement to the model tree for automating special
sequences or tasks.
• When hovering the mouse pointer over a property name, a declaration, or a shortcut
in a method editor window, a tooltip containing information about the property
name, declaration, or shortcut is displayed. When hovering the mouse pointer over
a name corresponding to an entity in the application part of the API (such as a form
or a form object), information about what type of object the name represents (such
as Input Field, Button, Form, or Menu) is displayed in a tooltip.
• It is now possible to automatically declare the type of a local variable. For example,
you can type x = model.geom() and click the Create Local Variable button on the
Method ribbon tab. The code is then changed to GeomList x = model.geom().
• The Extract Variable button on the Method ribbon in previous versions has been
replaced with a new button called Use Shortcut. Clicking the Use Shortcut button
creates a shortcut corresponding to the extracted code instead of a hidden instance
variable, which was what clicking the Extract Variable button created in previous
versions.
COMSOL MULTIPHYSICS | 11
• New application language methods have been introduced to create, load, and
remove models without having to specify a model tag. The create and load methods
generate a unique tag for the new model, and the remove method takes a model
object instead of a model tag. The syntax is:
Model createModel();
void removeModel(Model model);
Model loadModel(String filename);
Model loadProtectedModel(String filename, String password);
Model loadRecoveryModel(String folderName);
• Two new standard commands, Select All and Clear Selection, have been added to
the Application Builder. The commands are similar to their Model Builder versions
but work on a target Graphics form object. Two new methods, selectAll and
clearSelection, have been added to the application API. In the Application
Builder, the new commands appear in command sequences (for a button, for
example) under GUI Commands>Graphics Commands. The syntax for the new
methods:
void clearSelection(FormObject graphics);
void clearSelection(String graphics);
void selectAll(FormObject graphics);
void selectAll(String graphics);
• A Go to Source button has been added to the Settings window for local methods,
which, when clicked, causes the form object, which the local method belongs to, to
be selected in the form editor.
• Ctrl+/ is now an alternative shortcut for auto completion in the method editor.
COMSOL MULTIPHYSICS | 13
forces are introduced. This new condition removes the need to constrain rigid body
motion by inserting point constraints in such cases.
The Symmetry boundary conditions are also available for the Solid Mechanics
interface in this version without any additional module requirement.
• The Help and Documentation windows have been updated and now includes a
breadcrumb trail at the top, indication the location in the documentation set for the
information that is displayed.
• For physics interfaces that use symbols to indicate, for example, boundary
conditions, you can now control the general display of physics symbols and also
show and hide all physics symbols in the physics interface using the Physics Symbols
section in the Settings window for the main physics interface node. When physics
symbols are enabled, you can also control their display individually in the settings
for each physics interface node that supports symbols.
• The hide functionality in the graphics windows has been simplified. The View ribbon
tab now has a single Hide button instead of, in previous versions, separate Hide for
Geometry, Hide for Physics, and Hide for Mesh buttons. This button adds the type of
hide feature suitable for the current context.
• The Selection List window now indicated which geometric indices that are selected.
• The default font handling has been improved to better handle non-Latin fonts. You
can now specify the font to use directly in the installer when installing using a
non-Latin (Asian) language.
• The local table for interpolation functions, parameters, variables, polygons, and
interpolation curves now includes a Clear Table button.
• For model inputs, a Go to Source button is now available for moving to the node in
another physics interface that provides the input.
• The COMSOL Launchers folders in the version 5.3 installation now includes dedicated
launchers for all applicable graphics rendering options (DirectX, OpenGL, and
software rendering).
• Triple-clicking in text fields now selects the whole line in all versions of the
COMSOL Desktop.
• On macOS, Command-. (that is, the Command button and period) is now available
for stopping a method as an alternative to Ctrl+Pause.
GEOMETRY FUNCTIONALITY
General Improvements
In version 5.3, there are significant improvements in execution time, memory usage,
and disk usage for parts of the functionality in the geometry sequences.
New Functionality
• Coordinate systems in the geometry: In geometric primitives and transform features
in 3D, you can specify the settings in a local coordinate system given by a work
plane. This makes it easier to position new objects relative to existing objects.
• Coordinate systems from geometry under Definitions. A new coordinate system
type, System from Geometry, creates a coordinate system from a work plane. This
makes it easy to align a coordinate system with geometric entities. Some other
coordinate system types can also be defined relative to a work plane.
• Combined coordinate systems under Definitions. You can use the new Combined
System node to create a coordinate system that has different definitions on different
domains. This is useful when an anisotropic material has different orientations in
different domains.
• A new virtual operation, Remove Details, automatically generates a sequence of
virtual operations that removes details smaller than a given size. The Remove Details
node is available on the Virtual Operations menu. The generated sequences of virtual
operations are possible to edit if needed.
• Extrude enhancements: You can now extrude until you hit a selected vertex and
extrude in both directions at the same time.
• A new Line Segment feature that constructs a line segment between selected vertices
or given point coordinates.
• Enhancements for the Cylinder Selection and Disk Selection features: It is now
possible to specify inner radius and sector angles.
• In the Cross Section feature, you can now generate 2D selections from 3D selections.
• In the Sweep feature, you now get better results when sweeping along a chain of
edges, thanks to the new Parameterization and Smooth edge connections settings.
• When visualizing a work plane, its local coordinate system triad xw, yw, zw is also
visualized.
• It is now possible to select a geometry object in draw mode and then delete it by
pressing the Delete key.
COMSOL MULTIPHYSICS | 15
• For geometry part variants, there is a new Show as variant in part library check box
in the settings of a geometry part. This new check box makes it possible to have an
MPH file that contains different variants of a part. The variants typically differ only
in the set of input parameters. When loading the part, a dialog box appears where
you can select which variant you want to use. In version 5.3, this functionality is
used by parts in the Ray Optics part library.
• For import of geometry using MPHBIN or MPHTXT files, there is a new
possibility to exclude result from virtual operations in order to make sure that the
imported geometry is not virtual.
MESHING FUNCTIONALITY
• Automatic transitions with pyramid elements are now available when interfacing a
swept hex or prism mesh with a tetrahedral mesh. There is no longer a need for
converting a swept mesh before meshing the surrounding domain with the Free
Tetrahedral operation.
• There is a new Size Expression attribute node, which you can use to define a
space-varying mesh size based on an expression using the spatial coordinates.
• There is also a new Adapt node, which you can use to perform mesh adaptation.
Such Adapt nodes are created automatically in the mesh refinement meshing
sequences when using mesh adaptation from a study step.
• There is a new optimization option in the Free Tetrahedral operation that you can
use if you want to maximize the size of the smallest element while still trying to
respect the desired local element size. This optimization can improve the
performance when solving problems using explicit time stepping.
COMSOL MULTIPHYSICS | 17
remeshing caused by a physics-controlled mesh, you can switch to a user-controlled
mesh.
SOLVER FUNCTIONALITY
• An improved aggregated AMG solver using a smoothed aggregation multigrid
methods is now available and is possible to use as an alternative to GMG for
fluid-flow models, for example.
• The solver log now contains more information about the use of available cores and
used and available memory during the solution process.
• A new option for the direct solvers makes it possible to automatically switch to
out-of-core storage if the estimated memory (for LU) is exhausting the physically
available memory.
• For small eigenvalue problems, it is now possible to specify that all eigenvalues are
returned from the solver.
• The scaled absolute tolerance is now proportional to the relative tolerance by
default.
• The FFT solver can now handle larger data sets. If needed, you can save
intermediate FFT data to disk to reduce the memory requirements. You can also
choose Times to store with the options Time steps taken by solver (the default) and
From list. In the latter case, the output data is interpolated. This way, you can
decrease the amount of data stored in MPH files.
• For manual time stepping using the BDF method, you can now control the BDF
order and time steps in the Time Stepping section.
• In parametric sweeps and batch sweeps, continuing the solver and getting the initial
value are now supported. The initial value for a parametric sweep uses the first
parameter value.
• For a batch process, you can now stop it after a given time from the command line
using the option -stoptime <time to stop in seconds>.
• The Intel MKL has been upgraded to Intel MKL 2017 and IMPI 2017.
COMSOL MULTIPHYSICS | 19
New and Improved Results and Visualization Functionality
COMSOL MULTIPHYSICS | 21
• In the Global Matrix Evaluation node, From inverse Maxwell to mutual capacitance is a
now transformation option.
• A new sequence type, Global parameter, makes it possible to animate over global
parameters in the model for more flexible animations (animating over view
parameters to simulate camera-based animation, for example).
FRAME CONTROL
In previous versions of COMSOL Multiphysics, it was possible to apply multiple
frame-controlling physics on the same selection. For example, it was possible to add
two Solid Mechanics interfaces (with the Include geometric nonlinearity option enabled)
on the same selection and solve. In this case, an “override rule” was applied between
the controlling physics, effectively meaning that the last physics in the tree had control
of the frame deformation for the overlapping domains. This situation could cause
unexpected results.
In version 5.3, multiple physics interfaces controlling the same frame are not allowed
on the same selection and will cause an error when trying to solve. However, it is still
possible to use multiple frame-controlling physics with overlapping selection, but you
now have to explicitly disable frame control on all but one of the physics. This gives
you better control on what is going on. The functionality to disable frame control for
physics has been incorporated in the Settings window for study steps to allow choosing
different physics to control the frame in different study steps.
Frame-Scoped Variables
Certain variables pertaining to frame deformation are now defined with “frame
prefix”. For example, the relative element volume is now called spatial.relVol.
COMSOL MULTIPHYSICS | 23
Previously, these variables were added by the physics interface controlling the frame
deformation so they used a “physics prefix” (for example, ale.relVol). For backward
compatibility of old models, the physics interfaces still define the old variables, but they
are aliases of the new frame variables.
feature("foo").feature("prob1").feature("error1")
feature("foo").problem("error1")
CREATING SELECTIONS
In version 5.2, the selresult property replaced the createselection property.
createselection is still supported for backward compatibility.
MESH PARTS
For backward compatibility regarding STL/VRML import, and for COMSOL API
compatibility, the old user interface for mesh import (with a specified file name and
import properties) and the corresponding properties are available in the COMSOL
API but not in the COMSOL Desktop, unless it is the active option. This means that
the old user interface can only be reached if the filename is set in combination with the
STL import type (the API type stlvrml), which cannot be done from the new user
interface.
MESH IMPORT
The method used to automatically partition the boundary of imported meshes in 3D
has been improved. If you have an existing model, you can work with it without being
affected. However, if you click the Import button of the Import feature in the meshing
COMSOL MULTIPHYSICS | 25
sequence, the file is read again and the new partitioning method is used. The exception
is if the Import feature had Boundary partitioning set to Manual. In this case, the
modified parameter values are preserved under the Feature detection setting, which
uses the same algorithm as in version 5.0.
COMSOL tries to map the old selection on boundaries to the new boundaries, but it
is not always possible to do accurately when new faces have appeared or old faces have
disappeared. You may have to manually review and update boundary, edge, and point
selections after reimporting the mesh.
If you have a Java® or MATLAB® program that imports meshes, the number of
geometric entities may have changed compared to older versions.
SECURITY SETTINGS
In version 5.2a, the Allow external process and libraries check box on the Security page
in the Preferences dialog box is cleared by default to not allow applications to start
external processes on the computer. The default setting in 5.0 is set to allow such
external processes.
MESH IMPORT
An edge in an imported mesh that has a common start and end vertex, or that lacks
start and end vertices, is now split into two edges with distinct start and end vertices.
For meshes where this happens, the numbering of all geometric entities may change
when the mesh is rebuilt.
TR A N S P O R T O F D I L U T E D S P E C I E S
®
Running Java -files from previous versions may fail due to the new default name for
the Transport of Diluted Species interface. This can be avoided by adding a command
that specifies the identifier in accordance with the name of the interface. For example,
when creating an interface using the old name (chds):
model.physics("chds").identifier("chds");
The Java® API syntax for creating and accessing vectors and tensors in the Transport
of Diluted Species interface has changed as well as the syntax for setting physics
properties. This does not affect MPH-files. See the backward compatibility notes for
the Chemical Reaction Engineering Module for additional information that also
applies to the Transport of Diluted Species interface.
DOCUMENTATION
The COMSOL Multiphysics Programming Reference Manual replaces the
COMSOL API for Use with Java ® Reference Manual.
COMSOL MULTIPHYSICS | 27
unless the continuation algorithm would not have been used for this model in previous
versions (for example, if multiple parameters are used or if the parameter list is not
monotonous).
Laminar inflow and laminar outflow are available in the fluid flow physics interfaces in
the following modules:
VE L O C I T Y / A C C E L E R A T I O N I N T E G R A T I O N V A R I A B L E
For the Solid Mechanics interface (and all related multiphysics interfaces) and the
Truss interface, the help variable u0 (velocity integration variable) is used in Prescribed
Velocity and Prescribed Acceleration features for Time Dependent study types. This
This change can cause the solvers to take more nonlinear steps for stationary problems
and more time steps for time-dependent problems, and it may also lead to convergence
problems. For such cases, use the No method to obtain the old behavior. However,
doing so can hide numerical problems and potentially lead to large numerical errors.
TE R M I N A T I O N C R I T E R I O N F O R S T A T I O N A R Y S O L VE R S
The default termination criterion for stationary solvers has changed. In 4.3a, the
settings corresponded to Solution; now, the default is Solution or residual. This change
in default termination criterion might affect models created in earlier versions of
COMSOL Multiphysics if you regenerate the solver sequence in 5.2a.
COMSOL MULTIPHYSICS | 29
Euler method (in terms of the initial step). This value can improve the accuracy of the
initialization step but can also affect the start-up of some models. The default value is
0.001 (this differs from earlier versions, which used a value of 1). When opening
models created in version 4.3a or earlier, the value for this fraction is set to 1 to
maintain compatibility with those versions.
N E W TE R M I N O L O G Y F O R C O N S T R A I N T TY P E S
The following constraint types have new names in version 5.2a:
• Bidirectional, symmetric is now Apply reaction terms on: All physics (symmetric).
• Unidirectional is now Apply reaction terms on: Individual dependent variables.
• Symmetry
• The Slip option in the Wall feature
These boundary conditions are now formulated using the same set of Lagrange
multipliers as all of the other boundary conditions in the Laminar Flow interface. The
Lagrange multiplier un_lm has been removed.
Models saved in version 4.3 will include un_lm until the model is re-solved. In some
cases, occurrences of un_lm in the solver sequence must be replaced manually. This is
the case if un_lm was the only Lagrange multiplier component in a segregated group
or the only Lagrange multiplier component of a Vanka smoother. Alternatively, you
can generate a new automatic solver sequence. Models saved in versions earlier than
4.3 must either be re-solved in version 5.2a for postprocessing, or opened and re-saved
in version 4.3 before being opened in version 5.2a.
COMSOL MULTIPHYSICS | 31
AC/DC Module
New Functionality in Version 5.3
• The Touchscreen Simulator app has been updated to use the faster Stationary
Source Sweep study.
• The Capacitor Tunable model has been updated to use the new Electrostatics,
Boundary Elements interface.
• A tutorial series on three-phase submarine cable modeling.
• Axisymmetric model of a 3D inductor.
• 3D model of a permanent magnet motor
• 3D power switch with motion
• Topology optimization of a loudspeaker magnet
COIL FEATURES
Multi-Turn Coil features in old models will be mapped to the new Coil feature using the
Homogenized Multi-Turn Conductor model. Single-Turn Coil features in old models
will import as is with a warning that the feature is obsolete and will be removed in
future versions.
The User Defined Coil Geometry subnode, which is available for 3D Coil nodes with the
User-Defined Coil type, is now a domain feature. You can now select coil input and
output boundaries using the new Input and Output subnodes. The selection is set up
correctly when opening old models.
The Coil Geometry Analysis study step (formerly Coil Current Calculation) will now
solve for all of the coils in the active interfaces. To solve only for specific coils (specified
using the CoilName property), set the SpecifyCoil property to 1.
The default solver sequence generated by the Coil Geometry Analysis is different in
version 5.1. Code that accesses specific solver features in the generated solver sequence
may need to be reviewed.
AC/DC MODULE | 33
OTHER COIL IMPROVEMENTS
Harmonic Perturbation subnodes under coil features (Single-Turn Coil, Multi-Turn Coil)
are now global features, so the call to the create method should use the appropriate
space dimension (-1):
model.physics("mf").feature("stcd1").create("hp1",
"CoilHarmonicPerturbation", -1);
Global features have no selections, so code that accesses the selection of the Harmonic
Perturbation features may need to be reviewed.
Some of the improvements in the 3D Multi-Turn Coil features may require a review of
existing code that uses the COMSOL API.
Subnodes required to set up the coil features are now added automatically. Existing
code that uses the coil features may need to be updated.
The parameters eCoil and length have been moved from the Multi-Turn Coil features
(boundary and domain) to the new subfeature UserDefinedCoilGeometry.
OTHER IMPROVEMENTS
New functionality introduced in version 5.1 is disabled by default when opening
models created in previous versions:
This functionality can be enabled using the appropriate inputs in the Settings window.
Refer to the documentation for the individual features for more details.
• Perfectly matched layers are now available for the Pressure Acoustics, Transient
Interface.
• A new Thermoviscous Acoustics, Transient interface.
• The Poroelastic Waves Interface has been updates with a new Biot-Allard model to
include both thermal and viscous losses.
• The Convected Wave Equation, Time Explicit interface is now supported in 2D
axisymmetric geometries.
• Many physics interfaces and multiphysics couplings now provide predefined iterative
solver suggestions.
• The transient solver is now controlled from the physics nodes in a new Transient
Solver Settings section.
• Improved stabilization methods for the Linearized Navier-Stokes Physics Interfaces.
• Serendipity elements are now available in most acoustics interfaces.
• Preview evaluation plane functionality for far field and directivity.
• Beam width calculation functionality for 1D far-field plots.
• Updated interior perforate plate boundary condition in the Pressure Acoustics,
Frequency Domain interface.
• Heat source for the Pressure Acoustics interface.
• Improved ray acoustics in 2D axisymmetric geometries.
• New reflection coefficient models for wall features in ray tracing.
• New ray termination feature.
ACOUSTICS MODULE | 35
model.physics("acpr").feature("pwr1").feature("ipf1").
set("c", "acpr.c_c");
For users with licenses for both the Electrodeposition Module and the Batteries & Fuel
Cells Module: The Nondeforming Boundary and Deforming Electrode Surface
multiphysics features now support couplings to the Electrode Surface node in the
Lithium-Ion Battery and Battery with Binary Electrolyte interfaces.
TR A N S P O R T O F C O N C E N T R A T E D S P E C I E S I N T E R F A C E
See Chemical Reaction Engineering Module.
N E W F U N C T I O N A L I T Y I N VE R S I O N 5 . 3
The LiveLink™ interface now supports Solid Edge® ST9.
B A C K W A R D C O M P A T I B I L I T Y W I T H VE R S I O N 5 . 0
The default value for the keepfree property of the LiveLinkSolidEdge function is
now set to on. Previously, the default was set to off.
N E W F U N C T I O N A L I T Y I N VE R S I O N 5 . 3
• The LiveLink™ interface now supports SOLIDWORKS® 2017.
• For assemblies, the LiveLink™ interface now automatically synchronizes selections
that are defined in the component files. Previously, all selections had to be defined
in the synchronized assembly file.
• The new tutorial Stress Analysis of a Pipe Fitting has been added to demonstrate
how to set-up a simulation on a 2D cross-section of a 3D geometry that has been
synchronized using the LiveLink™ interface.
B A C K W A R D C O M P A T I B I L I T Y W I T H VE R S I O N 5 . 0
The default value for the keepfree property of the LiveLinkSOLIDWORKS function
is now set to on. Previously, the default was set to off.
CAD IMPORT MODULE, DESIGN MODULE, AND LIVELINK™ PRODUCTS FOR CAD | 41
Backward Compatibility with Previous Versions
B A C K W A RD C O M P A T I B I L I T Y W I T H VE R S I O N 5 . 2
• If you have not set the relative repair tolerance repairtol, you will get the new
default repair tolerance type: auto. This will result in a valid geometry in almost all
cases. In extreme cases, the result can have a different topology than in 5.2.
• In rare cases, if you have set the repairtol tolerance, version 5.2a can fail when
building the geometry. If so, set repairtoltype to auto (select Automatic from the
Repair tolerance list) to get the 5.2 behavior.
TU R B U L E N T F L O W, V 2 - F I N T E R F A C E
2
The v -f turbulence model is an extension of the k-ε model with the turbulent
viscosity based on the cross-stream velocity fluctuations. This makes it possible to
model turbulence anisotropy and to distinguish between wall blockage and
low-Reynolds-number effects.
E N H A N C E D WA L L TR E A T M E N T
The Single-Phase Flow interfaces have a new Wall feature, and for turbulent flows
there is a new Wall Treatment property. The new Wall feature has a simplified user
interface and automatically accounts for moving meshes.
The Wall Treatment Property introduces an Automatic option for all turbulence
models except the k-ε model. Automatic wall treatment gives an accurate
low-Reynolds-number formulation in regions where the mesh is fine enough and falls
back on a wall-function formulation in regions with a coarser mesh.
Models created in previous versions of COMSOL Multiphysics open without the new
Wall Treatment Property and with a legacy Wall Feature. To guarantee backward
compatibility for Model Java® files using a Single-Phase Flow, Brinkman, or High
Mach Number Flow interface, the following line should be added following the line
creating the interface,
model.physics("phys").prop("PhysicalModelProperty").
set("BackCompState", 0);
CFD MODULE | 43
A U T O M A T I C TR A N S L A T I O N B E T W E E N TU R B U L E N C E M O D E L S
The global feature Generate New Turbulence Model Interface creates a new Turbulent
Flow interface (including a new study) from an existing one. Initial values and
boundary conditions for turbulence variables not present in the original model are
estimated using the turbulent viscosity and the turbulent length scale.
I NT ER I O R WA LL BO U ND AR Y C O NDI T I ON I N PORO U S D O M AI NS
The Interior Wall boundary condition is now available in the Darcy’s law and
Two-Phase Darcy’s Law interfaces and is applicable in porous domains in the
Single-Phase Flow and Brinkman interfaces.
T H I N B A R R I E R B O U N D A R Y C O N D I T I O N I N T H E D A RC Y ’S L AW I N T E R F A C E
The Thin Barrier boundary condition defines a permeable wall on an interior
boundary.
N E W TU T O R I A L M O D E L S I N H I G H M A C H N U M B E R F L OW
• Euler Bump 3D
• Expansion Fan
• Supersonic Ejector
TR A N S P O R T O F C O N C E N T R A T E D S P E C I E S
See Chemical Reaction Engineering Module.
INLET FEATURE
The old inlet features still exist, but have been excluded from the physics context
menu. Old models retain old Inlet features, but adding a new Inlet feature comes with
the new functionality. Old Model Java® files create Inlet features of the old types. The
Normal stress condition can still be prescribed on inlets using an Open Boundary or a
Boundary Stress feature.
N E W N A M E S F O R M A S S TR A N S P O R T I N T E R F A C E S
Running Model Java® files from previous versions may fail due to the new default
names in the Transport of Diluted Species and Transport of Concentrated Species
interfaces. This can be avoided by adding a command that specifies the identifier in
accordance with the Name of the interface. For example, when creating a Transport of
Concentrated Species interface using the old name (chcs):
model.physics("chcs").identifier("chcs");
CFD MODULE | 45
Backward Compatibility with Version 4.3b
B U B B L E - I N D U C E D TU R B U L E N C E I N B U B B L Y F L OW
Equation terms accounting for bubble-induced turbulence in the Turbulent Bubbly
Flow interface are now added correctly. As a result, models with Turbulent Bubbly
Flow now show higher levels of turbulence.
FLUID-STRUCTURE INTERACTION
The Fluid-Structure Interaction (FSI) multiphysics interface has been updated. The
separate vWall field is no longer required and has been removed. FSI models from 4.3
and earlier versions that include Time Dependent study steps will be affected in the
following ways:
• Model files for Java® will fail. Any reference to the vWall field must be removed.
• Models older than 4.3 (that is, 4.2a and older) must clear their time-dependent
solutions when opened in 5.2a. An alternative procedure is to:
- Open the model in version 4.3.
FSI models with only stationary study steps will not be affected. Note that vWall will
still be available as a variable. Hence, references to fsi.vWall made in, for example,
another physics interface still work.
CFD MODULE | 47
Laminar Flow and Creeping Flow
• Symmetry
• The Slip boundary condition in the Wall feature
Rotating Machinery
• Symmetry
• The Slip boundary condition in the Wall feature
• The Wall Functions boundary condition in the Wall feature (turbulent flow only)
• The Moving Wall (wall functions) boundary condition in the Wall feature (turbulent
flow only)
• Rotating Wall (turbulent flow only)
Bubbly Flow
• Symmetry
• The Slip boundary condition for the liquid phase in the Wall feature
• The Wall Functions boundary condition for the liquid phase in the Wall feature
(turbulent flow only)
Mixture Model
• Symmetry
• The Slip boundary condition for the mixture in the Wall feature
• The Wall Functions boundary condition for the mixture in the Wall feature
(turbulent flow only)
CFD MODULE | 49
These boundary conditions are now formulated using the same set of Lagrange
multipliers as all of the other boundary conditions for the dependent velocity variables.
The previously used Lagrange multiplier un_lm has been removed.
When you open models saved in version 4.3, they include un_lm until the model is
re-solved. In some cases, occurrences of un_lm in the solver sequence must be replaced
manually. This is the case if un_lm was the only Lagrange multiplier component in a
segregated group or the only Lagrange multiplier component of a Vanka smoother.
Alternatively, you can generate a new automatic solver sequence. Models saved in
versions prior to version 4.3 must either be re-solved in version 5.2a for
postprocessing, or opened and re-saved in version 4.3 before being opened in version
5.2a.
Weak constraints for the Interior Wall feature are no longer available.
R E V I S I O N O F T H E TU R B U L E N C E M O D E L S
The formulations of some variables in the turbulence models have been revised in
order to improve accuracy. Models using a turbulence model can display a different
convergence behavior in version 5.2a than in version 4.3 and the results can differ
slightly between the versions.
N E W TR A N S P O R T I N D I L U T E D S P E C I E S I N F R A C T U RE S I N T E R F A C E
The new Transport in Diluted Species in Fractures interface is used to model mass
transport along thin fractures occurring in solid or porous media. The interface is
defined and solved on boundaries in the model geometry, assuming that the fracture
thickness is very small compared to its other dimensions.
Change this to
TR A N S P O R T O F C O N C E N T R A T E D S P E C I E S I N T E R F A C E
In version 5.1, the spatial direction indicator string (x, xy, and so on) has been moved
to the end of the variable name. This applies to all vector and tensor variables generated
by the interface.
For example, the diffusive flux vector components have changed (in 5.0 and earlier)
from
The surface species name needs to be included in the first argument of the set method.
In order to run Model Java® files from previous versions, apply the syntax changes as
shown in the example below:
The bulk species name needs to be included in the first argument of the setIndex
method. Apply the Java® API syntax changes as shown in the example below:
model.physics("sr").feature("sp1").set("rho_0", "rhocb1");
model.physics("sr").feature("sp1").set("rho_1", "rhocb2");
Apply the Java® API syntax changes as shown in the example below:
CORROSION MODULE | 57
• New tutorial models:
- The Atmospheric Corrosion of a Busbar model demonstrates a simulation of
atmospheric galvanic corrosion of a busbar.
- The Estimation of Corrosion Kinetics Parameters tutorial shows how to use the
Optimization interface to perform electrode kinetics parameter estimations based
on polarization data. This model requires the Optimization Module.
M O N O P I L E W I T H D I S S O L V I N G S A C R I F I C I A L A N O D E S TU T O R I A L
The new Monopile tutorial demonstrates how the Sacrificial Edge Anode node can be
used in cathodic protection simulations.
UPDATED MODELS
• The Cathodic Protection of Steel in Reinforced Concrete model has been updated
to use the new Primary Condition (Thermodynamic Equilibrium) electrode
kinetics.
• The Diffuse Double Layer model has been updated to use the new
Nernst-Planck-Poisson Equations multiphysics interface.
ELECTROCHEMISTRY MODULE | 61
Electrodeposition Module
New Functionality in Version 5.3
The following new functionality is available:
ELECTRODEPOSITION MODULE | 63
Fatigue Module
New Functionality in Version 5.3
VIBRATION FATIGUE
Vibration Fatigue is a new type of fatigue damage evaluation in the Fatigue interface
based on a frequency domain analysis containing results for a number of frequencies.
It can for example be used for predicting the results from the common type of
experiment where a structure is subjected to an excitation with increasing frequency,
sometimes called a sine sweep. The following types of descriptions are available:
VISCOPLASTIC STRAINS
In the fatigue criteria based on inelastic strains, it is now possible to select also
viscoplastic strains. This is an effect of the fact that a clear distinction between creep
strains and viscoplastic strains has been introduced in the Nonlinear Structural
Materials Module.
The same is true for energy based criteria, where there is now a distinction between
energy dissipated by creep and by viscoplasticity.
This will affect existing applications with fatigue evaluation based on the Anand
viscoplastic material model. Previously the strains from this material model were
referred to as creep strains. The conversion is automatic when opening an .mph file
from a previous version.
When using the API, however, you will need to replace expressions like
model.physics("ftg").feature("elif1").set("strainTypeCM", "Creep")
by
model.physics("ftg").feature("elif1").set("strainTypeCM",
"Viscoplasticity")
should be replaced by
model.physics("ftg").feature("ener1").set("ftgEnerType",
"Viscoplasticity")
FATIGUE MODULE | 65
Geomechanics Module
New Functionality in Version 5.3
A S S O C I A T E D F L OW R U L E F O R TRE S C A Y I E L D F U N C T I O N
An associated flow rule has been added to the Tresca yield function in Plasticity. As
before, the default flow rule is based on using the von Mises yield surface as plastic
potential.
In most cases, the old physics scope variables can still be accessed, so you should not
experience any backward compatibility problems, even if you have used such variables
in your own expressions.
H E A T A N D M O I S T U RE TR A N S P O R T
A set of new interfaces and features is available for modeling coupled heat and moisture
transport in air and building materials. They complete the features already available in
Version 5.2a for the modeling of heat and moisture transport in building materials, and
allow you to create models where the air and building material domains are
automatically coupled.
Moisture transport by convection and diffusion in air is handled by the new Moisture
Transport in Air interface, which adds the Moist Air node as default model. You can
account for the turbulent mixing caused by eddy diffusivity in turbulent moisture
convection by adding the Turbulent Mixing subfeature under the Moist Air node. The
Moist Surface and Wet Surface boundary conditions provide modeling of evaporation
and condensation on boundaries. Finally, this new version of the Moisture Transport
interface benefits from all the functionalities already available for moisture transport in
building materials in Version 5.2a (Building Material, Moisture Source, Moisture Content,
and so on).
The new Moist Air version of the Heat and Moisture Transport interface is found (along
with the Building Materials version) under the new Heat and Moisture Transport group
in the Heat Transfer branch in the model wizard. It adds the Heat Transfer in Moist Air
interface, the Moisture Transport in Air interface, and the Heat and Moisture
multiphysics node.
The Heat Transfer in Moist Air interface is a new version of the Heat Transfer
interface, only available with the Moist Air version of the Heat and Moisture Transport
interface, and having the new Moist Air domain feature as default model.
The new Moist Air domain feature of Heat Transfer interface corresponds to a preset
version of the Fluid feature, with Fluid type set to Moist air. With the predefined
multiphysics interface, the default Input quantity is set to Relative humidity, and the
required inputs are taken from the multiphysics coupling node.
H E A T TR A N S F E R M O D U L E | 67
Finally, the following improvements have been added to the Moisture Transport
interfaces:
• New default solver settings have been defined to improve convergence in study steps
solving for the Moisture Transport interface: the default BDF order is now 2 in Time
Stepping section; the Number of iterations in the Method and Termination section has
been increased to 2 for the segregated step containing the relative humidity; and the
default tolerance has been set to 1e-4. These last two new settings improve the
quality of the solution.
• The Thin Moisture Barrier feature has been modified to be in better accordance with
the material properties available for thin building materials. The default option
models a vapor diffusion barrier, for which three alternative sets of material
properties can be specified, depending on availability. The second option still allows
to set a user-defined value for the Moisture Transfer Coefficient.
H E A T TR A N S F E R I N T H E F RE Q U E N C Y D O M A I N
The Heat Transfer interfaces now support the Frequency-Domain Perturbation solver,
which computes the harmonic temperature variations around an equilibrium state. The
predefined Thermal perturbation, Frequency domain solver sequence first solves a
Stationary study step to find the equilibrium state and then reuses that solution as a
starting point for the second Frequency-Domain Perturbation step.
The Frequency to Time FFT and Time to Frequency FFT study steps have been made
available to perform inverse and forward FFT between time and frequency domains.
Two new refrigerant materials have been added in the Liquid and Gases material
database: R-134A (C2H2F4) and R-22 (CHClF2). Their thermal properties are
given.
I R R EVE R S I B L E TR A N S F O R M A T I O N I N S O L I D S
The Irreversible Transformation attribute node is now available under the Solid domain
node. It should be used to model thermally-induced irreversible transformations in
solids. The Temperature threshold model evaluates the transformation from the time
spent over (for Overheating analysis) or below (for Overcooling analysis) a given
temperature. The Energy absorption model is based on Arrhenius equation.
The heat source or sink due to enthalpy change during the transformation is accounted
for in the energy balance. Finally, you can define different thermal properties for the
transformed state; in this case, the material thermal properties are dependent of the
material damage indicator.
When this attribute is active, the segregated solver attribute is set by default, and the
group containing the irreversible transformation indicator is solved by a Jacobi iterative
method.
S E RE N D I P I T Y S H A P E F U N C T I O N S F O R TE M P E R A T U R E
The temperature dependent variable in Heat Transfer and Heat Transfer in Thin
Structures interfaces, which was always of Lagrange type, can now be of serendipity
type. This is reflected in the following new choices in the Discretization section of the
physics interface node: Quadratic serendipity, Cubic serendipity, and Quartic serendipity.
For highly distorted elements, Lagrange shape functions provide better accuracy than
serendipity shape functions of the same order. The serendipity shape functions will,
however, give significant reductions of the model size for a given mesh containing
hexahedral, prism, or quadrilateral elements. At first order, Lagrange and serendipity
shape functions are the same.
The shape functions for TextFace and Txdim in the Thin Layer feature, and TWall_u
and TWall_d in the Nonisothermal Flow multiphysics coupling feature also follow the
temperature shape function type, in particular if a serendipity option is chosen.
H E A T TR A N S F E R M O D U L E | 69
SYMMETRY FOR SURFACE-TO-SURFACE RADIATION EXTENDED
CAPABILITIES
The Symmetry for Surface-to-Surface Radiation global feature has new options available
to take advantage of multiple plane symmetries for 2D and 3D models. You should use
these options to reduce the mesh size, for a more efficient computation of the view
factor. In 2D models, the Two perpendicular planes of symmetry option is available. In
3D, either the Two perpendicular planes of symmetry option (planes with intersection
parallel to one of the axis), or the Two perpendicular planes of symmetry option (planes
parallel to the axis), can be defined.
In addition, you can visualize the plane(s) of symmetry in the Graphics window along
with the geometry. This is meant to ease the user experience when defining the
plane(s), and it applies to the options Plane of symmetry (2D, 2D-axi, and 3D models),
Two perpendicular planes of symmetry (2D and 3D models), and Three perpendicular
planes of symmetry (3D models). A check box is available to show/hide the planes in
the Graphics window.
In addition, sketches and more detailed equations have been added in the user
interface for all the correlations used for the Convective heat flux option. The images
appear in a new Sketch section, collapsed by default, showing the geometry along with
the input parameters used in each correlation.
T I M E - D E P E N D E N T E N E RG Y S T O R A G E TE R M I N T H E R M A L L Y T H I C K
LAYER
The Thermally thick approximation option in the Thin Layer feature now accounts for a
time-dependent term modeling the energy storage over time. This term requires the
material density and the heat capacity at constant pressure as inputs in the new
Thermodynamics section in the feature user interface. For time-dependent models
modeling a thermally thick layer by a boundary, such an energy storage term improves
the accuracy of the temperature profile compared to modeling the thin layer by a full
geometrical domain.
In Heat Transfer in Thin Shells interfaces, the Thin Layered Shell node has two new
subfeatures: External Temperature, to define the temperature on the downside and/or
upside of a thin layered shell, and Heat Source, to add an internal heat source within
each layer of a thin layered shell.
Additionally, the ambient temperature has been added as a feature input in the
Isothermal Domain feature, when Temperature definition is set to From prescribed
temperature.
H E A T TR A N S F E R M O D U L E | 71
Finally, all the ambient data variables (ht.Is_amb, ht.Ish_amb, ht.Isn_amb,
ht.T_amb, ht.p_amb, ht.phi_amb, ht.v_amb, and ht.xvap_amb) are now available
as global variables and can be used in a Global Evaluation for postprocessing.
When the Biological Tissue node is active with the Include damage integral analysis check
box selected, the damage indicator is solved by an iterative Jacobi method by default.
These studies contain two steps (Stationary or Time Dependent), one solving for the
fluid flow interface, and one solving for the heat transfer interface.
While multiphysics stabilizations (streamline and crosswind diffusion) are available for
the fully-coupled studies, the stabilization of each solved physics is used instead when
one of the physics interfaces or the multiphysics coupling is not solved in a study step,
and the solver suggestions are uncoupled.
MISCELLANEOUS
• New predefined variables are available with the Heat Transfer in Thin Shells
interface for the control of fluxes on boundaries where this physics interface is active.
You can plot the (vectorial) variables htsh.tflux, htsh.dflux, htsh.cflux, and
htsh.teflux to control the total heat flux, conductive heat flux, convective heat
flux, and total energy flux on the boundaries. In addition, the (scalar) variables
H E A T TR A N S F E R M O D U L E | 73
New Application in Version 5.3
In addition, the size of the air domain has been increased such that further increasing
the domain would have no noticeable effect on the flow field around the beaker.
In all these applications, the Insert Sequence functionality under Geometry node has
been used to import the geometry defined in a separated MPH-file. With this process,
the geometry stay editable when imported in the application.
The new default option in Thin Moisture Barrier feature is Vapor barrier material
properties, and the Moisture barrier material properties option has been removed. When
loading a MPH file that was created before version 5.3 this latter option will be cleared,
and the corresponding user inputs used to define the Moisture transfer coefficient
directly. However, for the API, it will be necessary to update the code with an existing
option name.
In the Equivalent Conductivity for Convection section of the Fluid node, the new
Automatic option for Temperature difference has become the default option. When
loading a MPH file that was created before version 5.3, the User defined option will be
set automatically with the previous value. However, for the API, it will be necessary to
update the code to set the User Defined option.
• When Solar position is selected in External Radiation Source, the new option Update
time from solver is selected by default. When loading an MPH file that was created
H E A T TR A N S F E R M O D U L E | 75
before version 5.2a this option will be cleared. However, for the API, for
time-dependent studies, it will be necessary to update the code to get the same
behavior as in previous versions. In most cases, removing the t term in the Second
field is the best option. Alternatively, clearing the Update time from solver option will
ensure that the same behavior as before is obtained.
• The crosswind stabilization of the heat transfer and fluid flow interfaces has been
updated. In general, the update reduces the smoothing induced by the stabilization
compared to previous version. In addition, when you use the Nonisothermal Flow
multiphysics coupling and the fluid is defined as incompressible, the uncoupled
versions of the streamlines and crosswind stabilization are used.
• Since Pair Thin Film and Pair Fracture are now pair features, their selection needs to
be redefined.
• The definition of the ht.feature.fc(RH.T,pA) function when Moist air fluid type
is used in Fluid feature has been corrected. This change can affect the results in
simulations where it is used.
• The frame support has been enhanced to support moving mesh combined with
deformed geometry in the same component.
• The Prescribed Radiosity feature has been updated so that it no longer ignores the
Temperature model input.
• In surface-to-surface boundary features, the ambient temperature definition has
been fixed when the Opacity Controlled and Defined ambient temperature on each side
options are used simultaneously.
The names of the heat capacity variables have changed in several features for
consistency:
The names of the thermal resistance and absolute thermal resistance variables have
changed in the Isothermal Domain Interface feature:
The name of the fluid viscosity variable has changed in the Local Thermal
Non-Equilibrium multiphysics coupling: ltne1.mu_f has become ltne1.mu.
OBSOLETE FEATURES
A number of features are now obsolete because they have been merged or replaced by
a more general features. However, when models from COMSOL 5.0 or before contain
these features, some of the obsolete features are visible in version 5.2a with a warning
sign notifying that the feature is now obsolete (see Table 1-1). Some features have
been completely removed (see Table 1-2). A model containing any of them can be
opened in 5.2a, but the feature will be missing.
Updating the models is recommended. Use the new feature and remove the obsolete
feature to make sure that the model will remain compatible with future versions of
COMSOL Multiphysics.
Convective Heat Flux Heat Flux with the Convective heat flux option
selected
Surface-to-Ambient Radiation Diffuse Surface with Include surface-to-surface
radiation deselected
Surface-to-Surface Radiation Diffuse Surface with Include surface-to-surface
radiation selected
Highly Conductive Layer Thin Layer with Layer type set to Conductive
Thin Thermally Resistive Layer Thin Layer with Layer type set to Resistive
H E A T TR A N S F E R M O D U L E | 77
TABLE 1-2: OBSOLETE FEATURES THAT ARE NO LONGER AVAILABLE
• Heat Flux (ht.hf1.Tvar), Line Heat flux, Point Heat flux, and Out of plane heat flux.
• Heat Source (ht.hs1.Tvar), Boundary heat source, Line heat source, and Point heat
source.
• Diffuse Surface (ht.ds1.Tvar).
The fully scoped variables Ptot, Pbtot, Pltot, and Pstot become P0, Pb, Pl, and Ps,
respectively, in the following features:
• Heat Flux
• Inflow Heat Flux
• Line Heat Flux
• Heat Source
• Boundary Heat Source
• Line Heat Source
• Line Heat Source (Thin Rod subfeature)
• Line Heat Source on Axis
• Layer Heat Source (Thin Layer subfeature)
• Qfric, QfricPow, and Qrate become Qb, Pb, and Qbpart, respectively
• Qfric0, Qrate0, Econtact0, hrad0, hgap0, and hconstr0 are removed and
migrated to existing variables Qb, Qbpart, Econtact, hrad, hgap, and hconstr,
respectively, in old models.
The Change Effective Thickness feature from the Heat Transfer in Thin Shells interface
merges htsh.de into the existing variable htsh.ds.
The Heat Transfer in Thin Shells interface also merges the property de and variable
htsh.de into existing property ds and variable htsh.ds. An API command such as
model.physics("htsh").prop("de").set("de", [...]) now does not have any
effect.
O U T - O F - P L A N E H E A T TR A N S F E R U P D A T E
The out-of-plane heat transfer property, which was available in 2D and 1D geometries,
has been removed as of COMSOL Multiphysics 5.0. Now, all geometries are
considered 3D geometries and thickness or area parameters are always available.
API Users
With the Overall heat transfer rate option (previously named Total power or Total heat
flux), the thickness parameters (dz_entr and Ac_input) have been removed for the
following features:
• Heat Source
• Heat Flux
• Boundary Heat Source
• Layer Heat Source
• Inflow Heat Flux
Compatibility with previous code is maintained for most of the cases. However, three
configurations require manual updates of the code:
• If you specified the thickness parameter twice (there were two instances of specifying
the parameter).
H E A T TR A N S F E R M O D U L E | 79
• If you first specified the thickness and in a second command the total power value.
• If you first specified the thickness and then activated the out-of-plane heat transfer
option.
For these 3 cases, you need to rewrite this part of the Java® code by doing the
following. For a heat source example (2D and 1D axisymmetric geometries):
Ptot_50 = Ptot_44_value*ht.d/dz_entr_44_value,
where Ptot_44_value is the total power value used in previous versions, Ptot_50 is
the total power value used since COMSOL Multiphysics 5.0, and dz_entr_44_value
is the value used in previous versions.
Flux Variables
The flux variables are always given in W/m² (also for 2D or 1D geometries). To obtain
the corresponding flux variables in W/m on a boundary in 2D, for example, the flux
variables have to be multiplied by the thickness ht.d.
All flux variables now have the following sign convention: positive heat flux
corresponds to heating, whereas negative heat flux corresponds to cooling. The
variables chflux and rflux may have opposite signs compared to previous versions,
depending on the context where they are defined.
H E A T TR A N S F E R W I T H P H A S E C H A N G E N OW U S E S A VO L U M E T R I C
FORMULATION
The variables ht.thetai now represent volume fractions (they were mass fractions
before). This implies changes in the definition of density and heat capacity at constant
pressure close to the phase change interface. Far from the phase change interface, the
density and heat capacity are unchanged.
Among the changes, the reference enthalpy, HRef, the value of which is defined up to
a constant, is now set to 0 J/kg at the reference temperature and pressure. This
changes the absolute values of the enthalpy and several variables based on it. In
particular, the value of the convective heat flux is changed. Even the sign may be
changed in some cases. However, the quantity of interest, the net convective heat flux,
is identical because the shift induced by the change of HRef applies for the enthalpy
definition at the inlet as well as at the outlet.
H E A T TR A N S F E R I N P O RO U S M E D I A
Old models using the Porous feature will be supported in the COMSOL Multiphysics
interface. However, it is recommended to replace this feature with Heat Transfer in
Porous Media (see Obsolete Features and Variables). For a model using the API,
it will be necessary to update the model to use Heat Transfer in Porous Media.
H E A T TR A N S F E R M O D U L E | 81
SURFACE-TO-SURFACE RADIATION
The surface radiosity, previously named J, is now named ht.J by default (assuming
that ht is the physics interface tag).
Models created using versions 4.3 and 4.3a that contain surface-to-surface radiation
support the old syntax in multiphysics interfaces. It is, however, recommended that
you update the models to use the new syntax. Models created in a version before 4.2a
need to be opened in version 4.3 or 4.3a and resaved before being opened in 5.0 or a
later version.
For a model using the API, you must update the model to use the new syntax.
Models created in versions 4.3 and 4.3a that include radiation in participating media
support the old syntax in multiphysics interfaces. It is, however, recommended that
you update the models to use the new syntax. Models created in a version before 4.2a
need to be opened in version 4.3 or 4.3a and resaved before being reopened in 5.0 or
a later version. In addition, for all versions, it may be necessary to regenerate the
default solver to get the correct solver settings.
The S2 quadrature in 2D has been replaced by the LSE symmetric quadrature. It has
been updated so that it coincides with the other quadratures. LSE symmetric
quadratures were already used for S4, S6, and S8 in 2D and for all 3D quadratures.
This quadrature update can result in significant changes in 2D models using the S2
quadrature. However, the theoretical error is not different and the 2D and 3D
implementations are now consistent.
Any model files for Java® that modify the default model value require a manual update.
• Heat flux
• Out-of-plane heat flux
• Convective cooling
• Out-of-plane convective cooling
• Boundary heat source
• Heat source
• Line heat source
• Point heat source
• Edge heat flux/Point heat flux
• Electrochemical reaction heat flux
• Reaction heat flux
For example, in a Boundary Heat Source feature, ht.surf has been renamed into
ht.bhs1.surf (assuming that ht is the physics interface tag). In the Heat Flux
feature, the variable that was previously named ht.q0_hf1 is now ht.hf1.q0.
H E A T TR A N S F E R M O D U L E | 83
Any model files for Java® that use the old variable names in expressions (such as
expressions used for plotting or data evaluation that include such old variable names)
need to be updated manually.
Due to these new default features, model files for Java can be simplified. In addition,
model files for Java that add the Fluid feature or the Opaque subfeature with the default
tag require a manual update to avoid duplicate tag conflicts.
• Laminar Flow
• Turbulent Flow, k-ε
• Turbulent Flow, Low Re k-ε
• Nonisothermal Flow
• Conjugate Heat Transfer
Weak constraints for the Interior Wall feature are no longer available.
R E V I S I O N T O T H E TU R B U L E N C E M O D E L S
The formulations of some variables in the turbulence models have been revised in
order to improve accuracy. Simulations using a turbulence model can display a
different convergence behavior in versions 5.0 and later compared to version 4.3, and
the numerical result can differ slightly between the versions.
• Convective Heat Flux (replaced by Heat Flux with Convective heat flux option)
• Out-of-plane Convective Heat Flux (replaced by Out-of-plane Heat Flux with Convective
heat flux option)
• Porous Matrix (replaced by Heat Transfer in Porous Media)
When models created in older versions are loaded in version 5.3, these features are
removed from the model tree and the model can still be opened. The new
corresponding feature can be added to replace the removed one. In the particular case
of a feature defined as the default feature of an interface in the model, the model
cannot be opened.
The table below contains a list of variables that have been removed and replaced by
new corresponding expressions.
TABLE 1-3: REMOVED VARIABLES AND CORRESPONDING EXPRESSIONS
qin -qr_in
qout qr_out
qw -qr_net
ndflux_acc ndflux
ndflux_acc_u ndflux_u
ndflux_acc_d ndflux_d
ntflux_acc ntflux
ntflux_acc_u ntflux_u
ntflux_acc_d ntflux_d
nteflux_acc nteflux
nteflux_acc_u nteflux_u
nteflux_acc_d nteflux_d
H E A T TR A N S F E R M O D U L E | 85
MEMS Module
New Functionality in Version 5.3
The following new functionality is available:
• Spring boundary conditions for the Rigid Domain and Rigid Connector features.
• Energy quantity variables have been added for contact modeling.
• Frequency domain analysis with contact modeling is now supported
• Harmonic Perturbation is now available for the Prescribed Velocity and Acceleration
features.
• Enhancements have been added for including external material functionalities.
See also the Structural Mechanics Module for improvements for the structural
mechanics interfaces in the MEMS Module.
MOBILITY
In physics interfaces modeling migration (for example, Transport of Diluted Species),
anisotropic mobility is now supported, and the mobility can be set to follow the
Nernst-Einstein relation. The default setting when making new models has been
changed to the Nernst-Einstein relation. Model files for Java®-generated prior to 4.3b
using migration will have to be modified manually to account for these changes.
MICROFLUIDICS MODULE | 87
Molecular Flow Module
New Functionality in Version 5.3
A Plane Symmetry boundary condition is now available for models with geometric
symmetry.
In addition, new variables exist for the total pressure, number density, and so on:
HIGHLIGHTING OF SELECTIONS
When working with complex assemblies in the Multibody Dynamics interface, there
may be many joints, each containing the selection of two rigid domains or attachments.
When you select a Joint node in the model tree, the selected objects are now
automatically highlighted in the graphics window as a quick feedback of the
correctness of the source and destination selections. Similarly, the two gears in a Gear
Pair, and the two parts joined by a Spring-Damper will be highlighted when the
corresponding nodes are selected.
M O D A L R E D U C E D O R D E R M O D E L S T U D Y TY P E
The Modal Reduced Order Model study type is now supported also by the Multibody
Dynamics interface. This study type is useful for extracting system matrices represented
in a modal base for large MBD models.
PO RO US PLAST ICITY
A new family of material models for modeling porous plasticity has been added. The
Porous Plasticity subnode is available for Linear Elastic Material and Nonlinear Elastic
Material.
• Shima-Oyane
• Gurson
• Gurson-Tvergaard-Needleman
• Fleck-Kuhn-McMeeking
• FKM-GTN
• Chaboche
• Perzyna
A S S O C I A T E D F L OW R U L E F O R TRE S C A Y I E L D F U N C T I O N
An associated flow rule has been added to the Tresca yield function in Plasticity. As
before, the default flow rule is based on using the von Mises yield surface as plastic
potential.
In most cases, the old physics scope variables can still be accessed, so you should not
experience any backward compatibility problems, even if you have used such variables
in your own expressions.
OPTIMIZATION MODULE | 93
Particle Tracing Module
New Functionality in Version 5.3
ROTATING FRAMES
Use the Rotating Frame feature to automatically apply the centrifugal, Coriolis, and
Euler forces for particle tracing in a rotating frame of reference. When releasing
particles, it is possible to specify the initial velocity in an inertial frame or with respect
to the rotating frame.
L A M B E R T I A N VE L O C I T Y D I S T R I B U T I O N
The particle release features can now release particles with a velocity distribution in 3D
following Lambert’s cosine law.
N O N U N I F O R M M A G N I T U D E S I N VE L O C I T Y D I S T R I B U T I O N S
For the spherical, hemispherical, conical, and Lambertian velocity distributions, it is
now possible to release particles with a distribution of speeds as well as directions.
By default, every particle that is released from the same point in a velocity distribution
will have the same magnitude. However, by expressing the initial speed in terms of the
unique particle index, it is now possible to apply a different initial speed to each particle
L I F T F O RC E F O R T H E P A R T I C L E TR A C I N G F O R F L U I D F L OW I N T E R F A C E
A dedicated Lift Force feature is now available for the Particle Tracing for Fluid Flow
interface.
Two different formulations of the lift force are available. The Saffman lift force is
applicable to inertial particles in a shear flow that are an appreciable distance away from
boundaries. A specialized wall induced correlation is also available for neutrally
buoyant particles in channels.
A N I S O T RO P I C TU R B U L E N T D I S P E R S I O N
When applying a random turbulent dispersion term to the drag force on particles in a
fluid using the continuous random walk model, the turbulent dispersion can now be
either isotropic (the default) or anisotropic. If anisotropic turbulence is used, the
turbulent dispersion terms are computed using specific expressions for the streamwise,
spanwise, and wall normal directions. Anisotropic turbulence can provide a more
realistic depiction of particle motion in a turbulent flow when the particles are close to
walls.
S Y M M E T R Y C O N D I T I O N F O R P A R T I C L E TR A C I N G
The Symmetry condition is a specialized boundary condition for the Charged Particle
Tracing and Particle Tracing for Fluid Flow interfaces. It is a special case of the Wall
condition that always causes model particles to be specularly reflected at the boundary.
The physical interpretation of this reflection is that, for every particle that would leave
the modeling domain through a symmetry plane, an identical particle would
simultaneously enter the modeling domain at the same location and the same time.
P A R T I C L E TR A C I N G M O D U L E | 95
NEW OPTIONS FOR INLET PAIRS
When releasing particles from an Inlet Pair defined on an assembly, it is now possible
to release the particles from only the source boundary, destination boundary, or both.
This is most noticeable when using a mesh-based release of particles, since the mesh
on either side of the identity pair can be different.
TU R B U L E N T D I S P E R S I O N C H A N G E S
In the settings window for the Drag Force for the Particle Tracing for Fluid Flow
interface, the Turbulent dispersion check box has been replaced by the Turbulent
dispersion model list. If the check box is selected in a model created in version 5.2 or
earlier, then after opening the model in version 5.2a, the option Discrete random walk
will be selected from the list. If the check box is cleared, then None will be selected from
the list.
In the Sampling from phase space distribution list, Uniform has been renamed KV.
In the Longitudinal velocity distribution list, Uniform has been renamed None and
Gaussian has been renamed Normal.
The parameters Position refinement factor and Release distribution accuracy order have
been removed. Due to some changes in the algorithm for initializing particle positions,
in version 5.2a, the distribution of particle positions no longer depends on the finite
element mesh and may differ from the distribution in version 5.2.
P A R T I C L E TR A C I N G M O D U L E | 97
subnode will be created. If instead the Collision model was set to Friction, the Friction
Force subnode will be added.
N E W O P T I O N F O R T- J U N C T I O N F E A T U R E F O R T H E P I P E F L O W
INTERFACE
An additional option for the T-Junction feature called Loss coefficients, extended
model is available for the Pipe Flow interface. This option allows you to specify six
dimensionless loss coefficients to account for joining and separating flows in junctions.
NEW APPLICATION
Boltzmann DC Glow Discharge: This application models a DC glow discharge that
periodically solves the two-term Boltzmann equation to update the transport and
source coefficients.
NEW MODELS
• Atmospheric Pressure Corona Discharge in Air
• Negative Streamer in Nitrogen in 1D
• Chlorine Discharge Global Model
• Microwave Microplasma
R AY TE R M I N A T I O N FE A T U RE
The new Ray Termination feature can be used to annihilate rays without requiring them
to stop at a boundary. The rays can be terminated as they exit a bounding box, which
can be based on the geometry or user-defined spatial extents. Use the Ray Termination
feature to easily discard unnecessary information about the ray paths and remove
clutter from the trajectory plots.
When the photometric data file is imported into a model, it generates a set of functions
that are used to initialize the ray intensity and power as a function of the initial ray
direction. You can specify directions for the photometric horizontal and photometric
zero, which indicate the orientation of the lamp according to IES standards.
I M P ROVE D H A N D L I N G O F R AY TR A C I N G I N 2 D A X I S Y M M E T R I C
GEOMETRIES
When computing ray intensity in 2D axisymmetric models, the wavefront associated
with the propagating ray is now treated as a spherical or ellipsoidal wave instead of a
cylindrical wave (which is only an appropriate simplification in true 2D models). In
other words, the principal radius of curvature associated with the azimuthal direction
is computed for all rays. This leads to more realistic calculations of ray intensity in 2D
axisymmetric models.
In addition, dedicated release features are now available to release rays from edges,
points, or at specified coordinates along the axis of symmetry. When using one of these
dedicated release features, a built-in option is available to release rays in an anisotropic
hemisphere such that each ray subtends approximately the same solid angle in 3D.
The following variables are defined by an instance of the Ray Detector feature with the
feature tag <tag>:
• <tag>.Nsel is number of transmitted rays from the release feature to the detector.
• <tag>.alpha is the transmission probability from the release feature to the
detector.
• <tag>.rL is a logical expression for ray inclusion. This can be set in the Filter node
of the Ray Trajectories plot in order to visualize the rays that connect the radiation
source to the detector.
• Linear Polarizer
• Linear Wave Retarder
• Mueller Matrix
• Grating
The Use corrections for finite source diameter check box has been replaced by the
Corrections for finite source diameter list. If the check box was selected, Create light
cones at release points will be selected from the list after opening the model in version
5.2a. If the check box was cleared, None will be selected from the list.
For the Illuminated Surface, the Standard deviation of the angle of incidence parameter
has been renamed Surface slope error and is now used to define a Rayleigh distribution
for perturbations to the surface normal, rather than the angle of incidence of radiation.
To account for the different effect that the surface slope error has on the model, any
value or expression entered for the Standard deviation of the angle of incidence in version
5.2 or earlier will be divided by 2, before being used to specify the Surface slope error
in version 5.2a.
The Number of rays in wave vector space Nw,r has been removed. The effect of surface
roughness can no longer multiply the number of degrees of freedom created by a
release feature at each release point.
• Linear Polarizer
• Linear Wave Retarder
• Circular Wave Retarder
• Ideal Depolarizer
• Mueller Matrix
If any of these features is present in a model created in version 5.2 or earlier, and None
is selected from the Intensity computation list in the settings window for the
Geometrical Optics interface, then the feature will be automatically disabled when the
model is opened in version 5.2a. To enable these features, select any option other than
None from the Intensity Computation list.
RENAMED SETTINGS
The Wall condition Bounce has been renamed to Specular reflection.
Expressions involving the ray frequency must always be included within the noenv()
operator. Some expressions for user-defined refractive indices may fail to be evaluated
properly in version 5.2a unless this operator is applied.
Enhanced features:
• Lumped element feature with extended options: series LC, parallel LC, series RLC,
and parallel RLC.
• Two-port network for advanced two-port device modeling with Touchstone file
import.
• Transient lumped port supporting S-parameter calculation.
• Scattering boundary condition for Electromagnetic Waves, Transient can be used
now also under high loss conditions.
The GHz frequency unit is now available for Frequency Domain, Frequency-Domain
Modal, and Eigenfrequency studies. The GHz units is also now used unit in the default
S-parameter plot with simpler S-parameter descriptions.
U P D A T E D TU T O R I A L S U S I N G R E D U C E D O RD E R M O D E L I N G TE C H N I Q U E S
Using asymptotic waveform evaluation:
RF MODULE | 109
• CPW Bandpass Filter
• Waveguide Iris Filter
• Beam Splitter
• Photonic Crystal
• Scattering on Substrate
• Optical Scattering Off of a Gold Nanosphere
• Dielectric Slab Waveguide
• Fabry-Perot Cavity
VISCOUS DISSIPATION
The viscous dissipation is now computed in the Hydrodynamic Bearing interface. This
makes it possible to compute the temperature distribution in the lubricant. The
variable containing the dissipated energy is named hdb.Qvd.
• A new physics interface: Schrödinger Equation. This physics interface solves the
Schrödinger equation for general quantum mechanical problems as well as for the
electron and hole wave functions in quantum-confined semiconductors under the
assumption of the envelope function approximation.
• Better convergence for current-driven Schottky contacts.
• More options for the trap density specification.
• A user-defined impact ionization model.
N E W A P P L I C A T I O N : S U P E R L A T T I C E B A N D G A P TO O L
The superlattice band gap tool helps the design of periodic structures made of two
alternating semiconductor materials (superlattices). The tool uses the effective mass
Schrödinger equation to estimate the electron and hole ground state energy levels in a
given superlattice structure.
• Double Barrier 1D
• ISFET
• MOSCAP 1D
• Si Solar Cell 1D
S P E C I A L S T U D Y S T E P F O R B O L T P R E - TE N S I O N
When using Bolt Pre-Tension and Bolt Selection, one extra degree of freedom (DOF) is
added for each bolt. Typically, these DOFs should only be solved for once, in an initial
study step. In version 5.3, the bolt DOFs are only active when you use the new Bolt
Pre-Tension study type, while they are inactive in all other types of study steps. This
means that you do not any longer actively have to make manual changes of the status
for these DOFs in the solver sequence.
Study sequences in models created in a version prior to 5.3 are not affected. In such a
model you will also, in the settings for the Bolt Pre-Tension node, find a Solve in bolt
pre-tension study only check box through which you can control the solver behavior
for any new study sequence you may generate.
B U C K L I N G S T U D Y TY P E F O R T H E B E A M I N T E R F A C E
It is now possible to perform linearized bucking analysis also using the Beam interface.
This makes if easier to analyze critical loads for various frame structures under
compression. Also, models in which different structural mechanics interfaces are mixed
can now use this study type, since it was available with, for example, the Solid
Mechanics and Shell interfaces already in previous versions.
The default is to use the new framework. If you want to switch to the behavior in
previous versions, there is a new Additive strain decomposition check box in the settings
for the material models.
With the Solid-Shell Connection and Solid-Beam Connection couplings you can connect
domains from either the Solid Mechanics or the Multibody Dynamics interfaces.
Since a layer thickness is known, it is also possible to compute strains in the elastic layer
when this type of input is used, and such variables have been made available.
STRESS LINEARIZATION
Stress linearization is a technique where the stresses through a thin section in a solid
model are represented by a constant membrane stress and a linearly varying bending
stress. Using this type of evaluation is common when analyzing pressure vessels. It is
described in ASME Boiler & Pressure Vessel Code, Section III, Division 1, Subsection
NB. Other fields of application are for computing reinforcement in concrete
structures, and for some types of weld analysis.
The new Stress Linearization node make it possible to select edges along which a stress
linearization is to be performed. Membrane, bending and peak stresses are reported,
and stress intensities are computed for each such stress classification line.
• Inelastic strain contributions for nonlinear elastic and hyperelastic materials can now
be implemented
• Two new interfaces to the C code that takes several more quantities as input,
including deformation gradients
• Serendipity shape functions can now be used
• Small strain formulation has been added
• You can start by making a special initialization call to the user function
• You can make a cleanup call to the user function (for example closing files)
• The state variables can be named individually
• The time is available as an input argument
H A R M O N I C PE R T U R B A T I O N F O R P RE S C R I B E D VE L O C I T Y A N D
ACCELERATION
In the Shell, Plate, and Beam interfaces, you can provide values for harmonic
perturbation for the Prescribed Velocity and Prescribed Acceleration nodes.
When using the same functionality in the Shell interface, it is now possible to
automatically remove superfluous constraints when parts of the shell is located on the
axis of rotation.
TR A N S I E N T R O L L I N G C O N T A C T
This conceptual example shows how to handle a transient contact problem with
stick-slip friction transition. A soft hollow pipe subjected to gravity load is released at
the top of a halfpipe. The motion varies between sliding and rolling, depending on its
position in the halfpipe and its velocity. The cross section of the pipe is also ovalized
due to the contact and inertial forces. An energy balance validates the accuracy of the
solution.
N E W TR A N S P O R T O F D I L U T E D S P E C I E S I N F R A C T U R E S I N T E R F A C E
The new Transport in Diluted Species in Fractures interface is used to model mass
transport along thin fractures occurring in solid or porous media. The interface is
defined and solved on boundaries in the model geometry, assuming that the fracture
thickness is very small compared to its other dimensions.
N E W F R A C T U R E N O D E I N T H E TR A N S P O R T O F D I L U T E D S P E C I E S I N
POROUS MEDIA INTERFACE
N E W I N T E R N A L WA L L N O D E I N T H E D A R C Y ’S L A W, R I C H A R D S
E Q U A T I O N S A N D TW O - P H A S E D A R C Y ’S L A W I N T E R F A C E S
The Darcy’s law, Richards Equations, and Two-Phase Darcy’s Law interfaces can now
define thin interior walls. This is useful to avoid meshing thin impermeable structures
embedded in porous media, such as retaining walls, plates, and slabs.
N EW T H I N B A R R I E R N O D E I N T H E D A RC Y ’S L AW A N D R I C H A RD S
EQUATIONS INTERFACES
The Darcy’s Law and Richards Equations interfaces can now define permeable walls
on interior boundaries. These internal boundaries are typically used to represent thin
low permeability structures. The new Thin Barrier feature allows to avoid meshing thin
structures like geotextiles or perforated plates.
N E W W E L L N O D E I N T H E D A R C Y ’S L A W, R I C H A R D S E Q U A T I O N S A N D
TW O - P H A S E D A R C Y ’S L A W I N T E R F A C E S
The Darcy’s law, Richards Equations, and Two-Phase Darcy’s Law interfaces include
the possibility to model wells. The new Well node makes it possible to select edges in
3D or points in 2D where either Injection wells or Production wells are active.
A Q U I F E R WA T E R TA BL E M O D E L
This tutorial model demonstrates the application of COMSOL Multiphysics to a
benchmark case of steady-state subsurface flow and transient solute transport along a
vertical cross section in an unconfined aquifer. The solute transport is subjected to
highly irregular flow conditions with strong anisotropic dispersion.
NEW FEATURE
A Surface Magnetic Current Density boundary condition node is now available.
UPDATED FEATURE
The Scattering Boundary Condition node for Electromagnetic Waves, Transient can now
be used also under high loss conditions.
• The eigenfrequency search method around shift is now set as Larger real part.
• The linper operator is applied internally in an excited port or lumped port feature.
R E N A M E D TU T O R I A L M O D E L
The Defining a Mapped Dielectric Distribution of a Metamaterial Lens model has been
renamed as Defining a Mapped Dielectric Distribution of a Material.
N EW D E F A U L T VA L U E F O R G A U S S I A N B E A M B A C K G RO U N D F I E L D S P O T
RADIUS
The Gaussian beam background field is based on the paraxial approximate solution to
Helmholtz’ equation. Since this approximation is less accurate for small spot radii, the
default value for the spot radius has been changed from one wavelength to ten
wavelengths.
WAVE O P T I C S M O D U L E | 123
Material Library
New and Updated Material Data in Version 5.3
Data has been added for the following materials: C36000, P92, VM12-SHC (ASME
Code Case 2781), IN-939 SSC, C26000, 17-4 PH, Copper, A182 Grade F1 (Ravne
No. 760), A537 (S185), Silicon, BS 460B steel reinforcing bars, BS B500B steel
reinforcing bars, 1040 steel, SMn443, JIS G 4801 SUP12, 52100, 6150, G4802
SK5-CSP, ASTM A723, PMMA, BK7 glass, GaS, 28CrMoV5-8, 5132, 9310, Ferrium
C61 (AMS 6517), Ferrium S53, Inconel 803, Inconel 864, 201, 9310, Ferrium C64,
Ferrium M54, AerMet 100, 304LN, 718, Al2TiO5, NaBr, Sulfur, Alloy D9, A319,
MAR-M247, GRCop-84, Dupont Delrin resins, Dupont Crastin, Hytrel, Minlon,
Rynite, Zenite, Zytel resins, Elf Atochem KYNAR resins, Petra 140 BK-112, Lexan
101, Celacex 1600A, Pro-fax 6823, ULTEM PEI resin, 1070, TRIP 800, P91, ASME
P23, T23 steels, ductile iron 80-55-06 (NE-GJS-600), 2101 duplex stainless, 2024 Al,
and for the following Cr steels: 1.4037 (X65Cr13), 1.4122 (X39CrMo17-1), 1.4742
(X10CrAlSi18), 1.4910 (X3CrNiMoBN17-13-3), 1.3964
(X2CrNiMnMoNNb21-16-5-3), and 430F.
For steels 2304, 2507, S32304, and S32750, an additional reference was added for the
elastic modulus resulting in the values changing by 0 to 5%. For M2 steel an additional
reference was added for the expansion resulting in the values changing by 0 to 2%.
The following sections list new and improved functionality in LiveLink™ for
®
MATLAB .
A C C E S S T O F U N C T I O N S F R O M T H E A P P S TA B O F T H E TO O L S T R I P I N
MATLA B ®
By installing the LiveLink for MATLAB.mltbx file you gain access to four functions
from the Apps tab of the toolstrip in MATLAB®. These functions are:
mphmodellibrary, mphnavigator, mphopen, and mphsearch. This makes it easy to
perform common tasks such as loading and searching for models, navigating the model
object structure, and viewing the model settings.
MPHRAY FUNCTION
The new mphray function has been added to support ray optics and ray acoustics data
sets.
MPHPARTICLE FUNCTION
The mphparticle function now supports the properties 'solnum', 'outersolnum',
'times' and 'velocities'. These new options give improved access to particle data
from parametric sweep studies.
MPHPLOT FUNCTION
Support is added for the following plot types: Height Aberration Plots, Arrow Surface
Plots (normal and tangent angles), Streamline Surface Plots, and Line Plots with two
y-axes.
L I V E L I N K ™ F O R M AT L A B ® | 125
mphplot(model, 'pg1', 'view', 'view1')
mphgeom(model, 'geom1', 'view', 'view1')
mphmesh(model, 'mesh1', 'view', 'view1')
MPHTHUMBNAIL FUNCTION
The new mphthumbnail function enables the setting and getting of the thumbnail
images of models. Note that model thumbnails are now preserved by default when
loading and saving models. In previous versions, these were silently removed.
• Buttons for loading and saving COMSOL Multiphysics models and handling server
connections have been moved from the COMSOL ribbon tab to the File tab in Excel®.
This leaves more space on the COMSOL tab for functionality for working with the
COMSOL Multiphysics models in the Excel workbook.
• To enable easier access to the product documentation, all windows and dialog boxes
now have a Help button to open context-sensitive help.
• Two new buttons have been added to the Numerical Results section of the COMSOL
ribbon tab. The Result Parameters button provides access to parameters defined in
the Parameters node in the Results section of the Model Tree. When clicked, the
Clear and Evaluate All button first clears all table entries and then evaluates all derived
values.
model.geom("geom1")
model.component("comp1").geom("geom1")
to indicate which component the geometry belongs to. To keep the old syntax in
generated Model Java® files, clear the Use component syntax check box under Code
generation on the Methods page in the Preferences window. All old scripts and Java®
source code files will continue to work using the old syntax.
model.physics("mf").feature().create("mtcd1",
"MultiTurnCoilDomain", 3);
model.physics("acpr").feature("pwr1").feature("ipf1").
set("c", "acpr.c_c");
model.physics("cpf").feature("cpf1").set("gamma_mat", "userdef");
New syntax (includes the species name in the first argument of the set method):
model.physics("tcdee").feature("ice1").set("D_c1", new
String[]{"D1", "0", "0", "0", "D1", "0", "0", "0", "D1"});
model.physics("tcdee").feature("ice1").set("D_c2", new
String[]{"D2", "0", "0", "0", "D2", "0", "0", "0", "D2"});
model.physics("tcdee").feature("ice1").set("D_c3", new
String[]{"D3", "0", "0", "0", "D3", "0", "0", "0", "D3"});
• Accessing tensor components (in the definitions of other variables, for example).
Old syntax:
Dxx_c1, Dxy_c1, Dxz_c1...
New syntax (includes the species name in the first argument of the set method):
model.physics("tcdee").feature("reac1").set("R_c1", new
String[]{"R1"});
model.physics("tcdee").feature("reac1").set("R_c2", new
String[]{"R2"});
model.physics("tcdee").feature("reac1").set("R_c3", new
String[]{"R3"});
New syntax:
model.physics("tcdee").feature("init1").setIndex("initc", "c20",
1);
model.physics("tcdee").feature("init1").setIndex("initc", "c30",
2);
model.physics("tcdee").feature("init1").setIndex("initphil",
"V0");
• Selecting properties.
Old syntax:
model.physics("tcdee").prop("Convection").set("Convection", 1,
"0");
model.physics("tcdee").prop("ConvectiveTerm").setIndex("Convectiv
eTerm", "noncons", 0);
New syntax (the property name corresponds to the section in the user interface):
model.physics("tcdee").prop("TransportMechanism").set("Convection
", 1, "0");
model.physics("tcdee").prop("AdvancedSettings").setIndex("Convect
iveTerm", "noncons", 0);
For information about API backward compatibility for the Surface Reactions interface,
see the Chemical Reaction Engineering Module release notes.
®
LIVELINK™ FOR SOLID EDGE CHANGES
The default value for the keepfree property of the LiveLinkSolidEdge function is
now set to on. Previously, the default was set to off.
DOCUMENTATION
The COMSOL Multiphysics Programming Reference Manual replaces the
COMSOL API for Use with Java® Reference Manual.
DEPRECATED METHODS
The following methods were deprecated in COMSOL 5.0:
TABLE 1-4: DEPRECATED METHODS AND THEIR REPLACEMENTS
com.comsol.model.OptFeature.field() OptFeature.comp()
com.comsol.model.OptFeature.field(String) OptFeature.comp(String)
com.comsol.model.Group.identifier() Group.paramName()
com.comsol.model.Material.identifier() ModelEntity.tag()
com.comsol.model.MaterialModel. ModelEntity.tag()
identifier()
com.comsol.model.ModelNode.identifier() ModelEntity.tag()
com.comsol.model.physics.Physics. Use tag() instead.
identifier()
com.comsol.model.physics. ModelEntity.tag()
MultiphysicsCoupling.identifier()
com.comsol.model.Group.identifier(String) Group.paramName(String)
com.comsol.model.Material. ModelEntity.tag(String)
identifier(String)
com.comsol.model.MaterialModel. ModelEntity.tag(String)
identifier(String)
com.comsol.model.ModelNode. ModelEntity.tag(String)
identifier(String)
com.comsol.model.physics.Physics. Use tag(string) instead.
identifier(String)
com.comsol.model.physics. ModelEntity.tag(String)
MultiphysicsCoupling.identifier(String)
com.comsol.model.ModelEntity.name() ModelEntity.label()
com.comsol.model.ModelEntity.name(String) ModelEntity.
label(String)
com.comsol.model.ParameterEntity. Use the 0-based version
set(String, int, double) (setIndex) instead.
com.comsol.model.ParameterEntity. Use the 0-based version
set(String, int, double) (setIndex) instead.
com.comsol.model.ParameterEntity. Use the 0-based version
set(String, int, double[]) (setIndex) instead.
com.comsol.model.ParameterEntity. Use the 0-based version
set(String, int, int) (setIndex) instead.
com.comsol.model.ParameterEntity. Use the 0-based version
set(String, int, int[]) (setIndex) instead.
com.comsol.model.ParameterEntity. Use the 0-based version
set(String, int, int, double) (setIndex) instead.
com.comsol.model.ParameterEntity. Use the 0-based version
set(String, int, int, int) (setIndex) instead.
com.comsol.model.ParameterEntity. Use the 0-based version
set(String, int, int, String) (setIndex) instead.
com.comsol.model.ParameterEntity. Use the 0-based version
set(String, int, String) (setIndex) instead.
com.comsol.model.ParameterEntity. Use the 0-based version
set(String, int, String[] (setIndex) instead.
PHYSICS INTERFACES
• The default Initial Value features in the following interfaces have been extended:
- Transport of Concentrated Species
- Reacting Flow in Porous Media (rfcs)
- Reacting Flow
- Rotating Machinery, Reacting Flow
Previously, only the initial mass fractions could be specified. Now, the initial values
can be specified in terms of mass fractions, mole fractions, molar concentrations,
number densities, or densities. When opening an old Model MPH file, Mixture
specification is set to Mass fractions, and the mass fractions specified are entered in
to
model.physics("chcs").feature("init1").set("w0", 2, "0.1");
• The Pressure Acoustics, Frequency Domain interface and the Boundary Mode
Acoustics interface have a new default feature. If the default feature has been edited
in a Java® file, the following line should be added to the Java® file to obtain the old
behavior for Pressure Acoustics, Frequency Domain:
model.physics("acpr").feature().create("pam1",
"PressureAcousticsModel").selection().all();
or
model.physics("acbm").feature().create("pam1",
"PressureAcousticsModel").selection().all();
PHYSICS INTERFACES
• The Crosswind diffusion formulation has been updated for all physics interfaces
supporting Crosswind diffusion. Models solved with the new formulation can give
different results than models solved in versions earlier than 4.3b. Java® files can be
modified to retain old crosswind formulations. Please contact COMSOL Support
for details.
• The default settings have changed for the Background Pressure Field in the Pressure
Acoustics interfaces. Add the following line to obtain the old behavior of this
feature:
model.physics("acpr").feature("bpf1").set("c", 1, "acpr.c_c");
• In the Darcy’s Law interface and the Richards’ Equation interface in the Subsurface
Flow Module, fluid compressibility is now a material parameter and no longer has a
default value. If the default value was used, you now have to set the value. The
following example sets the permeability to the old default value:
model.physics("dl").feature("smm1").set(chif_mat,userdef);
model.physics("dl").feature("smm1").set(kappa,4e-10);
• The Level Set and Phase Field interfaces now include the Initial Interface feature by
default. If you have a model that was created in an earlier version of COMSOL
Multiphysics, it will fail to create a feature with the same tag name.
• In version 4.0a, the property nonlin in the stationary solver could have the values
auto, on, off, and linearized. The default in most cases was auto, but in some
cases, specifically in a frequency-domain study, the default was linearized. In
version 4.1, the possible values are auto, on, off, and linper, with auto as default,
except in the Frequency Domain, Linearized study step where the default is linper.
The value linearized can still be set, but this is treated as auto. If the problem is
linear and the linearization point is zero, auto should give the same solution as
• The pressure variable in solid mechanics, typically solid.pw, now only gets
allocated degrees of freedom for incompressible materials. If you have referred to it,
for example, during segregation in the solver, the code will have to be changed to
remove the field.
• The solution to eigenvalue and eigenfrequency problems may now appear in a
different order.
• The Batteries & Fuel Cells Module’s boundary feature,
BoundaryReactionCoefficient, is tagged by rc instead of brc by default. This
means that files that explicitly refer to the old default tag name must be modified to
refer to the new tag name.
• The units of the load face parameter (Fph) of the Phase feature in
AcousticStructure, TransientAcousticStructure,
ThermallyInducedStresses, SolidMechanics,
JouleHeatingThermalExpansion, Poroelasticity, and
FluidStructureInteraction have changed from degrees to radians.
• The physics.field() operator for Beam and Truss are not backward compatible
with 4.0. Scalar fields are now vector fields.
• The variables for strain and stress in the Shell interface have been renamed. Variable
names that began with a lowercase s now begin with an uppercase S. For variables
This concludes the release notes for COMSOL Multiphysics version 5.3.
ty in 13 new functionality in 40
INDEX| 141
new functionality in 88 new functionality in 112
Molecular Flow Module Structural Mechanics Module
backward compatibility 88 backward compatibility 118
Multibody Dynamics Module new functionality in 113
new applications in 90 new models in 118
new functionality in 89 studies and solvers, new functionality in
18
N Nonlinear Structural Materials Module
Subsurface Flow Module
new applications in 92
new functionality in 120
new functionality in 91
new model in 121
O operators, functions, and definitions,
W Wave Optics Module
new and updated 18
backward compatibility 123
Optimization Module
new functionality in 122
new functionality in 93
S Semiconductor Module
new applications in 112
142 | I N D E X