The software system design based on the cesium optical pumping magnetometer proposed in this paper addresses the shortcomings of traditional magnetometer systems, providing an effective solution with innovation and practical value. Actual marine trials have been conducted, and the results show that these features significantly improve the measurement accuracy and reliability of the cesium optical pumping magnetometer. Below are my comments:

1. The paper mainly discusses the software, while Section 2.1 introduces the hardware platform. Is the software running on a self-developed hardware platform or a commercially available magnetometer? If it is a self-developed hardware platform, what is its acquisition structure? What are its sensitivity and dynamic range?
2. Please translate the text in the lower right corner of Figure 11 into English.
3. Ensure proper capitalization in Figures 3 and 6.
4. In Table 1, correct the capitalization of "NET communication Interface" and check other tables for similar issues.

This manuscript has unique and innovative ideas. It has optimized the high-precision magnetometer system. It is strongly recommended to make minor modifications to be accepted.

As the title suggests 'Software Program Development,' there is limited insight provided or explanation given about the software and its application. It would be more justified and balanced if these aspects were explained in detail alongside the other content.

Line 35-39: How does the system address environmental interference, particularly in cases of natural calamities like thunderstorms? If there is a power surge or electronic failure, how does the system recover, and what role does the software play in ensuring data integrity and functionality?

Line 40: What is the latency period for data transfer during real-time magnetic compensation data processing? Could you elaborate on the specific real-time processing functions implemented?

Figure 1: What is the internet speed required for optimal system performance? Is real-time monitoring conducted over a LAN or WAN? Additionally, is remote access to the system possible?

Section 2.2: Are all the software components mentioned in the paper developed by the authors, or are commercial software applications utilized as well?

Clarification Request: Could you elaborate on the following software components mentioned in the paper?

    Automatic Switching Software

    Data Acquisition Software

    Real-Time Magnetic Compensation Data Processing Software

    Data Storage Software

    Data Communication Software

If all these software components were developed by the authors, what platforms or programming environments were used? Are there any unique features that distinguish these software systems from existing commercial solutions?

What programming languages or tools were used to develop the automatic switching software?

Can you elaborate on the architecture or specific programming frameworks used for the data acquisition and processing software?

Table 1 (Page 7): The alignment of "Interface" and "Description" in Table 1 appears inconsistent. Could you clarify or suggest adjustments for better presentation?

Dead Zones Mitigation:

    How is the optimal working probe determined when multiple probes might provide conflicting data in overlapping regions?

    Are there specific algorithms or machine learning models used to predict or mitigate dead zones?

Hardware Integration:

    Are there specific challenges in integrating optically pumped probes at different angles? For instance, does this require precise mechanical alignment or calibration?

    How does the system ensure synchronization between the hardware probes and the software modules?

Data Communication and Storage:

    What protocols are used for data communication between the data acquisition system and the upper computer main control system?

    Can the system handle large-scale data or high-speed data streams without compromising performance?

Communication Protocols:

        What measures are in place to ensure reliability and low latency in the RS422-based serial communication and Gigabit Ethernet protocols?

        Are there potential limitations in data transmission rates that might impact real-time processing?

Restart Mechanism:

        How does the system ensure that data acquisition resumes smoothly and without duplication after a restart?

Data File Creation:

        How does the system ensure that data integrity is maintained when storage space is low?

        Are there provisions for automated alerts or logs when data acquisition is halted due to insufficient disk space?