This wiki is not maintained! Do not use this when setting up AuScope experiments!

This is an old revision of the document!

Chair: Atifur

Attended: Prad, Ross, Simin, Jessie, Katie, Tiege, Lucia, Jamie

Apologies:

Absent: Mas, Lucas

General Issues

• Ke clock jump/delay drift, fs crash

Mk5 is proving unreliable, maser is not stable that might also cause it. Might change to backup Mk5 ke if keeps happening. FS crash related to Mk5.

• Ke ES Oven V in maserke was red (>25) for a minute then went blue (<1), but seems to be oscillating around the green range.

One of the external heater that stabilizes it. Brett is checking whether it is a read-out error or temperature problem. Should be fixed in a couple weeks time.

• AUM missed scans

Related to scheduling error.

• start/end messages

Modify the end messages by hand. Include all the information about the experiment to your knowledge.

• Dec/Jan roster

New PhD recruits.

• 0 UT session start

Perhaps start of 2019. Rearrangement of shifts?

Handover Issues

• CRDS97 :
  • 08:54:53 UT - error m5 -900 : already off and error m5 -906 mark5 return code 6: inconsistent or conflicting request. The recording halted as a consequence of the above error.

Scheduling issue.

• 09:28:47 UT - For the previous 28.7 minutes, there was a watchdog warning which prevented the log from getting updated.

Error with Summary file. Should be careful since automatically generates schedule file.

• AUM004 :
  • Drift in delay. DBBC rebooted.

Unknown. Could be maser.

• After Experiment - data between ~0900-1510 recorded to another module, required for the subsequent R4 experiment. This had to be deleted in order to observe R4855 - no data will be available for correlation. Please make sure to check that the correct module is selected if the mark5/pcfs has been power cycled, before resuming the schedule.