When you have set up the data collection in CL61, CL61 starts generating netCDF files. To customize the data output, you can define an averaging scheme for the measurements, and set netCDF attributes and netCDF file naming.
- Establish a maintenance connection to the device.
Change the user level.
Define the averaging settings.
set algo.1averaging.interval <averaging interval> set algo.1averaging.depolinterval <averaging interval> set reporting.profile.interval <profile interval> set reporting.livefile.profilesperfile <number of profiles>
The maximum averaging is 2 minutes inside CL61. If you want additional averaging, do this outside CL61, for example, in Matlab.
The backscatter profiles and the depolarization ratio profile have separate averaging schemes. The minimum averaging scheme for attenuated backscatter is 5 seconds and for depolarization 10 seconds.
The interval parameters are a multiple of 5-second profiles (n × 5).
The following table shows examples of measurement averaging schemes.
Parameter Value DEFAULT 5 profiles with 1-minute averaging, 5-minute file algo.l1averaging.interval 12 algo.l1averaging.depolinterval 12 reporting.profile.interval 12 reporting.livefile.profilesperfile 5 MAXIMUM RESOLUTION 12 ABS profiles with 5-second averaging, 12 DEPOL profiles with 10-second rolling averaging, 1‑minute file algo.l1averaging.interval 1 algo.l1averaging.depolinterval 2 reporting.profile.interval 1 reporting.livefile.profilesperfile 12 24 ABS profiles with 5-second averaging, 24 DEPOL profiles with 1-minute rolling averaging, 2‑minute file algo.l1averaging.interval 1 algo.l1averaging.depolinterval 12 reporting.profile.interval 1 reporting.livefile.profilesperfile 24 30 profiles with 2-minute averaging, 60-minute file algo.l1averaging.interval 24 algo.l1averaging.depolinterval 24 reporting.profile.interval 24 reporting.livefile.profilesperfile 30
The following table explains the parameters.
Parameter Description Value / range Default algo.l1averaging.interval
Number of 5‑second profiles averaged in each x‑polarization (XPOL), p‑polarization (PPOL), and attenuated backscatter profile (ABS).
Averaging refers to the running average, so for every 5‑second profile, this parameter averages the number of previous profiles. The algorithm produces profiles in 5‑second intervals.
You can specify that profiles recorded in netCDF files are averaged by n × 5 seconds, where n = 1 … 24.
1 … 24
Number of 5‑second profiles averaged in each depolarization profile.
For every 5-second profile, this parameter averages the number of previous profiles. The algorithm produces profiles in 5-second intervals.
2 … 24
Interval for reporting to write out profiles.
Only every nth profile is written to the netCDF file where the n is this parameter.
This parameter can be used to avoid overlapping averaging. For example, if algo.l1averaging.interval is set to 6 corresponding to a 30‑second time span, this parameter can be set to 6 as well to get the profiles every 30 seconds.
1 ... no maximum
Number of profiles that are written in each .nc file.
If reporting.profile.interval is set to 6 and this parameter is set to 4, one netCDF file will cover 2 min of data (6 × 4 × 5 s).
1 … 1440
Define the reporting unit (meters or feet).
The measurements are always done in meters and the conversion to feet is done before writing the netCDF file.
set reporting.netcdf.unit <m∣ft>
Define what metadata to include in the netCDF files if needed.
set reporting.netcdf.institution set reporting.netcdf.comment
Define how the netCDF files are named using prefixes if needed.
set reporting.livefile.nameprefix <prefix> set cl.sender.fileprefix <prefix>
Parameter Description reporting.livefile.nameprefix Adds user-selected prefix to the netCDF file when transferring the file to the customer server. cl.sender.fileprefix Adds user-selected prefix to netCDF file when transferring the file to the customer server. Used to distinguish files coming from different CL61 devices.
The filename format is the following: <cl.sender.fileprefix><reporting.livefile.nameprefix>_YYYYMMDD_HHmmss.nc
Check the changed configuration.
get algo get reporting
The changes are visible in the netCDF files immediately.