Backward Compatibility with Version 4.4

COMSOL Server

COMSOL Server from version 4.4 is now called the COMSOL Multiphysics Server.

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.

For MPH-files created in earlier versions, selections are automatically updated with the new entity numbers.

Local Coordinate Values

For model components created in version 5.0 and onward, the variable names xi1, xi2, and xi3 are reserved for the predefined local coordinate variables. To access the previous behavior (that local coordinate variables do not exist), you can use the API method model.modelNode(<tag>).defineLocalCoord(false).

Transport of Diluted Species

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().create("chds", "DilutedSpecies", "geom1",

                       new String[][]{{"c"}});

Add the following line to specify the identifier accordingly:

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.