Modelica.UsersGuide.ReleaseNotes

This section summarizes the changes that have been performed on the Modelica standard library. Furthermore, it is explained in Modelica.UsersGuide.ReleaseNotes.VersionManagement how the versions are managed with the subversion management systems. This is especially important for maintenance (bug-fix) releases where the main version number is not changed.

Extends from Modelica.Icons.ReleaseNotes (Icon for release notes in documentation).

Package Content

Name	Description
VersionManagement	Version Management
Version_3_2_BugFixes	Version 3.2 with bug fixes
Version_3_2	Version 3.2 (Oct. 25, 2010)
Version_3_1	Version 3.1 (August 14, 2009)
Version_3_0_1	Version 3.0.1 (Jan.27, 2009)
Version_3_0	Version 3.0 (Feb., 2008)
Version_2_2_2	Version 2.2.2 (Aug. 31, 2007)
Version_2_2_1	Version 2.2.1 (March 24, 2006)
Version_2_2	Version 2.2 (April 6, 2005)
Version_2_1	Version 2.1 (Nov. 11, 2004)
Version_1_6	Version 1.6 (June 21, 2004)
Version_1_5	Version 1.5 (Dec. 16, 2002)
Version_1_4	Version 1.4 (June 28, 2001)

Modelica.UsersGuide.ReleaseNotes.VersionManagement

