This module contains the classes

  • refactor, a module that assists in refactoring Modelica classes,
  • Tester that runs the unit tests of the Buildings library,
  • Validator that validates the html code of the info section of the .mo files, and
  • Annex60 that synchronizes Modelica libraries with the Annex60 library.
  • ErrorDictionary that contains information about possible error strings.

Refactoring code

This module provides functions to

  • create Modelica packages and autopopulate for example the and package.order files
  • move Modelica classes include any associated .mos scripts, reference results and images, and
  • rewrite the package.order file.

Create in directory a Modelica package.

If directory/ exists, this method returns and does nothing. Otherwise, it creates the directory and populates it with a and package.order file.

Parameters:directory – The directory in which the package is created.
buildingspy.development.refactor.move_class(source, target)

Move the class from the source to the target name.

Both arguments need to be Modelica class names such as Buildings.Fluid.Sensors.TemperatureTwoPort, or a directory with a top-level file, such as Buildings/Fluid, that contains a file Buildings/Fluid/

  • source – Class name of the source.
  • target – Class name of the target.

Usage: Type

>>> import buildingspy.development.refactor as r
>>> r.move_class("Buildings.Fluid.Movers.FlowControlled_dp",         >>>              "Buildings.Fluid.Movers.Flow_dp") #doctest: +SKIP
buildingspy.development.refactor.write_package_order(directory=u'.', recursive=False)

Write the package.order file in the directory directory.

Any existing package.order file will be overwritten.

  • directory – The name of the directory in which the package.order file will be written.
  • recursive – Set to True to recursively include all sub directories.

Usage: To rewrite package.order in the current directory, type

>>> import buildingspy.development.refactor as r
>>> r.write_package_order(".") #doctest: +ELLIPSIS

Regression tests

class buildingspy.development.regressiontest.Tester(check_html=True, tool=u'dymola', cleanup=True)

Class that runs all regression tests using Dymola.

Initiate with the following optional arguments:

  • check_html – bool (default=True). Specify whether to load tidylib and perform validation of html documentation
  • tool – {dymola, omc, jmodelica}. Default is dymola, specifies the tool to use for running the regression test with run().
  • cleanup – bool (default=True). Specify whether to delete temporary directories.

This class can be used to run all regression tests.

Regression testing using Dymola

For Dymola, this module searches the directory CURRENT_DIRECTORY/Resources/Scripts/Dymola for all *.mos files that contain the string simulate, where CURRENT_DIRECTORY is the name of the directory in which the Python script is started, as returned by the function getLibraryName(). All these files will be executed as part of the regression tests. Any variables or parameters that are plotted by these *.mos files will be compared to previous results that are stored in CURRENT_DIRECTORY/Resources/ReferenceResults/Dymola. If no reference results exist, then they will be created. Otherwise, the accuracy of the new results is compared to the reference results. If they differ by more than a prescibed tolerance, a plot such as the one below is shown.


Plot that compares the new results (solid line) of the regression test with the old results (dotted line). The blue line indicates the time where the largest error occurs.

In this plot, the vertical line indicates the time where the biggest error occurs. The user is then asked to accept or reject the new results.

For Dymola, the regression tests also store and compare the following statistics for the initialization problem and the time domain simulation:

  1. The number and the size of the linear system of equations,
  2. the number and the size of the nonlinear system of equations, and
  3. the number of the numerical Jacobians.

To run the regression tests, type

>>> import os
>>> import buildingspy.development.regressiontest as r
>>> rt = r.Tester(tool="dymola")
>>> myMoLib = os.path.join("buildingspy", "tests", "MyModelicaLibrary")
>>> rt.setLibraryRoot(myMoLib)
>>> # doctest: +ELLIPSIS
Using ... of ... processors to run unit tests for dymola.
Number of models   : ...
          blocks   : 0
          functions: 0
Generated ... regression tests.
Script that runs unit tests had 0 warnings and 0 errors.
See 'simulator-....log' for details.
Unit tests completed successfully.
Execution time = ...

To run regression tests only for a single package, call setSinglePackage() prior to run().

Regression testing using JModelica

For JModelica, the selection of test cases is done the same way as for Dymola. However, the solver tolerance is obtained from the .mo file by reading the annotation Tolerance=”value”.

