smithsonian / r2dbe Goto Github PK

This will require changes to the R2DBE monitor daemon to publish data to redis (with r2dbe_monitor subscribed)

mandc.r2dbe.R2dbe._read_snap should use man_trig=True in the call to snapshots_get.

Firmware modifications to calculate average power over short intervals and log to shared RAM / send over 1GbE.

• one r2daemon.py should be started per backend during start_backend.py
• should include check to see if daemon already running, stop it, then restart after backend config

Expose an easy way through which R2DBE configuration, specifically related to site-specific flags and settings can be changed after startup. One useful solution may be to create an R2DBE object with setter / getter methods.

Implementation may include:

1. bitcode changes to support this, e.g. long-term histograms on 8-bit data
2. software development to solve for ADC parameters
3. system for logging / applying solutions

@lindyblackburn

The only way to read the current time from R2DBE is to add the number of GPS PPS pulses received to the reference time written at startup. This is undesirable, since the time calculation should be based purely on the maser-referenced clock.

A number of noise-box control scripts contain hard-coded IP addresses which must be edited for each site. This causes the site-specific r2dbe repository to be in conflict with maser. If the IP address can be moved to the configuration file, it will be possible to keep these scripts consistent with maser.

switch_get_status.py
switch_set_IF.py
switch_set_noise.py

r2dbe_start.py calls alc.py, which must live in the current working directory. This means r2dbe_start.py must be run from the software directory. It's often more convenient to run r2dbe_start.py from some other location, such as the location where the site-specific configuration file lives.