Maintenance of the Modelica Standard Library is performed with three branches on the subversion server of the Modelica Association (https://svn.modelica.org/projects/Modelica):

Released branch

Example: "/tags/v3.0.1/Modelica"

This branch contains the released Modelica versions (e.g., version 3.0.1), where all available test cases and compatibility checks with other Modelica libraries have been performed on the respective release. This version is usually shipped with a Modelica modeling and simulation environment and utilized by a Modelica user.

Development branch

Example: "/trunk/Modelica"

This branch contains the actual development version, i.e., all bug fixes and new features based on the last Modelica release. New features should have been tested before including them. However, the exhaustive tests for a new version are (usually) not performed. This version is usually only be used by the developers of the Modelica Standard Library and is not utilized by Modelica users.

Maintenance branch

Example: "/branches/maintenance/3.0.1/Modelica"

This branch contains the released Modelica version (e.g., version 3.0.1) where all bug fixes since this release date are included (up to a new release, when becoming available; i.e., after a new release, the previous maintenance versions are no longer changed). These bug fixes might be not yet tested with all test cases or with other Modelica libraries. The goal is that a vendor may take this version at any time for a new release of its software, in order to incorporate the latest bug fixes, without changing the version number of the Modelica Standard Library.

Incorporation of bug fixes (subversion "commit") shall be performed in the following way:

• One person is fixing the bug and another person is checking whether the fix is fine.
• It is up to the library developer, whether he opens a new branch for testing and then merges it with the "head" maintenance branch or not.
• Every change to the maintenance branch has to be done at the development branch (see above) as well. One exception are pure changes to the "versionBuild" annotation as these have no meaning in the development trunk.
• Every change to the maintenance branch requires introducing a description of the bug fix under Modelica.UsersGuide.ReleaseNotes.Version_<release-number>_BugFixes.
• Annotations "version" and "versionDate" must not be changed in a maintenance release.
• Every change to the maintenance branch requires changing the "versionBuild" number (incrementing it by one), as well as the "dateModified" field.
  Example:

    annotation(version      = "3.1",
               versionDate  = "2009-06-22",
               versionBuild = 3,
               dateModified = "2009-08-28 07:40:19Z",
               revisionId   = "$I​d::                                       $")

  The "revisionId" field is a bit special though. If written like in the example above it will be automatically expanded to:

               revisionId   = "$I​d:: package.mo 2879 2009-08-28 07:40:19Z #$"

  by the subversion checkout procedure.
• If time does not permit, a vendor makes the bug fix in its local version and then has to include it in the maintenance version. It would be best to make these changes at a new branch in order to get a unique release number.

A valid "commit" to the maintenance branch may contain one or more of the following changes.

• Correcting an equation.
• Correcting attributes quantity/unit/defaultUnit in a declaration.
• Improving/fixing the documentation.
• Introducing a new name in the public section of a class (model, package, ...) or in any section of a partial class is not allowed. Since otherwise, a user might use this new name and when storing its model and loading it with an older build-version, an error would occur.
• Introducing a new name in the protected section of a non-partial class should only be done if absolutely necessary to fix a bug. The problem is that this might be non-backward compatible, because a user might already extend from this class and already using the same name.

Extends from Modelica.Icons.ReleaseNotes (Icon for release notes in documentation).

Modelica.UsersGuide.ReleaseNotes.Version_3_2_BugFixes

Below the bug fixes are summarized that have been incorporated into the maintenance branch of Version 3.2. All these changes are backwards compatible.

The following uncritical errors have been fixed (i.e., errors that do not lead to wrong simulation results, but, e.g., units are wrong or errors in documentation):

Extends from Modelica.Icons.ReleaseNotes (Icon for release notes in documentation).

Modelica.UsersGuide.ReleaseNotes.Version_3_2

Version 3.2 is backward compatible to version 3.1, i.e., models developed with versions 3.0, 3.0.1, or 3.1 will work without any changes also with version 3.2. This version is a major improvement:

• 357 models and blocks and 295 functions are newly included.
• 7 new libraries are included.
• The icons of the library are newly designed to provide a modern, unified view, see Modelica.Icons.
• All non-Modelica files, such as images, pdf-files, C-source files, scripts are moved to the new directory "Modelica\Resources". Furthermore, all file references are changed to URIs as introduced in Modelica 3.1 (e.g., a file with the file name "Modelica/Resources/Images/xxx" is referenced as "modelica://Modelica/Resources/Images/xxx").
• All physical models that dissipate heat (such as electrical elements, electrical machines, bearings, dampers, etc.), have now an optional heat port to which the dissipated energy is flowing, if activated. This will significantly improve design studies about the thermal efficiency of technical systems.
• All electrical machines in the Machines library have now a "Losses" tab in the parameter menu to optionally model machines losses such as frictional losses, stator core losses or stray load losses, respectively.
• All electrical machines in the Machines library have now a "powerBalance" result record, summarizing converted power and losses.

Version 3.2 is slightly based on the Modelica Specification 3.2. It uses the following new language elements (compared to Modelica Specification 3.1):

• Operator records and overloaded operators.
• Functions as input arguments to functions.
• Improved expandable connectors (variables declared in expandable connectors are ignored if not referenced).

A large part of the new classes have been developed with partial financial support by BMBF (BMBF Förderkennzeichen: 01IS07022F) within the ITEA2 project EUROSYSLIB. We highly appreciate this funding.

The following new libraries have been added:

The following new components have been added to existing libraries:

The following existing components have been improved in a backward compatible way:

The following critical errors have been fixed (i.e., errors that can lead to wrong simulation results):

The following uncritical errors have been fixed (i.e., errors that do not lead to wrong simulation results, but, e.g., units are wrong or errors in documentation):

The following trac tickets have been fixed:

Note:

• Libraries Modelica_FundamentalWave and Modelica_QuasiStationary are included in this version in an improved form.
• From library Modelica_LinearSystems2, the sublibraries Math.Complex, Math.Vectors and Math.Matrices are included in this version in an improved form.
• From library Modelica_StateGraph2, the sublibrary Blocks is included in this version in an improved form.

Extends from Modelica.Icons.ReleaseNotes (Icon for release notes in documentation).

Modelica.UsersGuide.ReleaseNotes.Version_3_1

Version 3.1 is backward compatible to version 3.0 and 3.0.1, i.e., models developed with version 3.0 or 3.0.1 will work without any changes also with version 3.1.

Version 3.1 is slightly based on the Modelica Specification 3.1. It uses the following new language elements (compared to Modelica Specification 3.0):

• Prefix stream and built-in operators inStream(..) and actualStream(..) in Modelica.Fluid.
• Annotation connectorSizing in Modelica.Fluid.
• Annotation inverse in Modelica.Media.
• Annotations versionBuild, dateModified, revisionId at the root level annotation of package Modelica, to improve the version handling.
• Modifiers can be used in connectors instances (so balanced models are less restrictive). This allowed to make the implementation of conditional connectors (support and heatPort) in the Rotational, Translational and Electrical libraries simpler.

The following new libraries have been added:

The following new components have been added to existing libraries:

The following existing components have been improved in a backward compatible way:

The following uncritical errors have been fixed (i.e., errors that do not lead to wrong simulation results, but, e.g., units are wrong or errors in documentation):

Extends from Modelica.Icons.ReleaseNotes (Icon for release notes in documentation).

Modelica.UsersGuide.ReleaseNotes.Version_3_0_1

This Modelica package is provided under the Modelica License 2 and no longer under Modelica License 1.1. There are the following reasons why the Modelica Association changes from Modelica License 1.1 to this new license text (note, the text below is not a legal interpretation of the Modelica License 2. In case of a conflict, the language of the license shall prevail):

1. The rights of licensor and licensee are much more clearly defined. For example:
   • The licensed work (Original Work) can be used in unmodified form in open source and commercial software (the licensee cannot change the license and the work must be provided without fees)
   • If a model component is copied out of a Modelica package under Modelica License 2 and is modified in order to adapt it to the needs of the modeler, then the result can be licensed under any license (including a commercial license).
   • It is practically not possible to change the license of a Modelica package under Modelica License 2 to another license, i.e., a licensee cannot change the license by adding material or changing classes, so the work must remain under Modelica License 2 (to be more precise, if the licensee makes modifications to the Original Work "which represents, as a whole, an original work of authorship", he/she can change the license to another license. However, for a Modelica package this would require a lot of changes which is usually unrealistic).
   • If an executable is constructed using a Modelica package under Modelica License 2, then this executable can be licensed under any license (including a commercial license).
   We hope that this compromise between open source contributors, commercial Modelica environments and Modelica users will motivate even more people to provide their Modelica packages freely under the Modelica License 2.
   
   
2. There are several new provisions that shall make law suites against licensors and licensees more unlikely (so the small risk is further reduced).

The following new components have been added to existing libraries:

The following existing components have been changed (in a backward compatible way):

The following critical errors have been fixed (i.e., errors that can lead to wrong simulation results):

The following uncritical errors have been fixed (i.e., errors that do not lead to wrong simulation results, but, e.g., units are wrong or errors in documentation):

Extends from Modelica.Icons.ReleaseNotes (Icon for release notes in documentation).

Modelica.UsersGuide.ReleaseNotes.Version_3_0

Version 3.0 is not backward compatible to previous versions. A conversion script is provided to transform models and libraries of previous versions to the new version. Therefore, conversion should be automatic.

The following changes are present for the whole library:

• In the Modelican language version 3.0, several restrictions have been introduced to allow better checking, e.g., models on all levels must be balanced (number of equations = number of unknown variables - unknown variables that have to be defined when using the component). A few models of the Modelica Standard Library did not fulfill these new restrictions and had either to be moved to library ObsoleteModelica3 (e.g., Blocks.Math.TwoInputs) or had to be differently implemented (e.g., Media.Interfaces.PartialMedium.BaseProperties). The Modelica Standard Library version 3.0 fulfills all the restrictions of the Modelica Language version 3.0.
   
• The graphical annotations describing the layout of icon and diagram layer are changed from Modelica language version 1 to Modelica language version 3. This gives several significant improvements:
  Especially, the coordinate systems of icon and diagram layers are no longer coupled and therefore the size of the icon layer can be changed independently of the size of the diagram layer. Also it can be defined that the aspect ratio of a component icon is kept when changing its size in a model. This flag is set so that all icons of the Modelica Standard Library keep its aspect ratios. This is slightly non-backward compatible: If the aspect ratio was not kept when using a component from the Modelica Standard Library, it is now resized so that the aspect ratio is maintained.
   
• All non-standard annotations removed by:
  (1) Removing the annotation since without effect (e.g., "__Dymola_experimentSetupOutput", "Window", "Terminal" removed).
  (2) Renaming the annotation to a standard name (e.g., "Hide" renamed to "HideResult").
  (3) Renaming the annotation to a vendor specific name (e.g., "checkBox" renamed to "__Dymola_checkBox").
   
• All emulated enumerations (defined via packages and constants) have been replaced by "real" enumerations. User models are automatically correctly converted, provided the user models used the package constants previously. Existing models that use directly literal values for enumerations, might give in some cases wrong results (if the first constant of the emulated enumeration had value zero, whereas the first value of an enumeration is one).
   
• The operator "cardinality" will be removed in one of the next versions of the Modelica language, since it is a reflective operator and its usage significantly reduces the possibilities of advanced model checks (e.g., to guarantee that a model is "balanced", i.e., the number of equations and unknowns is identical, for all valid usages of the component). As a preparation for this change, all models that contain the "cardinality(..)" operator are rewritten: If possible the operator is removed. If this is not possible, it is only used in asserts to check that, e.g., a connector is connected at least once or is connected exactly once. In the next Modelica language version new language elements will be introduced to specifiy such a property check without the cardinality operator. Once these language elements are available, the cardinality operator will be removed completely from the Modelica Standard Library.
  The changes with respect to the cardinality(..) operator are usually not backward compatible. This is the reason for the changes of the Rotational and Translational library (see below).
   
• The design of the Rotational and Translational libraries have been changed (especially to remove the cardinality(..) operator, see above):
  • Components have a useSupport flag to enable or disable a support flange. If the support flange is enabled, it must be connected. If it is disabled, it must not be connected and the component is then internally grounded. The grounding is visualized in the icon.
  • The relative angle/distance and the relative speed of all force/torque elements (that need the relative speed) are by default defined with "StateSelect.prefer", i.e., to use these variables as preferred states. This improves the numerics if the absolute angle or the absolute distance are continuously increasing during operation (e.g., driving shaft of the wheels of a car). The effect is that relative angles/distances and speeds are used as states and the size of these variables is limited. Previously, the default was to use the absolute angle/distance and absolute speed of every inertia/mass which has the disadvantage that the absolute angle and or distance are state variables that grow in size continuously.
    A significant advantage is also, that default initialization is usually better, because a default value of zero for a relative angle/distance is usually what the user would like to have. Previously, say, the load was initialized to a non-zero angle and then the elastically coupled motor inertia had to be explicitly also initialized with this value. This is now, no longer needed. Since the default nominal value of 1 is usually too large for a relative quantity, the nominal values of the relative angle/distance was changed to 1e-4.
  • The two libraries have been restructured in sublibraries to cope with the growing number of components.
  • Finally, the Translational library has been made as similar as possible to the Rotational library by, e.g., adding missing components.
     
• The initialization of the MultiBody, Rotational and Translational libraries have been signficantly simplified by removing the "initType" parameters and only using start/fixed values. This design assumes that a tool has special support for start/fixed values in the parameter menu.
   
• Nearly all parameters defined in the Modelica Standard Library had been defined with a default equation, e.g.,

     parameter Modelica.SIunits.Resistance R=1; 

  Physical parameters, such as a resistance, mass, gear ratio, do not have a meaningful default and in nearly all cases, the user of the corresponding component has to provide values for such parameters. If the user forgets this, a tool cannot provide diagnostics, since a default value is present in the library (such as 1 Ohm for the resistance). In most cases the model will simulate but will give wrong results due to wrong parameter values. To improve this situation, all physical parameter declarations in the Modelica Standard Library have been changed, so that the previous default becomes a start value. For example, the above declaration is changed to:

     parameter Modelica.SIunits.Resistance R(start=1);  

  This is a backward compatible change and completely equivalent from the perspective of the Modelica language. It is, however, advised that tools will print a warning or optionally an error message, if the start value of a parameter is defined, but no value for the parameter is given via a modification. Furthermore, it is expected, that the input field of a parameter menu is empty, if no default equation is defined, but only a start value. This shows clearly to the modeler that a value has to be provided.

The following new components have been added to existing libraries (note, the names in paranthesis are the new sublibrary names that are introduced in version 3.0):

The following existing components have been changed in a non-backward compatible way (the conversion script transforms models and libraries of previous versions to the new version. Therefore, conversion should be automatic):

The following existing components have been improved in a backward compatible way:

The following critical errors have been fixed (i.e., errors that can lead to wrong simulation results):

The following uncritical errors have been fixed (i.e., errors that do not lead to wrong simulation results, but, e.g., units are wrong or errors in documentation):

Extends from Modelica.Icons.ReleaseNotes (Icon for release notes in documentation).

Modelica.UsersGuide.ReleaseNotes.Version_2_2_2

Version 2.2.2 is backward compatible to version 2.2.1 and 2.2 with the following exceptions:

• Removal of package Modelica.Media.Interfaces.PartialTwoPhaseMediumWithCache (this was not yet utilized).
• Removal of the media packages in Modelica.Media.IdealGases.SingleGases that are not type compatible to Modelica.Media.Interfaces.PartialMedium, because a FluidConstants record definition is missing, for details, see Modelica.Media.IdealGases (this is seen as a bug fix).

An overview of the differences between version 2.2.2 and the previous version 2.2.1 is given below. The exact differences (but without differences in the documentation) are available in Differences-Modelica-221-222.html. This comparison file was generated automatically with Dymolas ModelManagement.compare function.

In this version, no new libraries have been added. The documentation of the whole library was improved. Especially, the documentation is now also available as one pdf file.

The following new components have been added to existing libraries:

The following existing components have been improved:

The following critical errors have been fixed (i.e., errors that can lead to wrong simulation results):

The following uncritical errors have been fixed (i.e., errors that do not lead to wrong simulation results, but, e.g., units are wrong or errors in documentation):

Extends from Modelica.Icons.ReleaseNotes (Icon for release notes in documentation).

Modelica.UsersGuide.ReleaseNotes.Version_2_2_1

Version 2.2.1 is backward compatible to version 2.2.

In this version, no new libraries have been added. The following major improvements have been made:

• The Documentation of the Modelica standard library was considerably improved:
  In Dymola 6, the new feature was introduced to automatically add tables for class content and component interface definitions (parameters and connectors) to the info layer. For this reason, the corresponding (partial) tables previously present in the Modelica Standard Library have been removed. The new feature of Dymola 6 has the significant advantage that all tables are now guaranteed to be up-to-date.
  Additionally, the documentation has been improved by adding appropriate description texts to parameters, connector instances, function input and output arguments etc., in order that the automatically generated tables do not have empty entries. Also new User's Guides for sublibraries Rotational and SIunits have been added and the User's Guide on top level (Modelica.UsersGuide) has been improved.
   
• Initialization options have been added to the Modelica.Blocks.Continuous blocks (NoInit, SteadyState, InitialState, InitialOutput). If InitialOutput is selected, the block output is provided as initial condition. The states of the block are then initialized as close as possible to steady state. Furthermore, the Continuous.LimPID block has been significantly improved and much better documented.
   
• The Modelica.Media library has been significantly improved:
  New functions setState_pTX, setState_phX, setState_psX, setState_dTX have been added to PartialMedium to compute the independent medium variables (= state of medium) from p,T,X, or from p,h,X or from p,s,X or from d,T,X. Then functions are provided for all interesting medium variables to compute them from its medium state. All these functions are implemented in a robust way for all media (with a few exceptions, if the generic function does not make sense for a particular medium).

The following new components have been added to existing libraries:

The following components have been improved:

The following errors have been fixed:

Extends from Modelica.Icons.ReleaseNotes (Icon for release notes in documentation).

Modelica.UsersGuide.ReleaseNotes.Version_2_2

Version 2.2 is backward compatible to version 2.1.

The following new libraries have been added:

The following changes have been performed in the Modelica.Mechanics.MultiBody library:

• Component MultiBody.World has a new parameter driveTrainMechanics3D. If set to true, 3D mechanical effects of MultiBody.Parts.Mounting1D/Rotor1D/BevelGear1D are taken into account. If set to false (= default), 3D mechanical effects in these elements are not taken into account and the frame connectors to connect to 3D parts are disabled (all connections to such a disabled connector are also disabled, due to the new feature of conditional declarations in Modelica language 2.2)
• All references to "MultiBody.xxx" have been changed to "Modelica.Mechanics.MultiBodys.xxx" in order that after copying of a component outside of the Modelica library, the references still remain valid.

Extends from Modelica.Icons.ReleaseNotes (Icon for release notes in documentation).

Modelica.UsersGuide.ReleaseNotes.Version_2_1

This is a major change with respect to previous versions of the Modelica Standard Library, because many new libraries and components are included and because the input/output blocks (Modelica.Blocks) have been considerably simplified:

• An input/output connector is defined without a hierarchy (this is possible due to new features of the Modelica language). For example, the input signal of a block "FirstOrder" was previously accessed as "FirstOrder.inPort.signal[1]". Now it is accessed as "FirstOrder.u". This simplifies the understanding and usage especially for beginners.
• De-vectorized the Modelica.Blocks library. All blocks in the Modelica.Blocks library are now scalar blocks. As a result, the parameters of the Blocks are scalars and no vectors any more. For example, a parameter "amplitude" that might had a value of "{1}" previously, has now a value of "1". This simplifies the understanding and usage especially for beginners.
  If a vector of blocks is needed, this can be easily accomplished by adding a dimension to the instance. For example "Constant const[3](k={1,2,3}" defines three Constant blocks. An additional advantage of the new approach is that the implementation of Modelica.Blocks is much simpler and is easier to understand.

The discussed changes of Modelica.Blocks are not backward compatible. A script to automatically convert models to this new version is provided. There might be rare cases, where this script does not convert. In this case models have to be manually converted. In any case you should make a back-up copy of your model before automatic conversion is performed.

The following new libraries have been added:

The following existing libraries outside of the Modelica standard library have been improved and added as new libraries (models using the previous libraries are automatically converted to the new sublibraries inside package Modelica):

As a result, the ModelicaAdditions library is obsolet, because all components are either included in the Modelica library or are replaced by much more powerful libraries (MultiBody, StateGraph).

The following new components have been added to existing libraries.

The following bugs have been corrected:

Other changes:

• All connectors are now smaller in the diagram layer. This gives a nicer layout when connectors and components are used together in a diagram
• Default instance names are defined for all connectors, according to a new annotation introduced in Modelica 2.1. For example, when dragging connector "Flange_a" from the Rotational library to the diagram layer, the default connector instance name is "flange_a" and not "Flange_a1".
• The Modelica.Mechanics.Rotational connectors are changed from a square to a circle
• The Modelica.Mechanics.Translational connectors are changed from a green to a dark green color in order that connection lines can be better seen, especially when printed.
• The Modelica.Blocks connectors for Real signals are changed from blue to dark blue in order to distinguish them from electrical signals.

Extends from Modelica.Icons.ReleaseNotes (Icon for release notes in documentation).

Modelica.UsersGuide.ReleaseNotes.Version_1_6

Added 1 new library (Electrical.MultiPhase), 17 new components, improved 3 existing components in the Modelica.Electrical library and improved 3 types in the Modelica.SIunits library. Furthermore, this User's Guide has been started. The improvements in more detail:

New components

New examples

The following new examples have been added to Modelica.Electrical.Analog.Examples:

CharacteristicThyristors, CharacteristicIdealDiodes, HeatingNPN_OrGate, HeatingMOSInverter, HeatingRectifier, Rectifier, ShowSaturatingInductor ShowVariableResistor

Improved existing components

In the library Modelica.Electrical.Analog.Ideal, a knee voltage has been introduced for the components IdealThyristor, IdealGTOThyristor, IdealDiode in order that the approximation of these ideal elements is improved with not much computational effort.

In the Modelica.SIunits library, the following changes have been made:

Extends from Modelica.Icons.ReleaseNotes (Icon for release notes in documentation).

Modelica.UsersGuide.ReleaseNotes.Version_1_5

Added 55 new components. In particular, added new package Thermal.HeatTransfer for modeling of lumped heat transfer, added model LossyGear in Mechanics.Rotational to model gear efficiency and bearing friction according to a new theory in a robust way, added 10 new models in Electrical.Analog and added several other new models and improved existing models.

New components

Package-specific Changes

• All example models made encapsulated
• Upper case constants changed to lower case (cf. Modelica.Constants)
• Introduced Modelica.SIunits.Wavelength due to typo "Wavelenght"
• Introduced ModelicaAdditions.Blocks.Logical.Interfaces.Comparison due to typo "Comparision"
• Changed these components of *.Blocks to block class, which have not been already of block type
• Changed *.Interfaces.RelativeSensor to partial models

Class-specific Changes

Modelica.SIunits

Removed final from quantity attribute for Mass and MassFlowRate.

Modelica.Blocks.Math.Sum

Implemented avoiding algorithm section, which would lead to expensive function calls.

Modelica.Blocks.Sources.Step

block Step "Generate step signals of type Real"
        parameter Real height[:]={1} "Heights of steps";
 // parameter Real offset[:]={0} "Offsets of output signals";
// parameter SIunits.Time startTime[:]={0} "Output = offset for time < startTime";
// extends Interfaces.MO          (final nout=max([size(height, 1); size(offset, 1); size(startTime, 1)]));
        extends Interfaces.SignalSource(final nout=max([size(height, 1); size(offset, 1); size(startTime, 1)]));

Modelica.Blocks.Sources.Exponentials

Replaced usage of built-in function exp by Modelica.Math.exp.

Modelica.Blocks.Sources.TimeTable

Interface definition changed from

    parameter Real table[:, :]=[0, 0; 1, 1; 2, 4] "Table matrix (time = first column)";

to

    parameter Real table[:, 2]=[0, 0; 1, 1; 2, 4] "Table matrix (time = first column)";

Did the same for subfunction getInterpolationCoefficients.

Bug in getInterpolationCoefficients for startTime <> 0 fixed:

        ...
                end if;
          end if;
          // Take into account startTime "a*(time - startTime) + b"
          b := b - a*startTime;
        end getInterpolationCoefficients;

Modelica.Blocks.Sources.BooleanStep

block BooleanStep "Generate step signals of type Boolean"
        parameter SIunits.Time startTime[:]={0} "Time instants of steps";
        parameter Boolean startValue[size(startTime, 1)]=fill(false, size(startTime, 1)) "Output before startTime";
        extends Interfaces.BooleanSignalSource(final nout=size(startTime, 1));
equation
        for i in 1:nout loop
//   outPort.signal[i] = time >= startTime[i];
          outPort.signal[i] = if time >= startTime[i] then not startValue[i] else startValue[i];
        end for;
end BooleanStep;

Modelica.Electrical.Analog

Corrected table of values and default for Beta by dividing them by 1000 (consistent with the values used in the NAND-example model):

• Semiconductors.PMOS
• Semiconductors.NMOS

Corrected parameter defaults, unit and description for TrapezoidCurrent. This makes the parameters consistent with their use in the model. Models specifying parameter values are not changed. Models not specifying parameter values did not generate trapezoids previously.

Icon layer background changed from transparent to white:

• Basic.Gyrator
• Basic.EMF
• Ideal.Idle
• Ideal.Short

Basic.Transformer: Replaced invalid escape characters '\ ' and '\[newline]' in documentation by '|'.

Modelica.Mechanics.Rotational

Removed arrows and names documentation from flanges in diagram layer

Modelica.Mechanics.Rotational.Interfaces.FrictionBase

Modelica.Mechanics.Rotational.Position

Replaced reinit by initial equation

Modelica.Mechanics.Rotational.RelativeStates

Bug corrected by using modifier stateSelect = StateSelect.prefer as implementation

Modelica.Mechanics.Translational.Interfaces.flange_b

Attribute fillColor=7 added to Rectangle on Icon layer, i.e., it is now filled with white and not transparent any more.

Modelica.Mechanics.Translational.Position

Replaced reinit by initial equation

Modelica.Mechanics.Translational.RelativeStates

Bug corrected by using modifier stateSelect = StateSelect.prefer as implementation

Modelica.Mechanics.Translational.Stop

Use stateSelect = StateSelect.prefer.

Modelica.Mechanics.Translational.Examples.PreLoad

Improved documentation and coordinate system used for example.

ModelicaAdditions.Blocks.Nonlinear.PadeDelay

Replaced reinit by initial equation

ModelicaAdditions.HeatFlow1D.Interfaces

Definition of connectors Surface_a and Surface_b:
flow SIunits.HeatFlux q; changed to flow SIunits.HeatFlowRate q;

MultiBody.Parts.InertialSystem

Icon corrected.

Extends from Modelica.Icons.ReleaseNotes (Icon for release notes in documentation).

Modelica.UsersGuide.ReleaseNotes.Version_1_4

• Several minor bugs fixed.
• New models:
  Modelica.Blocks.Interfaces.IntegerRealInput/IntegerRealOutput,
  Modelica.Blocks.Math.TwoInputs/TwoOutputs
  Modelica.Electrical.Analog.Ideal.IdealOpAmp3Pin,
  Modelica.Mechanics.Rotational.Move,
  Modelica.Mechanics.Translational.Move.
  

Version 1.4.1beta1 (February 12, 2001)

Adapted to Modelica 1.4

Version 1.3.2beta2 (June 20, 2000)

• New subpackage Modelica.Mechanics.Translational
• Changes to Modelica.Mechanics.Rotational:
  New elements:

  IdealGearR2T    Ideal gear transforming rotational in translational motion.
  Position        Forced movement of a flange with a reference angle
                                     given as input signal
  RelativeStates  Definition of relative state variables
  

• Changes to Modelica.SIunits:
  Introduced new types:
  type Temperature = ThermodynamicTemperature;
  types DerDensityByEnthalpy, DerDensityByPressure, DerDensityByTemperature, DerEnthalpyByPressure, DerEnergyByDensity, DerEnergyByPressure
  Attribute "final" removed from min and max values in order that these values can still be changed to narrow the allowed range of values.
  Quantity="Stress" removed from type "Stress", in order that a type "Stress" can be connected to a type "Pressure".
• Changes to Modelica.Icons:
  New icons for motors and gearboxes.
• Changes to Modelica.Blocks.Interfaces:
  Introduced a replaceable signal type into Blocks.Interfaces.RealInput/RealOutput:

  replaceable type SignalType = Real
  

  in order that the type of the signal of an input/output block can be changed to a physical type, for example:

  Sine sin1(outPort(redeclare type SignalType=Modelica.SIunits.Torque))
  

Version 1.3.1 (Dec. 13, 1999)

First official release of the library.

Extends from Modelica.Icons.ReleaseNotes (Icon for release notes in documentation).