https://github.com/geontech/fei_filereader
Frontend Interfaces 2.0-compliant tuner with simulation backend (based on files)
https://github.com/geontech/fei_filereader
Last synced: about 1 year ago
JSON representation
Frontend Interfaces 2.0-compliant tuner with simulation backend (based on files)
- Host: GitHub
- URL: https://github.com/geontech/fei_filereader
- Owner: Geontech
- License: lgpl-3.0
- Created: 2016-03-10T19:49:20.000Z (about 10 years ago)
- Default Branch: master
- Last Pushed: 2018-06-07T19:34:16.000Z (almost 8 years ago)
- Last Synced: 2025-01-21T12:48:46.196Z (over 1 year ago)
- Language: C++
- Size: 133 KB
- Stars: 2
- Watchers: 7
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# FEI_FileReader
Frontend Interfaces 2.0-compliant tuner with simulation backend (based on files)
## Docker-Compose Example
This Docker Compose definition runs an OmniORB server (Names and Events), Domain, and an instance of the FEI FileReader. This is a stand-alone demo configuration.
### Setup
In in order to use this however, the FEI FileReader needs RF Snapshots mounted to `/var/rf_snapshots`.
For the sake of this demo configuration, the YML file assumes you'll keep the files in the `snapshots` directory (i.e., relative to the YML definition file itself). To bring up the demo configuration:
docker-compose up -d
You can then use `docker exec` to join the running Domain or FEI FileReader device where you can then use the Python sandbox to setup allocations.
If you're using [Docker-REDHAWK's](http://github.com/GeonTech/docker-redhawk) scripts, that's the `login` script. You can also use the `rhide` script to start an IDE instance to setup allocations and stream data.