Skip to content

UseCases

Michael Wetter edited this page May 25, 2018 · 2 revisions

This page lists a use case for an end-user and a developer.

End User

The End-User represents the user who is testing a controller that they have developed on a BOPTEST test case. The End-User will:

  1. Download selected test case image and deployment script from repository of test cases.
  2. Use the deployment script to deploy the test case image as a docker container and establish communication with the test case container through a port mapping.
  3. Interact with the test case container to retrieve information about the test, such as available control signals, measurements, communication steps, and input measurement forecasts (e.g. weather for MPC).
  4. Set the communication step size, in simulated seconds, with the test case or set the test case to advance according to the wall clock.
  5. Link the controller to be tested to the test case.
  6. Run the test to completion, exchanging measurement, forecast, and updated control signal data at every communication step.
  7. Receive KPI results of test.
  8. Receive other data collected during test, such as control signal or measurement trajectories, for further post processing.

Test Case Developer

The test case developer represents the user who is creating test case emulator models, defining control signals and measurements, setting simulation options (such as solver, tolerance, available communication steps), and writing KPI calculations. The test case developer will:

  1. Create the test case modelica model according to the specifications and template outlined in the test case requirements document.
  2. Include any required exogenous input data, such as weather files or occupancy schedules, defined outside of the model.
  3. Peer review test case model.
  4. Export the model as an FMU.
  5. Finalize test of the simulation of the FMU with exogenous input data locally.
  6. Use script to use FMU and exogenous input data files to build docker image representing test case (template docker images and associated files developed by infrastructure developer)
  7. Post docker image to BOPTEST test case repository.
Clone this wiki locally