Mapping the Atmospheric Network Monitor

[chromiumboy]

With the merging of PR #32294, the atmospheric network monitor is now available to be mapped on space stations

Mappers should note that, in order to be fully functional, the atmospheric network monitor also requires gas pipe sensors (introduced in PR #33128) to be mapped onto the same grid; they will relay important information about the current status of the grid's pipe network to the monitor

Gas pipe sensors should be treated like regular gas pipes; they cannot be placed over an existing pipe that has the same orientation. At a minimum, one gas pipe sensor should be connected to the distro loop and another to the waste loop. Only one sensor is necessary per pipe subnetwork; pipe subnetworks are comprised of the stretch of pipes that lie between pairs of atmos devices, such as filters, mixers, and pumps. Gas pipe sensors will not cause a split in a subnetwork, but you should note that valves will combine/split the subnetworks they connect when they are open/closed, respectively

By default, the monitor status panel will display a list of entries, one for each gas pipe sensor, with the names of the gas pipe sensors and their network addresses in the entry header. If the sensors are labelled (i.e., with a hand labeller), only the label on the gas pipe sensor will be displayed. Several prototype variants for the gas pipe sensor have been included in the PR which have different labels; these include 'distribution loop', 'waste loop', 'mixed air', as well for the different parts of the TEG. The header of each entry in the subpanel also has a colored stripe on the left-hand side; the color of this strip can be changed by spray painting the gas pipe sensor with the desired color

Gas pipe sensors are listed on the monitor in the order that they are attached to the grid. Note that there is no need to link them with the monitors, it's all handled automatically in the code

Maps which have been updated

• Amber
• Bagel
• Box
• Cog
• Core
• Fland
• Gate
• Marathon
• Meta
• Oasis
• Omega
• Packed
• Reach
• Loop

[HyperB1]

Could the Atmospheric Network Monitor functionality have been integrated into the Atmospheric Alerts Computer?

[chromiumboy]

Could the Atmospheric Network Monitor functionality have been integrated into the Atmospheric Alerts Computer?

I find there's too much data to neatly convey on one screen (all those overlays to manage on the nav map for a start)

The two consoles complement each other, but they serve two different purposes: the alerts computer is for tracking current issues with the station's atmosphere, while the network monitor is for tracking the status of its pipe infrastructure

Plus I like seeing more consoles around the station :)