Skip to content
Snippets Groups Projects
Commit 858d3f1f authored by Samuel Truman's avatar Samuel Truman
Browse files

Update README.md

parent 015830be
Branches main
No related tags found
No related merge requests found
# Web-Based Supervisor Monitor
Next-generation, web-based supervisor monitor
The supervisor monitor is a specialized component of the VIA-VR platform designed to provide real-time oversight during VR sessions. It allows a supervising professional, such as a healthcare provider or educator, to monitor the progress and engagement of users within the VR experience. This tool not only displays live updates of the user's interactions and physiological responses (requires the measurements engine developed by the HCI group at the University of Würzburg) but also enables the supervisor to make adjustments to the VR environment on-the-fly. This feature is particularly useful for tailoring the experience to the user's needs, ensuring optimal engagement and effectiveness of the VR therapy or training session.
# Related Repositories
- [Unity Supervisor Monitor Integration](https://gitlab2.informatik.uni-wuerzburg.de/GE/Dev/ViaVR/components/unity-supervisor-monitor-integration) - The Unity counterpart
- [Unity Streaming Web App](https://gitlab2.informatik.uni-wuerzburg.de/GE/Dev/ViaVR/components/unity-streaming-web-app) - Server to stream video and audio from Unity to the supervisor monitor
- [HCI server package](https://gitlab2.informatik.uni-wuerzburg.de/GE/Dev/ViaVR/hci/measurement-engine-packaged) - Measurements engine
## Prerequisites
......@@ -33,29 +28,44 @@ Next-generation, web-based supervisor monitor
- Copy the setup executable from the `out` folder to the target PC
- Run the setup executable on the target PC
## Privacy
The issue of privacy, especially regarding future use cases of the monitor, like transmitting Health data, is from great
concern. Therefore, it is aimed to at least provide some kind of encryption.
- ### Encryption
## About VIA-VR
The VIA-VR project presents an innovative authoring platform designed to revolutionize Virtual Reality (VR) applications in the medical domain. At its core, this platform aims to empower medical professionals to create, modify, and implement VR experiences tailored for educational and therapeutic purposes. By significantly lowering the barriers to entry in terms of development effort and technical expertise required, VIA-VR stands at the forefront of making VR technology more accessible and applicable in healthcare settings.
VIA-VR is developed by a consortium consisting of:
- Games Engineering Group, Julius-Maximilians-Universität Würzburg
- Human-Computer-Interaction Group, Julius-Maximilians-Universität Würzburg
- Graphics & Geometry Group, Technische Universität Dortmund
- Health-Technology-Ethics Group, Evangelische Hochschule Ludwigsburg
- Articy Software GmbH & Co. KG, Germany
The VIA-VR project is funded by the German Federal Ministry of Education and Research (BMBF) as part of the research initiative for Human-Technology Interaction ”Digital Platforms: Interactive Assistance Systems for Humans“ (project number 16SV8444).
This repository contains a package that is part of the VIA-VR project, made by the Games Engineering Group at the Julius-Maximilians-Universität Würzburg.
[Project website](https://www.hci.uni-wuerzburg.de/projects/via-vr/)
## Project Status
This repository contains the codebase and resources for a completed research project. The project has reached its intended goals and objectives, and no further active development or maintenance is planned.
## Contributing
As there is no active maintainer for this project, contributions are not being actively reviewed or merged. However, if you wish to extend or build upon this work, you are welcome to fork the repository and continue development on your own.
Currently, all data send via the Rest Api are encrypted via Tls. So only the initial broadcast and the monitor streaming is not. But it is to note that currently it is not validated via the certificate that the other end is really who it supposed to be. Instead, a short ID is generated on connection to mask the thumbprint and identify the other end via this ID.
- ### Monitor Identification
The identification of the monitor is implemented via a simple 6-Digit ID that is generated on Start Up.
It is also known when connecting to the monitor what kind of transmissions the monitor expects.
## Contact
## General Architecture
Prof. Dr. Sebastian von Mammen
Games Engineering Group
Chair of Human-Computer Interaction
Julius-Maximilians-Universität Würzburg
sebastian.von.mammen@uni-wuerzburg.de
- ### Connection
The connection is first initialised by the monitor sending a broadcast message in the current network.
This broadcast message is then accepted by the Unity Application that again then sends a Keep Alive message to the
monitor. When the monitor receives this first initial keep alive message he in turn also sends a keep Alive message
to the Unity Application. When from either point the keep alive message is missing for more than 15 seconds
the connection is broken and the Application is searching for a new Server and vice versa.
Connection also can be broke up manually by sending a disconnect message to the other device.
- ### Rest Requests
The Supervisor Monitor internally runs a fully functional Rest server. So to receive or transmit data it is recommended to use the Rest api. Special behaviour for certain identifiers can be changed by AddGetResponse, AddPostResponse and AddPutResponse.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment