Develop a generic monitor for logging information generated by various AARTFAAC processing blocks. Possible extension to a control interface talking to MCU001.

transientskp / aartfaac-control

AARTFAAC control scripts

0 stars 0 forks source link

Develop a generic monitor for logging information generated by various AARTFAAC processing blocks. Possible extension to a control interface talking to MCU001. #5

Open hsuyeep opened 9 years ago

hsuyeep commented 9 years ago

We need a tool to collect all logging/monitoring information from various processing blocks, and to display them on a single screen to get an immediate status of the full AARTFAAC pipeline.
Tool should be able to read logging information from file dumps, as well as have a live interface where monitoring data is dumped by each relevant processing block over a known TCP connection.
This tool could possibly have a public interface via a webpage, for any AARTFAAC user to monitor the pipeline, and a private administrator interface for control of AARTFAAC via communication with acontrol running on MCU001.

gijzelaerr commented 9 years ago

did you look at cherimoya?

Error323 commented 9 years ago

Yes, this will be cherimoya eventually! For now however, Peeyush created a small python script that gives us some of the stats that current Cherimoya cannot handle, with the idea to get a feel for the right stats and then come back to Cherimoya and you Gijs for implementing these features.

hsuyeep commented 9 years ago

Hi Giijs, no, I've not looked at Cherimoya in great detail, will do that now. Right now what I have is the ability to parse the gpucorr output and pipeline logs, and to display uncalibrated visibilities in a matplotlib window. Like Folkert said, this is a light weight tool which can be run to quickly check if observations are setup correctly and working. For long term runs, Cherimoya would be more friendly.

-- P On 06-Feb-2015, at 12:33 PM, F. Huizinga wrote:

Yes, this will be cherimoya eventually! For now however, Peeyush created a small python script that gives us some of the stats that current Cherimoya cannot handle, with the idea to get a feel for the right stats and then come back to Cherimoya and you Gijs for implementing these features.

� Reply to this email directly or view it on GitHub.

gijzelaerr commented 9 years ago

cherimoya may need some refactoring, but eventually it is just some simple scripts translating aartfaac logs into an other log format so graphite (an off the shelf metic storing and visualisation platform) can eat it.