## 4 Model Operation Example  
This paper takes the sewage system of a certain ship as an example. After the programmer displays the parameters such as pipelines, flow direction, nodes, and tanks from the drawings in an SVG format and positions the controls like the pumps, valves, flow labels \"Gpipe\", and pressure labels \"Ppipe\" in the required places (as shown in Figure 8), the SVG images are then converted into PNG format. The WPF control image is also saved as a PNG after hiding the base map. These two images are then fed into YOLOv5 for recognition. The results are shown in Figures 9 and 10, with the numbers indicating the confidence scores. From the results, it can be seen that most of the confidence scores are above 0.75, indicating that YOLOv5 can accurately recognize various pipeline elements and control components in the sewage system. YOLOv5 also identifies and saves the position parameters of the elements in the images to a designated CSV file, as shown in Table 1. After data integration and conversion, the data are fed into the pipeline network calculation program. Figure 7: Pipeline node processing flow. When the user enters the program, the interface is displayed as shown in Figure 7. Taking the \"Clean Train Tank\" module as an example, when the user clicks on controls such as pumps and valves, the corresponding controls will change to the color of the pipeline to indicate they are open. Once the three valves and one pump on the left side are all opened, the C# calculation program will determine that the pipe segment is flowing. Since this pipe segment serves as both the source and terminal segment, the program will conclude that the pipeline is open. Then, the pre-entered flow and pressure values will be calculated and displayed on the corresponding labels. On the right side, where no pump is running, when the user opens the corresponding valve, since this pipeline has only one valve, the program will read the data stored in the valve and display it. In cases where there is a branch, the flow will be evenly distributed. Figure 11 shows the program display after the user has completed several steps. Figure 8: Programmer’s design drawing. Figure 9: YOLOv5 recognition of pipeline network. \begin{table}
\begin{tabular}{c c c c c c} \hline \hline
**PipeID** & **Name** & **PipeDirection** & **PipeConnectA** & **PipeConnectB** & **IsSource** & **IsTerminal** \\ \hline
1 & LineValve7 & BA & 9A & & TURE & FALSE \\  & LineValve1, LineValve2, & & & & TURE & TURE \\  & LineValve3, LinePump1 & & & & & \\
3 & LineValve4 & BA & 8A & & TURE & FALSE \\
4 & & BA & 6A & 5A, 7A & FALSE & FALSE \\
5 & LineValve5 & BA & 4B, 7A & & TURE & FALSE \\
6 & & AB & 4A & & FALSE & TURE \\
7 & & AB & 4B, 5A & & FALSE & TURE \\
8 & & AB & 3A & & FALSE & FALSE \\
9 & LineValve7 & AB & 1A & 15B, 16A & FALSE & FALSE \\
10 & LineValve6 & BA & 8B, 11A & & TURE & FALSE \\
11 & & AB & 8B, 10A & 16B, 17A & FALSE & TURE \\
12 & LineValve8 & BA & & 14A, 18A & TURE & FALSE \\
13 & LineValve9 & AB & & 14B15A & FALSE & FALSE \\
14 & LinePump2V & BA & 12B, 18A & 13B, 15A & FALSE & FALSE \\
15 & & BA & 13B, 14B & 9B, 16A & FALSE & FALSE \\
16 & LineValve10 & BA & 9B, 15B & 11B, 17A, 19A & FALSE & FALSE \\
17 & LineValve11 & BA & 11B, 16B, 19A & & FALSE & FALSE \\
18 & LineValve12 & AB & 12B, 14A & & FALSE & TURE \\
19 & & CC & 11B, 16B, 17A & 22A, 23A & FALSE & FALSE \\
20 & LineValve14 & BA & & 24A, 28A & FALSE & TURE \\
21 & LineValve15 & BA & & 24B, 29A & FALSE & TURE \\
22 & LineValve13 & BA & 19B, 23A & & TURE & FALSE \\
23 & & CC & 19B, 22A & 27B & FALSE & FALSE \\
24 & & BA & 20B, 28A & 21B, 25A, 29A & FALSE & FALSE \\
25 & & BA & 21B, 24B, 29A & 26A, 33A & FALSE & FALSE \\
26 & LineValve16, LinePump3 & BA & 25B, 33A & 27A, 30A & FALSE & FALSE \\
27 & LineValve17 & BA & 26B, 30A & 23B, 31A & FALSE & FALSE \\
28 & LineValve18 & AB & 24A & & FALSE & TURE \\
29 & LineValve19 & AB & 21B, 24B, 29A & FALSE & TURE \\
30 & LineValve20 & BA & 26B, 27A & & TURE & FALSE \\ \hline \hline \end{tabular}
\end{table}