dlakaplan / logparse Goto Github PK

abort_task skip means go to next source
source hasn't risen yet

Slack output in markdown blocks

For
example

would be easier to read too, I think.

just using calls to "mail"?

Note the following convention holds for current/future files written with the VEGAS backend. We may need a slightly different prescription for older sessions using VEGAS+GUPPI/GUPPI alone.

VEGAS file naming convention is as follows:

vegas_[mjd]_[seconds after UTC midnight]_[source]_[scan #]_[file #].fits

...and cal files have cal between the scan/file numbers (see examples below).

vegas_58987_23250_J1713+0747_0001_cal_0001.fits 
vegas_58987_23374_J1713+0747_0002_0001.fits

Operator name
How many sources?
What frequencies?

I think you mentioned this before @dlakaplan. Would it be straightforward to set up a flag to post to pulsars.slack.com (#observations) as a part of my cron job?

Some of the inter-observation time is Rx change etc.

E.g.:

AGBT18B_226.C-VEGAS_1400.2020-05-02_13:53:46+00:00.OPERATOR.log.txt

[project code].[sched block].[start time (UTC)].[observer].log.txt

EXEC wait_puppi_temporary "180" "Check PUPPI power with guppi_adc_hist"

This command pauses execution for 180 sec and requires user input -- useful when remote observers want to check puppi levels and record them in the logs, but normally this is commented out for operator-run observing. It would be good to be able to check for this and output a warning if this line is not commented.