For JModelica, a JSON file stored as Resources/Scripts/BuildingsPy/conf.json can be used to further configure tests. The file has the syntax

    "jmodelica": {
      "ncp": 500,
      "rtol": 1E-6,
      "solver": "CVode",
      "simulate": True,
      "translate": True,
      "time_out": 600
    "model_name": "Buildings.Fluid.Examples.FlowSystem.Simplified2"

Any JSON elements are optional, and the entries shown above are the default values, except for the relative tolerance rtol which is read from the .mo file. However, with rtol, this value can be overwritten. Note that this syntax is still experimental and may be changed.

areResultsEqual(tOld, yOld, tNew, yNew, varNam, filNam)

Return True if the data series are equal within a tolerance.

  • tOld – List of old time values.
  • yOld – Old simulation results.
  • tNew – Time stamps of new results.
  • yNew – New simulation results.
  • varNam – Variable name, used for reporting.
  • filNam – File name, used for reporting.

A list with False if the results are not equal, and the time of the maximum error, and a warning message or None. In case of errors, the time of the maximum error may by None.

are_statistics_equal(s1, s2)

Compare the simulation statistics s1 and s2 and return True if they are equal, or False otherwise.


Set the batch mode flag.

Parameters:batchMode – Set to True to run without interactive prompts and without plot windows.

By default, the regression tests require the user to respond if results differ from previous simulations. This method can be used to run the script in batch mode, suppressing all prompts that require the user to enter a response. If run in batch mode, no new results will be stored. To run the regression tests in batch mode, enter

>>> import os
>>> import buildingspy.development.regressiontest as r
>>> r = r.Tester()
>>> r.batchMode(True)
>>> # doctest: +SKIP

Check whether all required python modules are installed.

If some modules are missing, then an ImportError is raised.


Flag, if set to False, then the temporary directories will not be deleted after the regression tests are run.

Parameters:delete – Flag, set to False to avoid the temporary directories to be deleted.

Unless this method is called prior to running the regression tests with delete=False, all temporary directories will be deleted after the regression tests.

static expand_packages(packages)

Expand the packages from the form A.{B,C} and return A.B,A.C :param: packages: A list of packages


Return the argument in exponential notation, with non-significant zeros removed.


Return the name of the library that will be run by this regression test.

Returns:The name of the library that will be run by this regression test.

Return the name of the modelica executable.

Returns:The name of the modelica executable.

Returns the number of regression tests that will be run for the current library and configuration.

static get_plot_variables(line)

For a string of the form *y={aa,bb,cc}*, optionally with whitespace characters, return the list [aa, bb, cc]. If the string does not contain y = …, return None.

A usage may be as follows. Note that the second call returns None as it has a different format.

>>> import buildingspy.development.regressiontest as r
>>> r.Tester.get_plot_variables('y = {"a", "b", "c"}')
[u'a', u'b', u'c']
>>> r.Tester.get_plot_variables('... x}, y = {"a", "b", "c"}, z = {...')
[u'a', u'b', u'c']
>>> r.Tester.get_plot_variables("y=abc") is None
static get_tolerance(library_home, model_name)

Return the tolerance as read from the .mo file.

  • library_home – Home directory of the library.
  • model_name – Name of the model.

Return the name of the log file of the unit tests, such as unitTests-jmodelica.log or unitTests-dymola.log.


Sets a flag that, if False, does not test the export of FMUs.

Parameters:fmu_export – Set to True to test the export of FMUs (default), or False to not test the FMU export.

To run the unit tests but do not test the export of FMUs, type

>>> import os
>>> import buildingspy.development.regressiontest as r
>>> r = r.Tester()
>>> r.include_fmu_tests(False)
>>> # doctest: +SKIP

Return True if the program is an executable

static isValidLibrary(library_home)
Returns true if the regression tester points to a valid library
that implements the scripts for the regression tests.
Parameters:library_home – top-level directory of the library, such as Buildings.
Returns:True if the library implements regression tests, False otherwise.

Set the pedantic Modelica mode flag.

Parameters:pedanticModelica – Set to True to run the unit tests in the pedantic Modelica mode.

By default, regression tests are run in non-pedantic Modelica mode. This however will be changed in the near future.

>>> import os
>>> import buildingspy.development.regressiontest as r
>>> r = r.Tester()
>>> r.pedanticModelica(True)
>>> # doctest: +SKIP

Print the number of models, blocks and functions to the standard output stream


Run all regression tests and checks the results.

Returns:0 if no errros and no warnings occurred during the regression tests, otherwise a non-zero value.

This method

  • creates temporary directories for each processors,
  • copies the directory CURRENT_DIRECTORY into these temporary directories,
  • creates run scripts that run all regression tests,
  • runs these regression tests,
  • collects the dymola log files from each process,
  • writes the combined log file unitTests-x.log to the current directory, where x is the name of the Modelica tool,
  • for Dymola, compares the results of the new simulations with reference results that are stored in Resources/ReferenceResults,
  • writes the message Regression tests completed successfully. if no error occured,
  • returns 0 if no errors and no warnings occurred, or non-zero otherwise.

Build the data structures that are needed to parse the output files.

Param:root_package The name of the top-level package for which the files need to be parsed. Separate package names with a period.

Exclude from the regression tests all tests specified in excludeFile.

Parameters:excludeFile – The text file with files that shall be excluded from regression tests

Set the root directory of the library.

Parameters:rootDir – The top-most directory of the library.

The root directory is the directory that contains the Resources folder and the top-level file.

Usage: Type
>>> import os
>>> import buildingspy.development.regressiontest as r
>>> rt = r.Tester()
>>> myMoLib = os.path.join("buildingspy", "tests", "MyModelicaLibrary")
>>> rt.setLibraryRoot(myMoLib)

Set the number of parallel threads that are used to run the regression tests.

Parameters:number – The number of parallel threads that are used to run the regression tests.

By default, the number of parallel threads are set to be equal to the number of processors of the computer.


Set the name of one or multiple Modelica package(s) to be tested.

Parameters:packageName – The name of the package(s) to be tested.

Calling this method will cause the regression tests to run only for the examples in the package packageName, and in all its sub-packages.

For example:

  • If packageName = Annex60.Controls.Continous.Examples, then a test of the Annex60 library will run all examples in Annex60.Controls.Continous.Examples.
  • If packageName = Annex60.Controls.Continous.Examples,Annex60.Controls.Continous.Validation, then a test of the Annex60 library will run all examples in Annex60.Controls.Continous.Examples and in Annex60.Controls.Continous.Validation.

Call this function to show the GUI of the simulator.

By default, the simulator runs without GUI

test_OpenModelica(cmpl=True, simulate=False, packages=[u'Examples'], number=-1)

Test the library compliance with OpenModelica.

This is the high-level method to test a complete library, even if there are no specific .mos files in the library for regression testing.

This method sets self._nPro to 1 as it only works on a single core. It also executes self.setTemporaryDirectories()

  • cpml – Set to True for the model to be compiled.
  • simulate – Set to True to cause the model to be simulated (from 0 to 1s).
  • packages – Set to a list whose elements are the packages that contain the test models of the library
  • number – Number of models to test. Set to -1 to test all models.


  1. In a python console or script, cd to the root folder of the library

    >>> t = Tester()
    >>> t.test_OpenModelica() # doctest: +ELLIPSIS, +REPORT_NDIFF
    OpenModelica script ...OMTests.mos created
    Logfile created: ...OMTests.log
    Starting analysis of logfile
    Tested 4 models:
      * 0 compiled successfully (=0.0%)
    Successfully checked models:
    Failed model checks:
      * BuildingsPy.buildingspy.tests.MyModelicaLibrary.Examples.BooleanParameters
      * BuildingsPy.buildingspy.tests.MyModelicaLibrary.Examples.Constants
      * BuildingsPy.buildingspy.tests.MyModelicaLibrary.Examples.MyStep
      * BuildingsPy.buildingspy.tests.MyModelicaLibrary.Examples.ParameterEvaluation
    More detailed information is stored in self._omstats

This function allows to use existing results, as opposed to running a simulation.

Parameters:dirs – A non-empty list of directories that contain existing results.

This method can be used for testing and debugging. If called, then no simulation is run. If the directories ['/tmp/tmp-Buildings-0-zABC44', '/tmp/tmp-Buildings-0-zQNS41'] contain previous results, then this method can be used as

>>> import buildingspy.development.regressiontest as r
>>> l=['/tmp/tmp-Buildings-0-zABC44', '/tmp/tmp-Buildings-0-zQNS41']
>>> rt = r.Tester()
>>> rt.useExistingResults(l)
>>> # doctest: +SKIP

Write in Resources/Scripts/OpenModelica/compareVars files whose name are the name of the example model, and whose content is:

compareVars :=

These files are then used in the regression testing that is done by the OpenModelica development team.

Validator of syntax

class buildingspy.development.validator.Validator

Class that validates .mo files for the correct html syntax.


Validate the experiment setup in .mo and .mos files.

Parameters:root_dir – Root directory.

This function recursively validates all .mo files in a package.

If there is malformed html code in the info or the revision section, then this function write the error message of tidy to the standard output.

Note that the line number correspond to an intermediate format (e.g., the output format of tidy), which may be different from the .mo file.

Parameters:rootDir – The root directory of the package.
Returns:str[] Warning/error messages from tidylib.
Usage: Type
>>> import os
>>> import buildingspy.development.validator as v
>>> val = v.Validator()
>>> myMoLib = os.path.join(                    "buildingspy", "tests", "MyModelicaLibrary")
>>> # Get a list whose elements are the error strings
>>> errStr = val.validateHTMLInPackage(myMoLib)

Merging Annex60 library

class buildingspy.development.merger.IBPSA(ibpsa_dir, dest_dir)

Class that merges a Modelica library with the IBPSA library.

Both libraries need to have the same package structure.

By default, the top-level packages Experimental and Obsolete are not included in the merge. This can be overwritten with the function set_excluded_packages().

static filter_files(file_list, pattern)

Return file_list for those that match pattern.

Currently, pattern can contain at most one wildchar (‘*’) character.

  • file_list – List of files.
  • pattern – Pattern that is used to match files.
A typical usage is
>>> import buildingspy.development.merger as m
>>> m.IBPSA.filter_files(['a.txt', 'aa/b.txt', 'aa/bb/c.txt'], '*.txt')
>>> m.IBPSA.filter_files(['a.txt', 'aa/b.txt', 'aa/bb/c.txt'], 'aa/*.txt')
>>> m.IBPSA.filter_files(['a.txt', 'aa/b1.txt', 'aa/b2.txt', 'aa/bb/c.txt'], 'aa/*.txt')
[u'aa/b1.txt', u'aa/b2.txt']

Merge all files except the license file and the top-level


This method is experimental. Do not use it without having a backup of your code.

This function merges the IBPSA library into other Modelica libraries.

In the top-level directory of the destination library, this function creates the file .copiedFiles.txt that lists all files that have been copied. In subsequent calls, this function deletes all files listed in .copiedFiles.txt, then merges the libraries, and creates a new version of .copiedFiles.txt. Therefore, if a model is moved in the IBPSA library, it will also be moved in the target library by deleting the old file and copying the new file.

This function will merge all Modelica files, Modelica scripts, regression results and images. An exception is the file IBPSA/, as libraries typically have their own top-level package file that contains their release notes and version information.

When copying the files, all references and file names that contain the string IBPSA will be renamed with the name of the top-level directory of the destination library. Afterwards, the package.order files will be regenerated, which allows libraries to have Modelica classes in the same directory as are used by the IBPSA library, as long as their name differs.

Parameters:overwrite_reference_results – Boolean True causes the reference results to be overwritten, False causes the reference results to be skipped if they already exist. Note that if the reference result does not yet exist, it will be merged regardless of the setting of this parameter.
A typical usage is
>>> import buildingspy.development.merger as m
>>> import os
>>> home = os.path.expanduser("~")
>>> root = os.path.join(home, "test")
>>> ibpsa_dir = os.path.join(root, "modelica", "IBPSA")
>>> dest_dir = os.path.join(root, "modelica-buildings", "Buildings")
>>> mer = m.IBPSA(ibpsa_dir, dest_dir) # doctest: +SKIP
>>> mer.merge()                            # doctest: +SKIP
static remove_library_specific_documentation(file_lines, library_name)

Remove library specific content.

For example, for the Buildings and IDEAS libraries, include the section in the commented block below, but keep the comment as an html-comment for other libraries.

<!-- @include_Buildings @include_IDEAS
some documentation to be used for
Buildings and IDEAS library only.
Parameters:file_lines – The lines of the file to be merged.
Returns:The lines of the files, with comments removed as indicated by the tag(s) in the comment line.

Set the packages that are excluded from the merge.

Parameters:packages – A list of packages to be excluded.

Error dictionary

class buildingspy.development.error_dictionary.ErrorDictionary

Class that contains data fields needed for the error checking of the regression tests.

If additional error messages need to be checked, then they should be added to the constructor of this class.


Return the dictionary with all error data


Increment the error counter by one for the error type defined by key.

Parameters:key – The json key of the error type.

Return a copy of the dictionary’s list of keys.


Return a copy of the tool messages as a list.