Skip to content

Commit f51617b

Browse files
authored
Update README.md
1 parent c4e6942 commit f51617b

File tree

1 file changed

+5
-33
lines changed

1 file changed

+5
-33
lines changed

apps/stability_app/README.md

+5-33
Original file line numberDiff line numberDiff line change
@@ -1,29 +1,15 @@
1-
# Example Application
1+
# Stability Application
22

3-
The Example App show how data from the vehicle can be received by an application running in the vehicle.
3+
The Stability app uses vehicle dynamics data and identifies if vehicle is stable or not. Signals used here are Yawrate, Lateral acceleration and Steering angle.
4+
The eCAL data is sampled at 20Hz, so for each Variance, max and min of the above parameters are collected and used to provide a threshold value is the vehicle is wobbling or not.
45

56
## Build
67

7-
When running `restart-shift2sdv`, or explicitly the `build-apps` script, the Example App will be build and containerized automatically as `ghcr.io/eclipse-sdv-hackathon-chapter-two/shift2sdv/example_app:latest`.
8-
9-
Of course, you are free to build manually if needed by calling the following command from the example_app folder:
8+
When running `restart-shift2sdv`, or explicitly the `build-apps` script, the Example App will be build and containerized automatically as `ghcr.io/eclipse-sdv-hackathon-chapter-two/shift2sdv/stability_app:latest`.
109

1110
```shell
1211
podman build -t example_app:latest .
1312
```
14-
15-
**Note:** Inside the test-vehicle the Example App will run on ARM-Platform. Test the build by running the command above and ask the hack coaches to build your image for ARM to run it inside the test vehicle.
16-
17-
## Running
18-
19-
The Example App is automatically started by Ankaios as there is an entry for it in the [shift2sdv_manifest.yaml](shift2sdv_manifest.yaml).
20-
21-
In the test vehicle the Example App container image will be started and managed by Eclipse Ankaios.
22-
23-
Talk to the hack coaches to build a multi-platform or ARM image before trying to run the app in the vehicle.
24-
25-
## Development
26-
2713
### Run
2814

2915
Start the app inside the devcontainer for local development:
@@ -32,9 +18,7 @@ Start the app inside the devcontainer for local development:
3218
python3 example_app.py
3319
```
3420

35-
### Testing with mock data
36-
37-
Ask the hack coaches for an eCAL recording to play back a recorded driving scenario with eCAL and to receive the vehicle dynamics data in the Example App for development.
21+
### Testing with Funny driving
3822

3923
Place the downloaded eCAL recording in a `measurements/` folder next to the current file.
4024

@@ -43,15 +27,3 @@ Start the eCAL recording within the devcontainer, replace `<recording_folder>` w
4327
```shell
4428
ecal_play -m measurements/<recording_folder>
4529
```
46-
47-
Start the Example App inside the devcontainer as shown above.
48-
49-
You should see logs of the JSON data received, and in the web browser the tachometer should show some speed values.
50-
51-
For debugging reasons you can start the eCAL Monitor terminal UI in a separate terminal window by running:
52-
53-
```shell
54-
ecal_mon_tui
55-
```
56-
57-
This lists all eCAL topics with their contents and meta information the host or container can see.

0 commit comments

Comments
 (0)