Project

General

Profile

Change Request #3853

Revisit method to launch co-simulation server

Added by Simon Barner 12 months ago. Updated 5 months ago.

Status:
Closed
Priority:
Low
Assignee:
-
Category:
-
Start date:
10/15/2019
Due date:
% Done:

100%

Estimated time:

Description

  • Are there more elegant ways to launch the process rather than assuming that Java is in the path and executing java -jar coe.jar?
  • Check if MacOS support can easily be provided
fmi_co-simulation.af3_23 (59.5 KB) fmi_co-simulation.af3_23 Tiziano Munaro, 04/15/2020 11:03 PM

Related issues

Related to Bug #3926: [Cosimulation] Complete re-implementation of the cosimulation logic requiredNew02/04/2020

Related to Change Request #4001: [FMI] Redirect COE output / Hide COE output from the AF3 consoleNew04/15/2020

History

#1 Updated by Simon Barner 12 months ago

  • Subject changed from Revisit method to launch Co-Simulation server to Revisit method to launch co-simulation server
  • Description updated (diff)

#2 Updated by Tiziano Munaro 8 months ago

  • Related to Bug #3926: [Cosimulation] Complete re-implementation of the cosimulation logic required added

#3 Updated by Tiziano Munaro 5 months ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 70

#4 Updated by Tiziano Munaro 5 months ago

The COE service is now

  • imported as a library and started using its main method instead of run via a OS-level command (java -jar coe.jar),
  • executed as a runnable
  • within an Eclipse job
  • asynchronously (thus not blocking the UI while running - however, an activity indicator in the lower right corner of the window provides the necessary feedback to the user).

Moreover, in case of an error (e.g. due to an FMU not being found), the ErrorStream of the HttpURLConnection is read, providing the user with useful feedback instead of just returning the response code.

Testing:
  • The attached AF3 project contains a component architecture called Original. Feel free to export one or both of the components (Step and Relay) as FMUs, combining them in other component architectures which can then be co-simulated.
  • Keep in mind that the co-simulation of a component architecture is only possible with at least two components, where at least one of them has to have an FMU specification.
  • When handling state automata make sure that they are deterministic! Otherwise, semantically correct FMUs are generated which, however, won't perform any action.

#5 Updated by Tiziano Munaro 5 months ago

  • Related to Change Request #4001: [FMI] Redirect COE output / Hide COE output from the AF3 console added

#6 Updated by Alexander Diewald 5 months ago

  • Assignee changed from Alexander Diewald to Johannes Eder

Merged. Please close.

#7 Updated by Johannes Eder 5 months ago

  • Status changed from Resolved to Closed
  • Assignee deleted (Johannes Eder)

Also available in: Atom PDF