Friday, May 29, 2020

SVL: Socially Distanced Remote Ops


Due to social distancing guidelines still in effect, Silicon Valley Lines canceled the May ops session originally scheduled for tonight. We discussed doing another remote ops session instead, and decided that this time we'd try to do a session from the club. This was to test both our ability to implement social distancing, as well as whether and how to incorporate remote operators into an operations scheme. Another goal tonight was to stress-test the club's Internet connection with multiple video streams in a multi-user setting.


We set up various cameras to record the action from different angles. We also moved the cameras around to capture trains as they moved from yards over the layout to their destinations for switching.


The verdict:
Over the course of the evening we ran a whopping four trains, instead of the 25 trains we normally run.
We can easily support a remote dispatcher and give remote operators control of a train. We have the technology to do that.

However, our Internet uplink does not support multiple HD streams in parallel. The double-deck arrangement makes visual train control via cameras challenging for a remote operator. While detected sections on the layout work well, and are needed for signaling, not all blocks have detection for various reasons. While normal video encoders for conferencing software prefer to show movement at the cost of lower resolution, for our purposes we probably prefer high resolution at the cost of reduced frame rate.


Even when the county's shelter-in-place orders are lifted, I expect that we will need to continue some form of social distancing measures for the time being, including wearing masks. A well-attended ops session is a lot of fun with a lot of energy in the room. However, the health of club members and visitors is paramount. More discussions are needed to find a way to run an ops session at the club that is fun, but avoids crowding in the aisles, and minimizes health risks. Very likely this will include a remote engineer component, and we need to figure out how to make that fun and satisfying for everyone involved.
[ part 2 ]

No comments: