INTO-CPS Application Release 3.4.6
INTO-CPS Application Release 3.4.6 (14/02/2018)
What's New?
This release is the first under the INTO-CPS Association. There has been minor changes such that various links are changed to point to the new INTO-CPS Association repositories.
Requirements
In order to open projects from Git, including the public examples import, you will need to have Git installed and available in your system path.
If you want to run co-simulations, you will need the COE. It can be downloaded from the download manager inside the app. In order to run the COE, you need to have Java 8 installed. Java 8 is also required to co-simulate FMUs exported from Overture.
To run Design Space Exploration Experiments, Python 2.7 is required.
The app has no other dependencies and no installation is required. Simply unzip and run. On Windows, the app cannot be run from a mapped network drive.
Known Issues
There are a few known issues with the app:
- When creating/importing projects, no check is made for the root path. The project will not open/import correctly if given an invalid path.
- When importing examples or projects through Git, if you import an already imported project to the same location, the download manager will sometimes hang at 0% progress.
- The app has no explicit setting for proxies. In order to use it behind a proxy, please set the
HTTP_PROXYenvironment variable (see https://github.com/into-cps/intocps-ui/wiki/Working-with-a-proxy)
For the full list, see https://github.com/into-cps-association/into-cps-application/issues. Some issues have not been moved from the old repository at https://github.com/into-cps/intocps-ui/issues yet.
Problems and Troubleshooting
If you run into any problems, please use the issue tracker at https://github.com/into-cps-association/into-cps-application/issues. The tracker is also available from within the app itself via Help > Report Issue