Files are under:
http://www.ovsa.njit.edu/fits/FTST/

in monthly subdirectories: e.g., 
http://www.ovsa.njit.edu/fits/FTST/2023/10

They are text files and are updated every second, and then copied to the output directory, approximately once per second.

The filenames are: flaretest_YYMMDDHHMMSS.txt, (2-digit year). The date refers to the EOVSA scan, and is slightly before the start time of the data in the file.

The file format is simple. There are 8 lines of header information. Here is the header for file:
http://www.ovsa.njit.edu/fits/FTST/2023/10/flaretest_231012151433.txt

SOURCEID: Sun���������
PROJECT: NormalObserving�����������������
SCANID: 231012151433
FREQ BAND:    1.00000000       7.00000000       13.0000000       18.0000000    
Avg. Time:     180
Threshold Time:      20
Nsigmas   3.00000000    
date, time, flare_flag, test_data(1,2,3), test_mean, test_sigma, threshold, count

You are mostly interested in 'Sun' and 'NormalObserving' for the source and scan IDs, but we also create files for the calibration scans.

The last header line defines the 10 columns in the file, The data are in 3 channels with band edges defined in the 4th header line. Data in each channel are sums of the amplitudes of all baselines for 10 of the antennas, excluding auto-correlations.

The quantities 'test_mean' and 'test_sigma' for each second are the mean and standard deviation for the 3rd (13-18 GHz) channel, compiled over the previous 3 minutes. The 'threshold' is mean+3.0*sigma. The 'count' in the last column is the number of non-zero data points used in the mean, and sigma calculation.

The count is not always 180, or 3 minutes, because there is typically a one or two second data gap every 15 minutes in the data..

The 'flare_flag' is mostly always F. To flag a flare the value of data in the third channel has to be greater than the threshold value for 20 seconds. (This is the Threshold Time in the header). The threshold time is set so that only large flares are flagged.