Page History
...
Scripts that you have started from within the LCC (as well as the middleware) are managed using tmux sessions (which is similar to screen).
Tmux is used to create, manage and kill virtual console sessions, which can be used for any purpose a console can take care of - in this case e.g. for starting (and stopping) your selected script. Tmux sessions always have a unique name by which they can be identified, e.g. middleware for the Middleware session.
The script that takes care of these sessions also writes command line outputs of the running programs into .../software/../lcc_script_logs. If you want to find out why your program crashed, the contents of this folder might be useful, in addition to log messages in the system and other custom error reports. You can find this folder for remote deployment as well (on the NUCs).
| Info | ||
|---|---|---|
| ||
This folder only appears after you have started a simulation. It is created by the LCC - relative to the LCCs location - to store logs of the running script and Middleware. |
Crash Checker
Most scripts started by the LCC run in tmux sessions (which is similar to screenfor more information, see above). These sessions have distinct names, depending on the program..
| Info | ||
|---|---|---|
| ||
Tasks with a limited runtime are managed using fork and the resulting PID, e.g. for sending reboot commands to the vehicles. These tasks are not observed by the crash checker, as they are not strictly part of a running simulation and are not supposed to be always online. Tmux offers a more convenient way to manage tasks, to detach them from the LCC and to observe if they are still online, and is thus used for any simulation-related externally started program (User-provided script, Middleware, IPs...) |
Sessions exist for the middleware and your script (if a locally running simulation was started). There also exist sessions for the labcam, position detection and other vital features of the LCC (if they are activated).
...
Overview
Content Tools