---

### Warning: Due to some issues with missing TLS support in some of the used Python libraries this implementation is currently not able to `install` any Modelica packages.

In the meantime we've started a Go language implementation that does not suffer those restrictions and which is now the primary development version on the master branch.

As of now it is planned to continue the active development on the master branch with the Go language implementation as it provides the user with self-contained ex ecutables that do not depend on any installed run-time environment like the Python version does.

The old and discontinued Python version will be kept on this python-version branch for historical reasons.

---

Impact

Impact is a Modelica package manager.

The concept was first presented in impact - A Modelica Package Manager

Michael Tiller, Dietmar Winkler (2014). impact - A Modelica Package Manager, Proceedings of the 10th International Modelica Conference, March 10-12, 2014, Lund, Sweden http://dx.doi.org/10.3384/ecp14096543

Installation and Usage

Install by using pip:

• Linux/Mac:$ pip install impact
• Windows:c:\> pip.exe install impact

and you should be able to use the command

impact -h

to get the usage information displayed.

Conventions

Impact follows a "convention over configuration" philosophy. That means that if you follow some reasonable conventions (that generally reflect best practices), the system should work without the need for any manual configuration. Here are the conventions that Impact expects:

• The name of the repository should match (case included) the name of your library.

• Semantic Versioning - To identify a library release, simply attach a tag to the release that is a semantic version (an optional "v" at the start of the tag name is allowed).

• Place the package.mo file for your library in one of the following locations within the repository:

  • ./package.mo (i.e., at the root of the repository)

  • ./<LibraryName>/package.mo (i.e., within a directory sharing the name of the library)

  • ./<LibraryName> <Version>/package.mo (i.e., within a directory sharing the name of the library followed by a space followed by the tag name, without any leading v present)

Development

The development takes place on https://github.com/xogeny/impact