Cosimulation feature 1

[PandoraQS]

• Coe.json is shown in a cosimulation page
• CoE server runs/stops when "CoE Start"/"CoE Stop" is pressed

TODO:

• Run the cosimulation
• Include a better scrollbar/customize it

[prasadtalasila]

@PandoraQS Thanks for the PR. Please check the comments.

[prasadtalasila]

Given that the application is completely dependent on Maestro, it is probably better to include maestro jar file in resources during the packaging of the application. Remember to use the latest release.
Please add the an npm command that can execute a small javascript file that can download the latest maestro release and place it in resources. This software can be used for npm start and npm test.
In addition, please have the jar integrated into the release being built in npm run dist step.

[prasadtalasila]

You can push this task to next PR if you prefer.

[prasadtalasila]

The application needs to be responsive. For example, please see this code

[PandoraQS]

As discussed, this is the screenshot for the cosimulation process (failing).

[PandoraQS]

Simulation seems to be working now: comparing them, the result outputs.csv is the same as the one of the simulation made with the previous version of the software. Plotting outputs.csv:

[prasadtalasila]

@PandoraQS

Let us follow the INTO-CPS Project (this is a new project created by a user; similar to the project structure of tutorials) as proposed in this discussion.

For this PR, we can work with the following project structure:

FMUs
  FMU1
  FMU2

cosimulation
   default/
      multi-model.json
      experiment.json

results/
  experiment_<timestamp>.csv

into-cps.yml

Please do update the README to reflect the working project structure expected from the user.

[PandoraQS]

config.json (one folder above the codebase):

{
  "coeJarPath": "/home/simone/Scrivania/into-cps-forked_react/coe/coe.jar",
  "simulationConfigPath": "/home/simone/Scrivania/into-cps-forked_react/INTO-CPS Project/default",
  "fmusPath": "/home/simone/Scrivania/into-cps-forked_react/INTO-CPS Project/FMUS",
  "multiModels": "/home/simone/Scrivania/into-cps-forked_react/INTO-CPS Project/default/",
  "outputPath": "/home/simone/Scrivania/into-cps-forked_react/INTO-CPS Project/results"
}

To change the config.coe path in .env:

CONFIG_COE_PATH="/home/simone/Scrivania/into-cps-forked_react/config.json"

[prasadtalasila]

@PandoraQS thanks for the updates. Please check the comments.

[prasadtalasila]

I like this convention. The src/cosimulation is better than src/maestro. The src/cosimulation/maestro.ts could still be there for interacting with Maestro at low-level.

[prasadtalasila]

Please check this file as well.

[PandoraQS]

PR Activities Review:

• Refactored MaestroManager:

  • Brought status messages together into a single file constants/statuses.ts.
  • Improved error handling for Java misconfiguration and startup issues with startMaestro, making messages more about Maestro's runtime behaviour rather than Java.
  • Ensured that startMaestro waits for the server to be ready before proceeding with cosimulation.
  • Improve handling of maestro JAR extraction
  • Fix port conflicts.

• Dynamic Cosimulation menu (Electron) enable/disable according to Maestro state

Added the useCosimulation hook:

• Unifying simulation status and error state in useCosimulation.ts.
• Listened for IPC messages that return simulation update, simulation error, simulation reset.

Cosimulation component refactored:

• Logics useCosimulation.ts separated from the UI CoSimulation.tsx.
• Dynamic showing of simulation results and error (Snackbar).

Improving the communication via IPC.

• Centralized electronAPI and cosimulationAPI in preload.ts for secure and consistent usage, while separating them for a better logical management.

  • Improved type safety with updates to global.d.ts.

• Added Maven JAR download:

  • Add postinstall script which dynamically downloads Maestro JAR from Maven repository.

• Fixed case sensitivity:

  • Standardised imports and filenames CoSimulation and useCosimulation.

• Various improvements:

  • Better TypeScript configuration with more strict checks.
  • Simulation errors are now displayed with visual feedback using Snackbar.

TO BE DONE:

• maestro.ts needs to be reviewed for a better management of the different functions.

[PandoraQS]

I have included the diagrams for the Maestro Model and the interaction between Maestro and the UI via IPC.