Adaptive scanning of ARM's radars and lidars is an important capability that could further enhance the scientific impact of these systems. Previous efforts like that during TRACER have showcased the feasibility of adaptive scanning while utilizing ARM's scanning radar systems (CSAPR2). There is a need to develop an open, consistent, science rules driven, and reusable framework in ARM for implementing these requests with the CSAPR2 (BNF, DUSTIEAIM) and eventually other instruments.
It is proposed that ARM dedicate resources towards the development of this framework for interacting with ARM's CSAPR2 radars in an open and modular fashion to allow extension to other instruments as well. While the current method to allow PI's access to change configuration files has worked for TRACER, it introduces concerns related to security and potential damage to the radar.
While the new CSAPR2 should have storm tracking software that can operate by itself, it would also be beneficial for ARM to develop an internal system for cell-tracking and relaying scan requirements to the CSAPR2s to allow cell-tracking capabilities for users that may not have the capabilities themselves to allow for a more robust and flexible tracking system.
This effort is broken into two phases of development that can be worked in parallel.
Full google document can be found here: https://docs.google.com/document/d/1oEuIVDKguSkb2pmo_7ucmr387qEk-8099A5djL8ZNB4/edit?usp=sharing
Phase 1: API for Interfacing with the CSAPR
-------------------------------------------------------
The goal is to demonstrate the capability to adaptively scan the new CSAPR2 at DUSTIEAIM. While the radar will be different from the BNF CSAPR2, we propose to initially start testing and the development of a "plug-in" for interacting with the BNF system in the summer of FY25 when there are no chances of precipitation.
The first task (1.1.1) is to have base scripts that can send a sequence of scans to the BNF CSAPR2 by September 30, 2025. This will require the developers gaining access to the CSAPR computers and working with SDS and the engineering team on how to provide instructions for scanning. For TRACER, this included modifying a configuration file. Existing code from TRACER to interact with the radar can be found in https://code.arm.gov/instrument/CSAPR_Cell_Tracking (Java code). The second part of this (1.1.2) is to develop the "plug-in" for the DUSTIEAIM CSAPR once installed and verified as operational.
The second task (1.2) of this phase is to develop a middleware layer or API to translate scan requests from PI's, mentors, or other users as needed into valid radar instructions. This layer would verify the user against a known list of users authorized to access the radar and during which periods, and verify that the proposed scan strategy will stay within the engineering limits defined by the mentor before sending instructions to the radar.
This middle layer system would take in a variety of input such as
ARM username and token (data discovery) to verify approval to operate. We should only allow one PI at a time to direct the CSAPR with overrides for the radar mentor team
Code for the instrument system to apply to (BNFCSAPR, SGPXSAPR, etc..)
Scan Metadata (Further defined by task 1.1)
Center of azimuth sector
Limits of azimuth sector
Elevation limits
Sequence of PPI elevations or RHI azimuths
Ideally within a few seconds, the inputs should be verified and the scan information sent to the radar. The system should also be able to default back to an approved operational scan strategy once the input has timed out. This may require further discussions with the radar mentor team on possibilities that do not require manual intervention with the radar.
This system should be modular to allow for the easy addition of additional instruments such as the scanning cloud radars (SACR) or scanning doppler lidars as "plug-ins". The API should be completed by December 2025 to allow for testing with the DUSTIEAIM radar prior to DUSTIEAIM.
Phase 2: ARM Cell Tracking
----------------------------------
The second phase (which can be developed in parallel with phase 1) is to develop cell-tracking capabilities to provide input into the API, similar to what was done in TRACER. This framework should include lessons learned from existing frameworks and work with existing open-source cell-tracking software. The first task (2.1) will be to engage with the scientific community around potential needs for this framework. It is anticipated that it should be able to run solely off ARM's real-time CSAPR2 data flow (as SDS set up for TRACER) but could also operate with real-time external data such as NEXRAD. The second task (2.2) is to review existing cell-tracking software and choose a system to base the initial ARM-Track system on taking into account feedback from the community.
The goal is for this system to analyze near-real-time data from the CSAPR, identify cells of interest based on a set of default requirements as defined by ARM and scientific requirements defined by PIs, and provide the necessary information to the ARM-Scan API.
Task 3 (2.3) will be the creation of this framework around a cell-tracking software to allow for varied inputs for tracking but also varied requirements from ARM and the science community. This system should take into account the needs of the radar mentor team for routine PPIs and scans over the main ARM site to aid in calibration and quality control. All metadata from the tracking should be saved and processed into an ARM-standard product for the users.
After verifying the consistent output from the tracking software, it should be tested with one of the CSAPR2's (2.4) during either maintenance mode with the new CSAPR2 prior to DUSTIEAIM or with the BNF CSAPR2 during a day free of precipitation.
The final task of phase 2(2.5) would be the development of a GUI interface. This interface would display real-time data from the radars and allow the ability to select cells based on the real-time data and have the radar track the cell selected to the end of life or upon new input from the user. The interface should allow the display of all variables through a selectable interface. Additional settings such as azimuth width could be entered by the user but also would need to be calculated from the cell information.
---------------------------
Depending on the speed of this entire system, edge computing may need to be explored. All these systems should be modular enough to operate on different systems as may be required.