This part of the documentation provides a bit more technical background for users who would like to understand and administrate the platform. Let us start with a schematic:
The three components, node, wireless router, and ethoscope are represented here. Node and ethoscope run various "services" (custom or not), which are individually represented by green rectangles. Services are daemons controlled by systemd.
As such, you can:
systemctl status <name-of-the-service>.systemctl <instruction> <name-of-the-service>.journalctl -u <name-of-the-service>The node typically exists on the network with the ip 192.168.1.2. It runs several services:
ethoscope_node.service, which provides a user interface to detect, start, stop... ethoscopes, on port 80.ethoscope_backup.service, which saves locally data from all Ethoscopes. Ethoscope .db files are saved on /ethoscope_data periodically (typically every 5min).ethoscope_video_backup.service (not shown in the figure below). It saves video chunks that were acquired by ethoscopes.ethoscope_update_node.service which allows users to update the software of the Node and of the Ethoscopes, on port 8888.Each ethoscope runs their own:
ethoscope_device, on port 9000. It exposes status, tracking data, snapshot... This server is normally only accessed indirectly through the node server. The server can be queried to start/stop video tracking. Importantly, they analyse raw video themselves.MySQL databases in which all secondary data (e.g. shape and position of individual animals) resulting from the ongoing experiment are stored.