Date:
Sunday, July 2, 2017
Telescope:
CTIO Blanco 4-m
Submitter:
Douglas Tucker
Submitter Email:
Observer Support:
Alfredo Zenteno
Night Assistant:
Alberto Alvarez
Also Present:
Manuel Hernandez
Problems:
None.
Program:
Proposal:
2017A-0910
Target of Oportunity:
No
Time Observed:
5.75
Time Engineering:
0.0
Time lost technical:
0.0
Time lost weather:
0.0
Time lost other:
0.0
Description:
Catching Supernovae in the Act with KEGS (Kepler Extra-Galactic Survey) and DECam
Primary Investigator:
Brad Tucker
Email:
Institution:
ANU
Instrument:
CTIO 4m DECam
Organization:
N/A
Total Program Time:
5.75
Proposal:
2017A-0260
Target of Oportunity:
No
Time Observed:
5.25
Time Engineering:
0.0
Time lost technical:
0.25
Time lost weather:
0.0
Time lost other:
0.25
Description:
Blanco Imaging of the Southern Sky (BLISS)
Primary Investigator:
Marcelle Soares-Santos
Email:
Institution:
Fermilab
Instrument:
CTIO 4m DECam
Organization:
NOAO
Total Program Time:
5.75
| Total Times | Time Observed | Time Engineering | Time lost technical | Time lost weather | Time lost other | Total Program Time |
|---|---|---|---|---|---|---|
| 2017-07-02 | 11.0 | 0.0 | 0.25 | 0.0 | 0.25 | 11.5 |
Printer-friendly version
At the beginning of the second half, we had some difficulties with the locally run version of the SISPI Observer Console at Fermilab. Perhaps due to network issues, we were not able to activate the “edit” button under the System Control tab of the Observer Console in order to change the contents of the observers/proposal id/program/investigator box. We tried for about 10 minutes with no success, even though SISPI control via “observer” status had been handed over to us. We eventually gave up, fired up the vncviewer, and started the SISPI Observer Console on observer2.ctio.noao.edu and ran it from there. Strangely, it appears that other buttons other than the “edit” button under the System Control tab of the Observer Console still worked on the locally run SIPSI (but this was not fully verified). We had also experienced some trouble with this “edit” button on 2017-07-01, but the problem resolved itself then after only about a minute (and could have just been user error… for that matter, the current problem could have also been user error, but it is hard to say… we did not have any problems with it on the remotely run SISPI via vncviewer…)
Other issues at the beginning of the second half that caused the second half program to have a delayed start of about 30 minutes was an issue on our side involved with our script to generate appropriate json files for the second half program. This was resolve on our end, but did delay the start of the second half program.