The current rapid-response mode back-end alters the incoming schedule file by adding a scan of a flux density calibrator at an opportune time but not a bandpass calibrator. While this is not a problem at 4cm, in the future I would like to try triggering with the 15 mm receiver but in this band 1934 is not suitable for bandpass calibration. Could the schedule file editing code please be updated to also include a bandpass calibrator scan to be added at an opportune time for observation bands where 1934 is not bright enough?

I think, because the JSON request had just been renamed, due to the source setting, the code got confused and crashed. Error message follows:

`Checking...

starting to run!

Traceback (most recent call last):

File "rapid_response_actioner.py", line 1017, in
atca, sched, logFile)

File "rapid_response_actioner.py", line 301, in checkOverride
monica.updatePoints()

File "/n/ste616/usr/src/atca-rapid-response/webserver/env/lib/python2.7/site-packages/cabb_scheduler/monica_information.py", line 107, in updatePoints

response = self.__comms(data)

File "/n/ste616/usr/src/atca-rapid-response/webserver/env/lib/python2.7/site-packages/cabb_scheduler/monica_information.py", line 101, in __comms

return json.loads(postResponse.text)

File "/usr/lib/python2.7/json/init.py", line 326, in loads
return _default_decoder.decode(s)

File "/usr/lib/python2.7/json/decoder.py", line 365, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())

File "/usr/lib/python2.7/json/decoder.py", line 383, in raw_decode
raise ValueError("No JSON object could be decoded")

ValueError: No JSON object could be decoded
`