parkes radiotelescope users guide · the parkes site contains the 64-metre radiotelescope, ......

69
Parkes RadioTelescope Users Guide 23 November 2012 [email protected]

Upload: vanhanh

Post on 28-Jul-2018

224 views

Category:

Documents


0 download

TRANSCRIPT

Parkes RadioTelescope Users Guide23 November 2012

[email protected]

Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Telescope Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1 Introducing the Parkes Observatory . . . . . . . . . . . . . . . . . . . . . . . . . 31.1 The Parkes RadioTelescope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.2 Transport to the Observatory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.2.1 Travel via Air . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2.2 Train and Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2.3 Travel by Car . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.3 Other Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.4 Observers Quarters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.5 Booking Your Accomodation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.6 Visitors Centre and The Dish Cafe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.7 Observatory Contact Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2 Planning Your Observations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.1 Applying for Observing Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.2 Radio-Frequency Interference Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.3 Observing Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.4 Preparing Schedule Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.5 Sensitivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.6 Parkes Receiver Fleet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.6.1 Receiver Calibration Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.7 Conversion System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.8 Signal Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.9 Standing Wave Reduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.10 Correlators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.11 Dish Surface Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3 Observer Training & Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.2 Duties of an LICENSED OPERATOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.2.1 One in the Tower Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.2.2 SAFETY TIMER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3.2.2.1 Timer Display and States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.2.2.2 Timer Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.2.3 Use of Clear Call Announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.2.4 Absences from an Operating Telescope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.2.5 Non-standard situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.2.6 Emergency Situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.2.7 Fatigue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.3 Duties of a DESIGNATED CONTACT PERSON (DCP) . . . . . . . . . . . . . . . . . . . . . . . . . 193.3.1 Response to the DCP Contact Bell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.3.2 Response of EMERGENCY CALL-OUT to EMERGENCY ALARM . . . . . . . . . 19

3.4 Questions and Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.5 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

4 Observing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254.1 Current Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254.2 The Call–out person . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254.3 The Telescope Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

4.3.1 Master Equatorial Guidance Telescope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254.3.2 The Error Detector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254.3.3 Dish and me movement limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264.3.4 Receiver Translator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

4.4 The Telescope Control Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284.5 Master Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

4.5.1 MCP Panel Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294.5.2 MCP LED Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

4.6 Weather and wind restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324.6.1 Storm Stow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324.6.2 Automated Wind Park . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324.6.3 Current Stow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

4.7 Stowing and Unstowing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.7.1 Stowing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.7.2 UnStowing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344.7.3 When Jack Levers won’t turn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

4.8 Power Supply via Mains/Diesel/UPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354.8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354.8.2 Monitoring Power - Monica . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.8.3 Power failure: Brief mains glitch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.8.4 Power failure: Generator starts automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.8.5 Power failure: Mains Return . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374.8.6 Severe Power Failure - no mains or generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374.8.7 Pre–empting an outage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374.8.8 Resetting the UPS Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

5 Observing Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415.1 Observing Checklist UPSTAIRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415.2 Observing Checklist DOWNSTAIRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

6 Data Reduction and End of Observing . . . . . . . . . . . . . . . . . . . . . 456.1 ATNF Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456.2 livedata & gridzilla . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456.3 ASAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

6.3.1 Example asap batch script: POSITION SWITCHING . . . . . . . . . . . . . . . . . . . . . . . 456.3.2 Example asap batch script: Beam Switching (MX Mode) . . . . . . . . . . . . . . . . . . . . 46

6.4 miriad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476.4.1 Gaussian fits within asap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

6.5 Source finding programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506.6 Other Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506.7 Australia Telescope Online Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506.8 Media Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506.9 Disk Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516.10 Observer Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

7 TroubleShooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537.1 Correlator issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

7.1.1 DFB issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537.1.2 Other Correlators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537.1.3 Block Control Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

7.2 Australia Telescope Distributed Clock Displays all zeros . . . . . . . . . . . . . . . . . . . . . . . . . . . 537.3 Azimuth and/or Zenith Drives Disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547.4 PKDESK requires a restart or crashes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547.5 Mouse seems to have disappeared on BOURBON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557.6 operfcc Reports Y2 Axis Following Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557.7 Loss of 1MHz sampling clock and/or 0.2pps (5-second) pulse . . . . . . . . . . . . . . . . . . . . . . 567.8 Pulsar Data Acquisition Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

7.8.1 Everything crashes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567.8.2 puma dies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577.8.3 DMA timeout on puma . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

7.9 ME or SERVO stops/crashes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577.10 Safety Timer fails to reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587.11 SPD display shows rubbish . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

8 Appendicies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598.1 Trainers Guide to Training Observers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598.2 Site Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

8.2.1 Tower: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618.2.2 Mechanical Workshop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618.2.3 Maser Hut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618.2.4 Generator Hut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618.2.5 Visitor’s Discovery Centre and Cafe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618.2.6 Opera House . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628.2.7 Woolshed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628.2.8 Quarters and Flat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Preface 1

Preface

Telescope Operators

PLEASE NOTE THE FOLLOWING IMPORTANT INFORMATION: The Parkes Radio Tele-scope does NOT employ telescope operators. At least two observers who have been trained tooperate the telescope will therefore be required to be at the observatory for most observing runsof long duration.

First-time Parkes observers should make every effort to plan their arrival to allow betweenthree and five hours to complete the obligatory SAFETY INDUCTION (∼ 2 hours) and TELE-SCOPE OPERATOR (∼ 1-2 hours) training during normal Observatory working hours (8:00am to 4:30 pm Monday to Friday) before their observing run begins.

Prior to your arrival, you should at least skim through Chapter 2 [Planning Your Observa-tions], page 7, Chapter 3 [Observer Training & Safety], page 15 and the Occupational Healthand Safety manual (PDF file).

Conventions

Computer system names and program names appear in a different typeface, e.g. pavo is thename of one of the Parkes observing control computers and tcs is the name of the main Parkesobserving program.

Command examples and filenames appear in a fixed-width typeface and separated from thenormal flow of text. To indicate the context, the commands are shown with the program’scommand prompt or the operating system’s prompt. For example:

pavo-100% tcs

is the command used to start up TCS. It may seem obvious, but you should not type thetext of the prompt when entering commands.

Optional command parameters appear [in square brackets]. Do not type these bracketswhen entering commands.

Another example - when running the ls command from the operating system shell, to listthe files in a directory:

$ ls

The ‘$’ is the operating system prompt, and the command is ‘ls’.

Linux/UNIX is case-sensitive, so operating system commands must be typed in the correctcase (usually lower case).

Chapter 1: Introducing the Parkes Observatory 3

1 Introducing the Parkes Observatory

The Parkes Observatory is located 414.80m above sea level at latitude -32d59m54.263s South,longitude 148d15m48.636s East, 25 kilometers North of the town of Parkes which is approxi-mately 365 kilometres West of Sydney. It is 6 kilometres off the Newell Highway, the main roadfrom Parkes to Dubbo. The Shire has a population of 15,000 and the town a population of10,000 and is in the middle of a rich sheep, wheat producing and mining area. The Observatoryis part of The Australia Telescope National Facility (ATNF), which is run by Astronomy andSpace Science, a division of the Commonwealth Scientific and Industrial Research Organisation(CSIRO). The Parkes site contains the 64-metre RadioTelescope, the 12-metre ASKAP pro-totype antenna, an administration building with offices, workshops and library, an Observer’sQuarters, Visitors Discovery Centre and The Dish Cafe. A map and key of the site can be foundbelow.

Figure 1.1: Parkes Observatory Site Map

001: Radio Telescope 003: Lab/Lunch Room

004: Standby Generator Building 006: Visitors Centre

007: Store Room 008: Observers Quarters

009: Grounds Maintenance Workshop 010: Flammable Liquids Store

013: Store 018: Administration/Receiver Lab

019: Pump House 020: Mechanical & Electrical Workshop

022: Workshop 024: Observing Assist. hse (No2E)

025: Observing Assist. hse (No1W) 026: The Dish Cafe

027: Visitors Toilet 028A: NASA Hut (Demountable)

028B: Office (Demountable) 028C: Office/Workshop (Demountable)

029: Machinery Shed

1.1 The Parkes RadioTelescope

The collecting area of the telescope is a 64-m diameter paraboloid (the dish). The surface is highprecision aluminium millimetre wavepanels to a diameter of 17-m (for operation to 43 GHz),then perforated aluminium plate out to 45-m, and rectangular galvanised steel 5/16-inch meshfor the remainder of the surface. The focal ratio is 0.41 for the full 64-m surface, the focus being

4 Parkes Users Guide

located 26-m above the centre. The aerial cabin, which houses feeds and receiver equipment,is supported by a tripod. Access to the aerial cabin is either by the lift on one of the tripodlegs (the "lift leg") or by a ladder on one of the other legs. The feed platform translator, whichholds up to four receivers, at the base of the aerial cabin has both up/down (focus), lateral androtational movement. Further properties of the RadioTelescope are shown below.

weight of dish: 300 tonnes

weight of counterweights: 475 tonnes

total weight of the dish: 1,000 tonnes

surface area of reflecting mesh: 0.4 hectares (1 acre)

height of concrete tower: 10.7 metres (35 ft)

height to centre of dish: 27.4 metres (90 ft)

height to top of aerial cabin: 58.6 metres (192 ft)

power of Azimuth/Zenith drives: 11 kW (15 hp)

pointing accuracy: $<$20 arcsec

coverage: Az 0-360, El 30.5-88.5

The dish may be operated between the Zenith angle software limits of 1.5 and 59.5 degrees.There are three hardware limits at Zenith angles less than 1.5 degrees, and also another threepast 59.5 degrees. The dish can be "stowed" at a physical limit 30 minutes of arc beyond theZenith. It is constrained in this position by a locking pin. Azimuth angle is measured as 0degrees due north, increasing to the east.

1.2 Transport to the Observatory

There are regular transport services to Parkes from Sydney by planes, trains and automobiles(bus). There are also buses from Canberra, Brisbane, Narrabri, Melbourne and Adelaide thatstop at Parkes.

Airport transfers to and from the site are by Taxi. Please specify on your web booking formif you require a taxi to be booked for you and the time you are arriving/departing. The cost ofthe taxi is Monday - Saturday $70.00 each way, including GST and $80.00 each way on Sundays,including GST - this cost will be charged back to visitors.

1.2.1 Travel via Air

Regional Express have daily flights between Sydney and Parkes using light aircraft. The Parkesairport is 5 kilometres east of the township. The flight, which in 2012 costs about $280 for anadult return (with 21 days notice and including airport tax and GST), is cheaper if your flightto Parkes is included on an international airline ticket. It takes one hour for a direct flight andan hour and three quarters if stopping at Orange or Cudal on the way. Bookings can be made atany travel agent or the airline office. The telephone number for Regional Express Reservationsis 13 17 13 (within Australia).

1.2.2 Train and Bus

CountryLink operate a train out of Sydney which connects with a bus to Parkes at either Orangeor Lithgow. The combined journey takes about eight hours. See their site for updated fares.Countrylink can be contacted on 13 22 32 (within Australia).

1.2.3 Travel by Car

The journey from Sydney to Parkes is 365 kilometres and takes nearly 5 hours. There is achoice of two scenic routes over the Blue Mountains; through Penrith to Katoomba and then toLithgow, or through Windsor to Bell and then to Lithgow. If taking the Bell road head north-west out of Sydney through Baulkham Hills and the Windsor Road. To take the Katoombaroad head west out of Sydney through Parramatta and then on to the freeway to Penrith. After

Chapter 1: Introducing the Parkes Observatory 5

Lithgow the route is through Bathurst, Orange, Manildra and then Parkes. It is essential tohave a current drivers license acceptable in NSW to allow you to drive the CSIRO cars whichare used at the Observatory. Note that NSW law requires all drivers to carry a valid driver’slicense in English, or with an approved English translation (obtainable through the AustralianEmbassy before travelling). This will enable you to drive the site vehicles from the observersquarters to the 64-metre telescope (one kilometre each way). Bicycles provide an alternativemeans of transport. Traffic in Australia uses the left-hand side of the road. The limit on drinkdriving is 0.05.

1.3 Other Information

Other information on transport can be found at the ATNF website1.

1.4 Observers Quarters

For official observatory visitors, we have nine single rooms and two double rooms, two bathroomseach with bath, shower and toilet, a dining room, a conference room and a lounge room. Quartersstaff are present from 08:00 to 16:30 weekdays.

The cost of accommodation at the Parkes Observatory Quarters is shown in the table below.

per room, per night: $64.10 breakfast included

lunch (12.30-13.30): $13.20

dinner: $19.80

full board, per day: $97.10

4 bedroom unit: $84.70 nightly rate, minimum stay three nights or $593 weekly.

All prices are 10% GST inclusive. Students receive a 50% discount on room and meal prices.Children under 12 are given a 50% discount on meals.

The unit can be used as a self contained unit, but meals from the Quarters kitchen maybe requested (prices as above). The unit has five beds and a self-contained kitchen, for thosepreferring to do their own catering.

There are also numerous motels in the township of Parkes. On arrival, check in at the quartersand leave your luggage in the room assigned to you. If you are not staying at the quarters,check in at the administration desk (in the Administration Building). The administration deskis staffed from 8:00 to 16:30 Mondays to Fridays. If you arrive after staff working hours, contactthe quarters prior to your arrival to obtain your room arrangements or you can find your roomnumber from a schedule in the kitchen.

1.5 Booking Your Accomodation

Official visitors should inform the Observatory of their travel details and accommodation require-ments by filling in the WWW ATNF Reservation Form as soon as possible before travelling,and at least three days in advance of arrival.

1.6 Visitors Centre and The Dish Cafe

The observatory supports a Visitors Centre which is open to educational groups and the publiceach day from 08:30 to 16:15 (except Christmas and Boxing Days). The centre features displaysand interactive exhibits about the telescope and two theatres - The Invisible Universe about thetelescope, astronomy and radio astronomy and the 3D theatre, which has a variety of astronomyrelated 3D shows. Educational materials and souvenirs are available for sale from the centre orthrough their mail order service. Observers and ATNF staff enjoy a 20% discount on most itemsand free entry to the theatres.

1 http://www.atnf.csiro.au/observers/visit/travel visitors.html

6 Parkes Users Guide

The Dish Cafe provides a range of drinks and food with a great view of the telescope.Observers and staff enjoy a 10% discount plus $2.00 per coffee for observers if you bring yourown mug!

For staff: It helps cafe and Visitor Centre staff to know that you’re eligible for a discountif you have some form of identification such as a hard hat. Mor einformation on the VisitorsCenter. and The Dish Cafe can be found by clicking on the links.

1.7 Observatory Contact Details

The observatory can be contacted at the following address:

• Australia Telescope National Facility

• Parkes Observatory

• 473 Telescope Road (or PO BOX 276)

• PARKES NSW 2870

• Australia

• Switch:(02) 6861 1700 [International +61 2 6861 1700]

• Fax: (02) 6861 1730 [International +61 2 6861 1730]

Chapter 2: Planning Your Observations 7

2 Planning Your Observations

2.1 Applying for Observing Time

Proposal forms and submission deadlines can be found here, while current and archived observingschedules can be found here.

Information regarding system capabilities not listed here can be addressed [email protected]

2.2 Radio-Frequency Interference Considerations

An introduction to RFI observed at the observatory and surveys performed is available here.

2.3 Observing Modes

Spectral and continuum-line observations can be performed with all currently-available receiversand back-ends. Possible observing modes include:

• TRACK: Simply track the position for the specified length of time.

• SCAN: The telescope scans from one end to the other at a requested rate.

• MX: The position is tracked in turn by each beam (Multibeam receiver only.)

• MXCAL: Observe a calibrator with each beam in turn (Multibeam receiver only.)

• SPOT: Scan across a source for the purposes of defining pointing offsets and calibrationparameters.

• Equatorial-Horizontal Mixed Scans: Here the telescope can perform AZ-EL "spider" scans(..., -90, -45, 0, 45, 90, ...) referenced to an RA/DEC position. The scans are conductedalong the Great Circle passing through the source. Mapping an area in AZ-EL centred onthe RA/DEC position is also possible.

There are three methods of switching. Not all methods are available with all receivers/back-ends.

• Position Switching: Using the TRACK mode, the telescope alternates between an on andoff-source position where the latter is assumed to be free of line emission. This mode istypically used for observing molecular lines such as Ammonia and Maser lines. Point-by-point mapping can be done with this mode.

• Frequency Switching: During an observation, the observing frequency alternates betweena pair of frequencies. Both slow and fast modes are available. This mode is often used forSCANNING on-the-fly observations which look at spatially-extended emission such as wide(Galactic HI) and narrow hydrogen recombination spectral lines. The second (switched)frequency is used as a reference spectrum which aids in data reduction and can increasesignal to noise by at least a factor of two over the position-switching mode. The totalfrequency switch can be either “in-band” or “out-of-band”. The size of the throw dependson the nature of the emission you are seeking. The throw should be at least 2-3 times thewidth of the widest profile you might expect in your data. You should also be aware ifyou are observing multiple spectral lines within a bandpass, some of the data processingapplications such as livedata produce ghosts which may overlap and be confused with realspectra. For estimating the size of the required throw, for wide Galactic Hi observations, afrequency throw of about 3 MHz with an 8 MHz bandwidth is the norm.

• Beam Switching This is currently restricted to Multibeam receivers (MX mode). Theposition is tracked in turn by each required beam of the Multibeam system. This mode isideal for observing sources such as single galaxies (or multiple if all lie within the beam).When a beam is not looking at the source we assume it’s collecting a reference spectrumfrom blank sky. The prior and following scans are used to form the bandpass calibration.

8 Parkes Users Guide

2.4 Preparing Schedule Files

For the majority of programs, you will be using the Telescope Control Software (tcs). The tcsgraphical user interface (tcs GUI) is written in Glish/Tk and runs on a Solaris workstation. Aglish client runs on the same host as the tcs GUI which serves as a communications channelbetween the tcs GUI and the (Linux) controller.

There are two ways to use tcs. The first is to select observing parameters from the tcs GUIvia widgets and entry boxes. The second (and recommended) is to use schedule files which areloaded values become the default parameters on the tcs GUI. Until accustomed with the system,first-time users are strongly urged to use schedule files. Detailed information on keywords usedin schedule files and examples can be found in the tcs documentation

Some of the main items to worry about in your schedule file(s) are as follows, but note thisis not an exhaustive list!

• Project I.D.: PXXX (i.e. your project code)

• Project Name: as desired

• Correlator configuration, i.e., DFB3 "sdfb3 256 8192" for a spectral mode 256 MHz BWand 8192 channels or "sdfb3 tb16 64 512" for a time-binning mode 16-bins, 64 MHz BWand 512 channels

• receiver: your receiver

• Cycle time: e.g. 8 [sec]

• Time bins: 1 (spectral mode); number of time bins (time-binning). E.g. 16

• Doppler tracking

• feed angle: normally 0.0 (from -90 to 90)

• Parallactic angle tracking: ENABLED/DISABLED

• Frequency: central frequency

• Bandwidth [MHz]

• #channels

• Polarization products: some examples: 2 => for spectral mode, total intensity only. 3 =>for full Stokes parameters (typically in time-binning).

• frequency switching: SIGNAL (no freq sw), SLOW (for freq sw) then set the frequencyoffset [MHz]

• Tsys recording: add "enable becc" to your schedule (or type it in the TCS "Command"field).

There are online utilities to assist in the preparation of schedules for position–switching,beam–switching, tracking (with or without frequency switching) and on-the-fly mapping. Thesecan be found on the Parkes utilities page. Note that these tools DO NOT cater for Pulsarobservations.

2.5 Sensitivity

When preparing your observing proposal, you are required to estimate the expected bright-ness and sensitivity of your source for your particular Correlator/receiver combinations. Forspectral-line observations, sensitivity per bandwidth channel can be estimated from the follow-ing equations of line brightness and line flux respectively:

Trms(mK) ∼ Tsys√npol BW

chan δT

Srms(mJybeam

) ∼ TrmsGηb

Chapter 2: Planning Your Observations 9

In the above, G is the main–beam gain (Jy/K) for a receiver defined from Table 2.1, npolis the number of polarisations1, BW is the bandwidth [MHz], nchan is the number of channelsand δT is the on-source integration time in seconds. ηb is the beam efficiency factor: Ωmb

Ωtot= 0.7.

For continuum, we need to calculate the sensitivity over the whole bandwidth. The continuumline brightness and line flux respectively become:

Trms(mK) ∼ Tsys√npolBWδT

Srms(mJybeam

) ∼ TrmsGηb

For both the line and continuum flux, the source is assumed to fill the main beam whichhas efficiency Ωmb

Ωtot= 0.7. 1-sigma theoretical RMS noise estimates for line and continuum

observations can be estimated by using the on-line Sensitivity Calculator.

2.6 Parkes Receiver Fleet

Click on the receiver links below in Table 2.1 to show information regarding receiver informationsuch as characterization tests, gain-elevation curves and pointing accuracy. Please note thisinformation is being uploaded when receivers are installed and may not be available at thepresent time.

1 We assume an average of two independent polarisation channels.

10 Parkes Users Guide

----------------------------------------------------------------------------

Receiver Band Range Diameter FWHP Tsys Sen[a] Pols[b] Bandw

[cm] [GHz] [m] [’] [K] [Jy/K] [MHz]

----------------------------------------------------------------------------

1050cm

50 0.70-0.764 64 30 40 1.7? 2xL 64

10 2.60-3.600 64 6.3 35 1.1 2xL 1000

MB20

21 1.23-1.53 64 14.2 28 1.1 26xL 300

H-OH

21/18 1.2-1.8 64 14.8 25 1.2 2xL 500

GALILEO

13 2.20-2.5 64 8.9 20 1.5 2xC 300

2.15-2.27 64 9.2? 20? 2.1? 2xC 120

2.29-2.3 64 9.2? 19? 1.4? 2xC 10

AT S-BAND[c]

13 2.2-2.5 64 9.2? 79? 1.9? 2xL 300

AT C-BAND[c]

6 4.5-5.1 64 4.5 50 1.3 C 500

AT X-BAND[c]

3 8.1.8.7 64 2.5 140? 1.1? 2xL|C 500

3/13 8.1-8.7 64 2.5 140? 1.1? 2xL 500

2.2-2.5 64 9.2? 79? 1.9? C 300

METH6

5.9-6.8 64 3.45 55 1.4 2xC 300

MARS[d]

3 8.0-8.9 55 2.45 30 1.7 2xC 500

KU-BAND

2.2 12.0-15.0 64 1.9 150? 1.6? 2xL 500

K-BAND

1.3 21.0-24.0 55 1.3 105? 2.0? 2xC 500

13MM

1.3 16.0-26.0 55 1-1.4 95 2.0 2xL 1000

21.0-22.3 2xC 1000

---------------------------------------------------------------------------

[a] Includes typical atmospheric, ground and galactic contribution at Zenith.

[b] L = linear, C = circular, NB = narrowband.

[c] Dual linear feeds at S,C,X bands, lambda/4 plates avaliable for band centers.

[d] Full bandwidth by special arrangement.

A ’?’ indicates yet to be confirmed, use with caution.

Table 2.1: Parameters for the Parkes receiver fleet.

2.6.1 Receiver Calibration Signal

Most of the Parkes receivers allow injection of a calibration noise signal into the receiver waveg-uide ahead of the ortho-mode transducer (OMT). This is generally a more satisfactory methodthan injecting after the OMT or after the LNAs as these elements can then be modelled usingthe calibration signal.

The calibration signal is generally injected through a coupler in the circular waveguide ori-ented at 45 degrees to the linear probes of the OMT. Thus the cal can be closely represented bya 100% linearly-polarised signal with an accurately known feed angle.

Chapter 2: Planning Your Observations 11

The amplitude of the cal signal is adjustable by inserting or removing fixed attenuatorsbetween the noise source and the coupler. Changing the level requires access to the receiverin the focus cabin and takes of order 30 minutes. The cal can be switched on or off remotelyas required, using an observer-selectable waveform. Typically the cal is run as a continuouslow-level NAR (Noise-Adding Radiometer) with the cal level approximately 10% of Tsys, for atime-averaged increase of 5%. The frequency of the switching signal is typically between a fewHz and 500Hz.

The H-OH receiver has an optional quarter-wave plate which can be inserted in the circularwaveguide between the feedhorn and the OMT to achieve circular polarisation on the sky. Thequarter-wave plate is inserted before the cal injection so in this case the cal signal resembles a100% circularly-polarised signal on the sky but the cal signal alone cannot be used to model theprecise properties of the quarter-wave plate.

The 13MM receiver also has an optional quarter-wave plate used with the narrow-band VLBIfeed covering the 22 GHz water transition. As with the H-OH receiver, the cal injection occursafter the polariser (between the polariser and the OMT).

The MARS (8.4 GHz; X–band) receiver has a built-in (non-removable) waveguide circularpolariser also with cal injection between the polariser and OMT.

The C-band and X-band receivers in the AT Multi-band receivers also have quarter-waveplates ahead of the cal injection.

The GALILEO receiver has cal injection into circular waveguide but uses a circularly-polarised OMT (cal signal resembles 100% linear on sky).

The 50cm receiver in the 1050CM package injects a cal signal using a directional couplerafter each LNA (strictly, after the 4-port hybrid used to combine the signal from each pair ofopposing probes and LNAs). A splitter is used to generate two identical cal signals from thesame noise source.

2.7 Conversion System

The Parkes Conversion System (PCS) is summarised as follows:

• It is possible to observe simultaneously two widely separated spectral line features within areceiver passband. Alternatively, in the case of a dual band receiver (eg. The S-X receivercovering 2.2-2.5 GHz and 8.1-8,7 GHz), spectral line or broadband noise observations maybe made simultaneously for each of the bands.

• Dual polarisation is available for each of the observing frequencies, necessitating a total offour conversion channels. However, as the modules are paired, only two independent LocalOscillator (LO) systems are needed.

• The input bands are 300-750 MHz (UHF-band), 1.2-1.8 GHz (L-band), 2.2-3.6 GHz (S-band), and 4.5-6.1 GHz (C-band). Observations outside these bands, for example at K-band(22 GHz) are accommodated using an extra conversion on the receiver package or using LOsin the focus cabin and/or upstairs control room.

• Wherever possible signals generated by the local oscillator system should not fall within anysignal or intermediate frequency (IF) bands to reduce the incidence of internally generatedinterference [2]. Unfortunately, due to the very wide S-band (2.2-3.6 GHz), one of the LOfrequencies may fall inside the band for some observing frequencies.

• Frequency switching may be used for observations of a single spectral line. For C-bandinputs, frequency switching is available for two spectral lines simultaneously.

• In order to ensure the conversion system is capable of supporting simultaneous use of DigitalFilter Banks, Multibeam Correlator, BPSR, APSR, Pulsar Analogue Filter Banks, andCASPSR, a number of buffered outputs for each output bandwidth have been provided.Each of the 4 channels has 4 of 64 MHz, 3 of 128 MHz, 3 of 256 MHz, and 2 of 900

12 Parkes Users Guide

MHz bandwidth (BW) outputs available. One complete set of outputs for each channel(64, 128, 256, and 900 MHz BW) have been provided at the front of the conversion rack.The remaining system outputs are cabled to bulkhead connectors in the rear of the rackfor permanent connection to the DAS and an RF Switch Matrix. The latter operates thestandard connections from the conversion system to the several correlators/backend units.It is operated by software and in most cases the connection Conversion System outputto backend is automatically instated by the observation control software (TCS: TelescopeControl System).

An in–depth discussion of the PCS (including block diagrams) is available here.

2.8 Signal Path

An overall outline of the Parkes observing system is shown in Figure 2.1.

.

Figure 2.1: Overview of the Parkes observing system.

Single-beam spectral–line observations have back-end options using 4, 8 or 64 MHz bandpasscapabilities of the 2–bit Multibeam correlator, or patching in an ATCA–style bandpass filter toprovide 16 or 32 MHz bandpass capability. Wider bandwidths (>64 MHz) are available using the8–bit Digital Filterbanks (DFB3/DFB4), but it is also possible to achieve smaller bandpasseswith DFB3/DFB4 (ie., 8, 16, 32 MHz).

For Pulsar observations, it is possible to switch simultaneously record data on several backends at once.

Chapter 2: Planning Your Observations 13

2.9 Standing Wave Reduction

For Parkes, characteristic small-scale ripple with periodicity ∼5.7 MHz arises from multiplereflections in the 26m space between the vertex at one end, and the focus and/or undersideof the focus cabin at the other. Figure 2.2 shows 22 GHz observations of a strong Ammoniasource, G316.819, showing strong (1,1) and (2,2) transitions for 4 minutes (exact multiple of 60seconds). The two observations were taken one after the other, the first (upper panel) with nospecial ’de-rippling’ measures, the lower taken in a mode where the receiver is moved cyclicallyup and down in the translator Y-axis to ’smear out’ the ripple with amplitude 6.3mm peak-to-peak (λ/2) and period 60 seconds. This technique is available for use with higher-frequencyreceivers only and proposers should contact Parkes Operations ([email protected])before submitting proposals.

Figure 2.2: Upper panel showing characteristic 5.7 MHz standing wave interference withlower panel showing a cleaner spectrum obtained with receiver cycling.

2.10 Correlators

A number of correlators/backend units are available:

• DFB3: spectral line, pulsar, continuum and polarimetry, for up to two IFs dual polarizationobservations

• DFB4: spectral line, pulsar, continuum and polarimetry, for one IF dual polarization ob-servations

• Multibeam Correlator: multi beam correlator for spectral line observations for up to 14 IFsdual polarization.

• BPSR: multi beam digital backend for pulsar observations (up to 13 IFs dual polarization).

• APSR: coherent dedispersion recorder for pulsar observations (one IF dual polarization).

• AFB: Analogue Filter Banks, analogue multibeam backend for pulsar observations (up to13 IFs).

Please check the Parkes Correlator Guide for information on capabilities or [email protected] to ascertain requirements.

2.11 Dish Surface Quality

A 4 GHz holographic survey of the dish surface was performed prior to the 1995 upgrade of thefocus cabin. Other surveys at 3.95 GHz (June 1996) and 12.75 GHz (July 1996) were performed

14 Parkes Users Guide

after the installation of the new focus cabin. Details of the readjustment of the inner 44m ofthe Parkes reflector in December 1996 is also also available here. As part of the NASA Marstracking contract in 2003/2004, the Parkes Telescope’s surface was upgraded to make it morereflective and sensitive at X-band (∼ 8.5 GHz). The surface upgrade improved the telescope’sperformance by about 1 dB (or 25%). A technical guide is available.

Chapter 3: Observer Training & Safety 15

3 Observer Training & Safety

3.1 Introduction

The Parkes RadioTelescope is a major resource for both Australian and international astronomy.Like any major astronomical facility it is a complex and costly instrument and may present apotentially hazardous environment. Unlike many other facilities around the world, the ParkesObservatory DOES NOT employ telescope operators and as such astronomers must be presentto perform observations. The Parkes Observatory is also different in that these observers sitwithin the telescope structure and not in a control room located away from the telescope.

There are two types of training at Parkes. The first is the Safety and Environment Induction(HSE) which can be done online (click above link) and is valid for one year. A face-to-face induc-tion is also done when you arrive at the site. The second type of training is the Observer trainingcourse. At the completion of the observer training you become a LICENSED OPERATOR andyour ’ticket’ remains valid for 24 months until a refresher is required.

People who have not received the HSE induction AND Observer training are not permittedto use the telescope.

The purpose of this chapter is to outline what will be taught during the Observer trainingCourse. Words in CAPITALS have special meaning and defined either in-text or in Section 3.5[Definitions], page 20.

3.2 Duties of an LICENSED OPERATOR

In general, a person wishing to become a LICENSED OPERATOR:

• Must thoroughly understand the One in the Tower mode of operation (see below.)

• Must have a good, general knowledge of how servo, me, pkdesk and other observingsoftware interact.

• Must be able to monitor the status of the dish using displays such as showtel, servo, me,pkdesk, pkmc etc.

• Must understand the restrictions on operating the telescope under certain abnormal condi-tions (such as those of high wind and power black-outs).

• Must be able to place the telescope in observing mode from a wind-park or stowed stateand re-stow if required.

• Must thoroughly understand and be able to operate the SAFETY SYSTEM when observingand what to do in a NON-STANDARD or EMERGENCY SITUATION.

• Must ensure the SAFETY SYSTEM is operational at the start of, and throughout, theirshift.

• Must be able to diagnose simple and common faults accurately.

• Must have an understanding of general procedures such as using the CLEARCALL andhow/when to contact the ROSTERED CALL-OUT PERSON.

The following sections outline specifics in more detail.

3.2.1 One in the Tower Rule

To use the Parkes RadioTelescope requires at least two people. One, called the LICENSEDOPERATOR, is responsible for the minute-to-minute movement, stowing/unstowing and safetyof the telescope. The second person is called the DESIGNATED CONTACT PERSON (orDCP) and is primarily responsible for the safety of the OPERATOR. The OPERATOR mustbe present in the TOWER when the Telescope is in use. The DCP must be contactable by theOPERATOR at all times. For the majority of the time, the OPERATOR is in the TOWER and

16 Parkes Users Guide

the DCP is located in the Observer’s Quarters building. This describes the One in the TOWERrule.

Contact between the OPERATOR and DCP is maintained primarily through a special tele-phone and alarm system. Under normal operating conditions the OPERATOR must press agreen reset button, at intervals approximately 15 minutes in length. If this button is not reg-ularly pressed, then a series of increasingly far-ranging tones are heard. The first is in theTOWER, so as to alert the OPERATOR. The second level of alarm alerts the DCP. The thirdlevel automatically alerts staff that live both on and off the site.

Please note the following:

• If there is more than one LICENSED OPERATOR in the TOWER, there is no requirementfor a CONTACTABLE DCP at the Quarters.

• If there is no–one to act as DCP, you are not permitted to observe.

3.2.2 SAFETY TIMER

The SAFETY TIMER is an electronic timer which is automatically activated whenever thetelescope is in operation and, optionally, at other times. This timer includes a clock with adisplay of elapsed time, controls multiple alarm systems, and has a number of push-buttons(some of which are replicated throughout the control rooms). The purpose of this timer is tomonitor a continuous and effective presence in the TOWER in order to maximise the safety ofthe OPERATOR(S) and the telescope.

The SAFETY TIMER cannot be disabled while the telescope is in operation. An interlockdisables the drive system if power is removed from the SAFETY TIMER.

In order to have confidence that the SAFETY SYSTEM is able to work effectively, the OP-ERATOR and DCP should check that both communication paths between them are functional.To this end a simple test of the DCP phone should be carried out whenever a DCP commencesduty, or changes location during a shift.

3.2.2.1 Timer Display and States

Figure 3.1: The Safety Timer.

The SAFETY TIMER display is shown in [Figure 3.1], page 16. It shows the amount of time(in minutes and seconds) which has elapsed since the timer was last reset.

The clock starts counting from 00:00:00 when it is initially activated (MCP powered ON)and whenever it is RESET. It will continue to count towards its maximum count (99:99:99)as it passes through the NORMAL, WARNING, CONTACT and ALARM states. These areexplained below.

• 00:00:00 - NORMAL

The clock starts counting from 00:00:00 with the SAFETY TIMER in the NORMAL state,when it is initially activated andwhenever it is RESET either manually or by the infrareddetector (IRD) in the CONRTOL ROOM.

• 14:40 - WARNING

At 14 minutes, 40 seconds, the SAFETY TIMER enters the WARNING state. At thistime a warning tone begins to sound in the TOWER to alert the OPERATOR that fifteen

Chapter 3: Observer Training & Safety 17

minutes have elapsed since the RESET button was last pressed and that only ten minutesremain before the alarm on the DCP phone will be rung to summon the DCP.

The SAFETY TIMER will emit a short tone every 30 seconds. If this is ignored, the tonewill continue until the elapsed time reaches the 25 minute mark. The OPERATOR shouldpress the RESET button as soon as possible and then continue with observing.

• 25:00 - CONTACT

At 25 minutes the SAFETY TIMER enters the CONTACT state and the CONTACT BELLbegins ringing continuously. The DCP must respond to this as described in Response tothe DCP Contact Bell. The clock continues to count up.

Note this stage can also be reached directly by pressing the YELLOW Contact button onthe SAFETY TIMER panel.

• 35:00 - ALARM

At 35 minutes the timer enters the ALARM state, the DCP phone alarm changes to beingrung for 1 second each alternate second, and, at 35:10, the off-site security company isalerted. The SAFETY TIMER will then remain in the ALARM state and the clock willcontinue to increment towards a maximum of 99:99:99 with the display showing how muchtime has elapsed since the last RESET.

More information on what occurs after this state is entered is located in Section 3.2.6[Emergency Situations], page 18 below.

3.2.2.2 Timer Controls

• Reset Button (Green) and the INFRA-RED DETECTOR (IRD)

The green RESET buttons and IRD are used to set the elapsed time counter back to zero.They are connected in such a manner as to preclude continuous resetting of the counter,should they be jammed in a pressed state. Its purpose is to indicate that a responsibleperson is present in the TOWER and is accepting responsibility for the safe operation ofthe telescope.

We recommend that the observer press the reset button regularly (without waiting for the15 minute warning). It may be pressed at any time to return the SAFETY TIMER to theNORMAL state. With movement is detected, the infrared detector switches on and remainson for 40 seconds; if it continues to detect movement, it stays on for another 40 secondsuntil the last detection. As long as movement is detected within a period of 4 minutes, theSAFETY TIMER will automatically reset to the NORMAL state (00:00:00);

• Contact Button (Yellow)

The yellow CONTACT button may be used to ring the DCP phone alarm in order to getin touch, urgently, with the DCP. However, in general, a telephone call is the preferablemethod. Pressing this button causes the SAFETY TIMER to turn on the DCP phonealarm.

• Alarm Button (Red)

When pressed, alerts the external security company. Pressing this button causes theSAFETY TIMER to immediately enter the ALARM state (see above).

There is a 10-second "period-of-grace" during which time pressing the green button bothRESETs the timer and cancels the SAFETEY TIMER going into the ALARM state. (Thisis in case the red button gets pressed accidentally.)

More information can be found in Section 3.2.6 [Emergency Situations], page 18.

• Auto(normal) Indicator (Green)

This indicator, when illuminated, shows that the telescope is in operation and that theSAFETY TIMER has been automatically enabled.

18 Parkes Users Guide

• Optional Enable Button (Blue)

If the telescope is not in operation, pressing the blue button for two seconds will cause itto light and will enable the timer to provide optional protection for a person working alonein the TOWER. Pressing this button when the telescope is in operation has no effect.

• Disable(off) Button (Orange)

If the telescope is not in operation, pressing the orange button will cause it to light andwill disable the optional protection mode. Pressing this button when the telescope is inoperation has no effect.

3.2.3 Use of Clear Call Announcements

The OPERATOR will use the CLEARCALL to warn of an impending movement of the tele-scope whenever it has been stopped in a position which allows for personal access (i.e., aftera maintenance or reconfiguration period). This includes, but is not limited to, movement inZenith away from either the Zenith or horizon limits, and movement in Azimuth only while atthe Zenith.

3.2.4 Absences from an Operating Telescope

The telescope should not be left unattended without it being STOWED. Exceptions includevery short periods of absence, not exceeding 5 minutes in order to perform such functions aschecking the weather from ground level outside the TOWER.

3.2.5 Non-standard situations

If something happens which prevents observing from taking place, a NON-STANDARD SITU-ATION may have developed. If it is not an emergency, the ROSTERED CALL-OUT PERSONshould be the first person contacted (unless, of course, the OPERATOR and DCP have boththe necessary expertise and authorisation to remedy the situation).

If the ROSTERED CALL-OUT PERSON (or, subsequently, another appropriately qualifiedmember of the Parkes Observatory staff) is telephoned, the OPERATOR may be given instruc-tions over the phone as to how to perform any necessary NON-STANDARD PROCEDURES.

3.2.6 Emergency Situations

If the SAFETY TIMER ALARM state is triggerred by one of the following;

• the SAFETY TIMER is allowed to count up to 35 minutes and 10 seconds, OR

• the red ALARM button on the SAFETY TIMER is pressed;

a flag will be raised in an alarm system that is monitored 24/7 by an external securitycompany. Their operator will follow a procedure of making phone calls to appropriate places orpeople, and possibly the Police to bring help to what must then be an emergency. As of June2010, this list, in order of contact is:

• Tower

• Quarters Kitchen

• ROSTERED CALL-OUT Mobile

• Matthew McFarland

• Malcolm Smith

• Brett Preisig

The last four listed above are EMERGENCY CALL-OUT PERSONS.

If the security company operator is unable to contact someone, the next place/person listedwill be contacted and so on until a contact has been reached. If no contact is available, thePolice will be notified.

Chapter 3: Observer Training & Safety 19

If someone in the Tower or Quarters Kitchen answers, they will be asked to clarify thesituation. If there is no need to progress to the next contact as shown above, the securityoperator will ask for a password. This password shall be told to people when the receive theirTelescope Operator Training and/or HSE induction. If the correct password is supplied, theoperator will hang up and discontinue contacting people in the list above. If an incorrectpassword is supplied, the security operator will continue calling as per the list above.

Examples of EMEGENCY SITUATIONs are presented below.

3.2.7 Fatigue

The personal safety of OPERATORS, as well as the safety of the telescope equipment, requiresall OPERATORs be mentally alert. People should not continue to be the OPERATOR if theyare too tired to perform their duties correctly. For example, it would be considered inappropriatefor a person to be the OPERATOR for more than 16 hours a day.

In addition, adequate breaks are necessary during long shifts in order to maintain alertness.For this reason, it is strongly recommended that when a shift lasts more than 10 hours, a breakor breaks totalling at least 1 hour be taken.

3.3 Duties of a DESIGNATED CONTACT PERSON (DCP)

The duties of the DCP are less extensive than those of the OPERATOR but are no less impor-tant. In essence, a DCP is responsible for the safety of the OPERATOR. To do this, the DCPmust ensure:

• The SAFETY SYSTEM is operational at the start of their shift that they remain CON-TACTABLE throughout their shift.

• They understand what they must do in the event of being called by the OPERATOR.

• They understand and can perform duties in the event of an EMERGENCY SITUATIONdeveloping.

3.3.1 Response to the DCP Contact Bell

Via the DCP phone alarm, the DCP is alerted to an urgent problem and must telephone theOPERATOR (ext. 1755 or 1754), immediately, to find out what the problem is. If the OPERA-TOR answers, a conversation will take place. During this it will be determined what assistanceis required. (Note, the time delay push-button may be pressed to silence the bell for a fewminutes while the call is made; however, unless someone in the TOWER responds, and resetsthe SAFETY TIMER, the bell will sound again after the time delay.) If no answer is obtainedwithin a reasonable time (12 rings is adequate) the DCP must assume that the OPERATORis in some way incapacitated and must proceed immediately, but carefully, to the TOWER toinvestigate. If, upon investigation, it is determined that there is a real emergency in progress,the red ALARM button should be pressed immediately – do not press the green RESET button.However, if you are too busy dealing with the emergency to be able to get to the buttons, theSAFETY TIMER, will automatically trigger an alarm to an external security company whenthe 35 minute mark is reached.

3.3.2 Response of EMERGENCY CALL-OUT to EMERGENCYALARM

This section is addressed, primarily, to the EMERGENCY CALL-OUT PERSON but is includedhere to describe what response can be expected to an ALARM call. As an EMERGENCYCALL-OUT PERSON, when you receive a call from Chubb Electronic Security in Bathurst andwill be informed that there is an EMERGENCY SITUATION at the telescope. Please refer toEMERGENCY CALL-OUT below.

20 Parkes Users Guide

3.4 Questions and Answers

The following questions and answers are given to provide some practical examples of situationswhich might arise under the One in the Tower method of observing.

Q1. It is midnight but observing has not yet started and the Telescope is STOWED. Anastronomer, who is a LICENSED OPERATOR, and the DCP have just been talking together atthe Quarters. The astronomer drives alone to the TOWER and enters the CONRTOL ROOM.What procedures should be followed first?

A1. The astronomer should phone the DCP as soon as possible and test the SAFETYSYSTEM to ensure that it is working.

Q2. A DCP, asleep at the Quarters, is awoken by the CONTACT BELL. The person phonesthe TOWER but obtains no response. What should be done?

A2. This may be an EMERGENCY SITUATION. The DCP should go immediately, butcarefully, to the TOWER and ascertain why the OPERATOR did not answer.

For the following questions, the situation is as follows: an astronomer, who is a LICENSEDOPERATOR, is operating the Telescope under the One in the Tower Rule at around 3am on aSaturday morning. The DCP is asleep in a bedroom at the Quarters.

Q3. Because all the objects have set, the astronomer decides to stow the dish and go to bed.What procedure should be followed?

A3. The astronomer may proceed to STOW the dish, but should pay particular care if out onthe Azimuth track. It is not necessary to wake the DCP for this procedure. When the telescopeis STOWED the astronomer may leave the TOWER if so desired.

Q4. The astronomer decides to check the weather from just outside the Telescope TOWERso as to have a clear look at the sky. May the astronomer do this? And, if so, what procedureshould be followed?

A4. The astronomer may perform this operation without calling the DCP provided that theastronomer is absent from the TOWER for no longer than 5 minutes.

Q5. The astronomer suddenly feels extremely ill and in danger of collapsing. What shouldbe done?

A5. This is an EMERGENCY/ALARM situation: the astronomer should press the REDALARM BUTTON immediately. It may save time if the DCP is phoned.

Q6. The astronomer notices that the wind has risen rapidly to 45 km/hr and the dish beginsto stow automatically. At this moment, there is a power black-out and the diesel generatordoes not start. The dish drive stops with the dish at 55 degrees Zenith angle. What should theastronomer do?

A6. This is an EMERGENCY SITUATION. The OPERATOR should contact the Call-out person immediately, followed by one of the following: Mal Smith, Matt McFarland, BrettPreisig.

Q7. Observing is proceeding normally and the weather conditions are fine with little or nowind. Suddenly the dish drive becomes disabled and the astronomer, after some time, diagnoses(correctly, as it later turns out) that there is an electrical drive system problem. What shouldbe done?

A7. This is a NON-STANDARD, but not EMERGENCY SITUATION. The person shouldcall the ROSTERED CALL-OUT PERSON. The DCP need not be disturbed.

3.5 Definitions

• CLEARCALL

The CLEARCALL is a public address system used to communicate with personel in variousparts of the telescope structure. In particular, it is required to be used to warn of impending

Chapter 3: Observer Training & Safety 21

movements of the telescope whenever it has been stopped in a position which allows forpersonal access. There are CLEARCALL microphones in the first and second level controlrooms. Throughout the telescope structure there are many CLEARCALL stations which alloperate in parallel, and have either hand-held or wall-mounted microphone/speaker units.

• CONTACTABLE

A person is deemed to be CONTACTABLE by the telescope OPERATOR if that personcan:

• reach the TOWER within a few minutes if required AND

• hear the SAFETY TIMER alarm bell AND

• ring, or be rung by the OPERATOR. This means informing the telescope OPERATORof their location and phone number.

The alarm on the DCP phone is activated when the SAFETY TIMER alarm bell reaches25 minutes. In a way, it is a portable SAFETY TIMER alarm bell, but it is limited as towhere it can be used. See the definition of the DCP PHONE for a list of such areas.

Permanently-connected SAFETY TIMER alarm bells are located at the following locations:

• on the first floor of the TOWER

• in the foyer of the Quarters

• in the foyer of the Administration building ("Opera House")

• in the meal room of the Woolshed

Therefore to be CONTACTABLE imples you are located either at the Quarters, the on-sitehouses, the Administration building, the Woolshed or the TOWER. It does not include the’trams’ adjacent to the Administration building (the "Olympic Village") or the VisitorsCentre as the staff there cannot be asked to act as a DCP.

• DESIGNATED CONTACT PERSON (DCP)

Person responsible for the safety of the OPERATOR. They may, or may not, be presentin the TOWER. Usually DCPs have undertaken the Observer Training course and mustremain CONTACTABLE by the OPERATOR for the duration of their rostered period ofresponsibility.

• DESIGNATED CONTACT PERSON PHONE

The DCP phone is an assembly comprising a PABX extension telephone, alarm, and apneumatic time-delay push-button. Portable DCP PHONES are confined to the Quartersbedrooms, Quarters dinning room, Quarters lounge room and the three on-site houses,including the flat. The pneumatic time-delay push-button is provided for temporarily si-lencing the bell while the DCP makes a telephone call to the TOWER.

• EMERGENCY CALL-OUT PERSON

An EMERGENCY CALL-OUT PERSON has their home/mobile phone number listed withan external security company. In the abnormal event of an EMERGENCY SITUATIONdeveloping, all persons listed will be called, in sequence, until soneone is contacted. Theywill be informed by the security company there is an EMERGENCY SITUATION at thetelescope.

This section is addressed, primarily, to the EMERGENCY CALL-OUT PERSON but isincluded here to describe what response can be expected to an ALARM call. As an EMER-GENCY CALL-OUT PERSON, when you receive a call from Chubb Electronic Security inBathurst and will be informed that there is an EMERGENCY SITUATION at the telescope.

If you receive a call from the monitoring centre, they may ask for a pass phrase. Youshould know what this is. If you have been contacted on one of the nominated premisesphone numbers, after giving the pass-phrase, you may instruct the call-centre to refrain

22 Parkes Users Guide

from calling further numbers if appropriate. If you receive a call as one of the contacts, youmust note which system and which specific alarm has been raised, and then take steps tofind the cause of the alarm and attend to it.

Some examples:

• The Lone employee safety timer alarm indicates that the safety timer has timed out,and that the DCP has been alerted for 10 minutes yet has not reset the timer, -something is wrong.

• The Lone employee Observer’s manual alarm indicates that someone in one of thecontrol rooms has pressed the Safety timer red Alarm Button and they need you onsite as soon as possible.

• Any of the contact buttons. (we usually call them duress buttons) alarms need to betreated with caution as they may have been prompted by a hold-up or fear of violence.If related to the Visitor’s Centre, then you should be aware that the Police will be ontheir way anyway. If related to the quarters kitchen, then they will not (unless no-oneis contactable). In either case you should try and contact the source of the alarm beforedeciding to walk through the door.

Don’t put yourself in danger, if in doubt call the Police.

In all of these cases, avoid going to site without letting someone know you are doing so!

• EMERGENCY SITUATION

An EMERGENCY SITUATION is one which poses an immediate threat to the safety ofeither an OPERATOR and/or the telescope.

• LICENSED OPERATOR

LICENSED OPERATORs are persons who have received Observer Training within the last24 months and are sufficiently responsible and qualified to be permitted to operate thetelescope.

• NON-STANDARD SITUATION/PROCEDURE

A NON-STANDARD SITUATION is a situation in which observing is not possible, butwhich does not pose an immediate threat to either the OPERATOR(s) or the telescope.NON-STANDARD PROCEDUREs are usually required in order to remedy such a situation,and would normally necessitate the contacting of the ROSTERED CALL-OUT PERSON.

• ROSTERED CALL-OUT PERSON

A member the Parkes Observatory staff who has technical competence and is rostered tobe available to assist in a NON-STANDARD SITUATION. They must be a LICENSEDOPERATOR. This person may be contacted by calling a mobile phone short-form code633 on any telephone extension within the observatory, They will then ascertain what theproblem is, and either give advice as to how to fix it, come to the observatory to makerepairs, or summon a third person (who has greater expertise in the situation) to do so.

• STOWED

The telescope is deemed to be STOWED whenever it is On-Stop with the Zenith LockingPin IN and with the Azimuth Jacks either disabled or in the STOWED position, whetheror not the control-system is activated. The power to the MCP is turned off so as to disablethe SAFETY TIMER

• STOWING

NORMAL STOWING is the procedure of moving the telescope to its Zenith Stop under thecontrol of the Manual Control Panel (MCP), driving the Locking Pin IN, and either disablingthe Azimuth drives (recommended) or placing the structure On Jacks. The completion ofthe placement of the structure On Jacks, by going to the Azimuth track and moving thejack handles to the STOWED position, does not require a second person to be notified.

Chapter 3: Observer Training & Safety 23

• TOWER

The TOWER is defined to be the Ground, First and Second Floors within the telescopebuilding. This definition extends to the landing only, outside the CONRTOL ROOM, aslong as the access door remains open. The stairway outside the CONRTOL ROOM, theAzimuth track, the centre column spiral stairway, and all other portions of the telescopestructure above the Second Floor are specifically excluded from this definition.

• UNSTOWING

NORMAL UN-STOWING is the procedure of driving the Pin OUT, moving the dish out ofthe Zenith limit under the control of the Manual Control Panel (MCP), and either enablingthe Azimuth drives or taking the structure off jacks. This procedure requires the use ofthe CLEARCALL to warn of the impending movement The completion of the taking ofthe structure off jacks, by going to the Azimuth track and moving the jack handles to theFREE position, does not require a second person to be notified.

Chapter 4: Observing 25

4 Observing

4.1 Current Issues

For details on current issues affecting observing, please see the local wiki page, located here.

4.2 The Call–out person

Should any problem arise after bussiness hours (4:30PM - 08:00AM) or on weekends, there isalways one member of the technical staff who is the Call–out person. The name of the currentstaff member who is on call–out, together with their phone number, is prominently displayedin the first level control room and on the web1. They can be contacted at any time out ofnormal working hours, in the event of a problem, by calling the abbreviated dialling code 633(no leading 0), which reaches the Call–out mobile phone. A home phone number may also belisted. Call–out personnel will advise of the preferred means of contact. Should they be unableto answer your query by phone, they will come out to the telescope to have a closer look at theproblem, or refer it to another staff member with more expertise in that area.

4.3 The Telescope Hardware

The essential elements of the Parkes RadioTelescope Control System are:

• The 64-m Alt-Azimuth mounted dish

• The Master Equatorial Guidance Telescope

• The Error Detection System

• The Aerial Cabin Focal Platform and Translator

• Control System Computers

• A weather monitoring system

• The Operator Safety System

4.3.1 Master Equatorial Guidance Telescope

The disadvantage of an Alt-Azimuth mounting arises when tracking celestial objects across thesky, because the dish must move in two axes at varying rates, whereas an equatorial systemmoves only in one axis at the constant sidereal rate. When the telescope was designed in the1950s, high speed computers capable of performing the rate calculations were not available. Theproblem was solved by the incorporation of a "Master Equatorial" (or ME) telescope. The MEis situated at the intersection of the Azimuth and Zenith axes and is mounted on a cylindricalcolumn within the tower structure which is physically isolated from the tower. This has theadded advantage that any movement in the tower structure which supports the dish does notaffect the telescope system pointing. The ME tracks the object across the sky, and the dishfollows by minimising the misalignment between it and the telescope by means of an ErrorDetector System.

4.3.2 The Error Detector

The Error Detector is situated under a cylindrical cover in the hub room. It consists of a lowpower He-Ne laser and a circular array of light-detecting diodes. The laser is beamed towards aplane mirror in the top of the ME, and when the dish and the telescope are aligned to within onearc minute, the reflected beam falls on the detector diodes. The offset of the laser beam fromthe centre of the array is read by the servo computer which, when the offset (error) is belowone minute of arc, closes the servo loop, causing the dish to accurately follow the movements of

1 http://www.parkes.atnf.csiro.au/observing/schedules/callout/index.html

26 Parkes Users Guide

the telescope. The dish is then said to be "locked" to the ME. Only then can the telescope bedriven in right ascension or declination. Errors during tracking and scanning are typically lessthan ten seconds of arc.

4.3.3 Dish and me movement limitations

The maximum manual drive rate for the dish in Azimuth is 24 degrees/minute in either direction.The corresponding maximum Zenith rate is 10 degrees/minute downwards or 12 degrees/minuteupwards. The maximum me slew rates rarely are not normally of concern to an operator, butare close to 60 degrees/minute in both hour angle and declination. In general, the maximumsoftware scanning rate is 4 degrees/minute in either Azimuth and/or Zenith.

Figure 4.1: Azimuth Drive Hardware and Software Limits.

In Zenith, the dish is limited to movements between 1.2 < Zenith < 59.5 degrees under normalsoftware operating conditions. At 1.2 degrees, the dish enters its "Zenith limit", within which itcan only be driven at a greatly reduced rate. A similar situation occurs when the dish approchesthe 59.5 degree mark. Similarly, the dish is not free to rotate in Azimuth indefinitely because ofcabling constraints. As shown in Figure 4.1, the "cable-neutral" position is at an Azimuth of 68degrees. There are two hardware (software) limits, one at 294.66 (294.4) degrees and the otherat 206.67 (207.0) degrees, and one is active at any time. The dish may not be driven throughthe active limit. If the dish enters one of these limits, special procedures are necessary to driveit out (see later).

Which limit is active is determined by the position of the dish with respect to the 68 degreemark. If the dish has entered the overlap region via the North direction (Azimuth = 0), it issaid to be in a "North wrap" and this information is displayed on the bottom lefthand cornerof the showtel monitoring program. Alternatively, if the dish has entered the overlap regionfrom the South, it is said to be in "South wrap". For example, at 60 degrees, the 206-degreelimit is active, whereas at 80 degrees the 294-degree limit is active. If the dish is in the overlapregion, and the 206-degree LED is lit, this means that the overlapping region was entered fromthe North (a counter-clockwise drive). Therefore to observe a source with an Azimuth below206 degrees a long clockwise drive would be required.

Chapter 4: Observing 27

The ME also has limitations in both Hour Angle and Declination, but these will not normallybe encountered because the me is not normally driven directly. The one exception is if the mehas been left tracking for a long period with the dish stowed, when it will encounter the westernhour angle limit.

4.3.4 Receiver Translator

The Translator is an electro-mechanical device used for positioning receiver packages at the focalpoint of the telescope. It has 5 axes of motion, namely:

• Z, the whole translator carriage horizontally along the floor,

• Y1, platform #1 (closest to the lift leg) up and down,

• Y2, platform #2 (closest to the air conditioner air register) up and down,

• R1, Platform #1 rotation about an axis perpendicular to the floor, and

• R2, Platform #2, as for R1.

Movement in any of these axes allows any of the installed receivers to be positioned atthe telescope focus, and, optionally, to be maintained at the "best-focus" position during theobservation, compensating for dish distortions. The translator can also be moved in the axialdirection (parallel to the optical axis) to optimise or adjust focus. Rotation of receivers is alsopossible, typically to "parallactify" the feed (i.e. compensate for the relative rotation of thetelescope focal plane on the plane of the sky, due to the Alt-Azimuth design of the telescope).

Schematics of the translator and focus cabine are shown in Figure 4.2 and Figure 4.3 respec-tively. Typically, the larger receivers such as the 1050CM and 20CM Multibeam take up anentire mounting frame whereas smaller receivers such as the 13MM, GALAILEO, etc only takeup half.

Figure 4.2: Layout the the translator

28 Parkes Users Guide

Figure 4.3: Cross sectional view of the focus cabin

4.4 The Telescope Control Software

The current system comprises the following computers;

• me: A PDP-11, located underneath the ME hardware itself. Drives the me (Master Equa-torial).

• servo: A PDP-11, located in Rack 1 of the second-level control room. Controls the mainantenna drives and the me servo system.

• pkdesk: A PC running Linux, located in the second-level control room in Rack 1. Processesrequests for antenna motion from all observing applications, handles all angle computationsand and passes low-level position requests to me and servo.

• fcc: A PC running Linux, located in the focus cabin (shielded cabinet). Handles allrequests for translator motion, from operfcc, from pkdesk (for focus tracking) or (in userlocal mode) direct from keyboard.

• pavo,pisces: Sun Solaris workstations located in the first level control room.

• pkccc1-4: PCs running realtime Linux, located in sheilded cabinets in the second–levelcontrol room.

Chapter 4: Observing 29

4.5 Master Control Panel

Figure 4.4: The Master Control Panel and UPS alarm (upper right).

The 64m Master Control Panel (MCP) is the primary interface between the PDP11-23 Tele-scope Drive Computer (SERVO), the limit switches and sensors mounted on the telescope struc-ture and the SWEO Regenerative DC Drives that control the motors. It provides interactivefunctions to bring the telescope into operation, position it manually and safely stow it whenoperations are complete. The Azimuth and Zenith drives are independent, and it is possible todrive the dish in one axis with the other axis still stowed.

4.5.1 MCP Panel Description

A description of MCP features is presented below.

• Position dials: Each axis (Azimuth, Zenith) has 2 dials, a coarse and a fine position encoder.These should not be used for recording dish positions as the computer (SERVO) positionis of a much higher accuracy.

• Limit indicators: One of these four button-like red lights (Az: 295 and -155 (205) deg.; Ze:+1 and +60 deg.) on either side of the coarse position dials is illuminated if the dish is ineither of the Azimuth wrap limits, the Zenith or horizontal limit. You can exit these limitsby pressing the appropriate EXIT LIMIT button.

30 Parkes Users Guide

• Azimuth Wrap Indicators: Which wrap limit is currently active: SOUTH or NORTH. SeeFigure Figure 4.1 below.

• Rate Control Knobs: These allow the dish to be driven under manual control in bothAzimuth and Zenith angle. When moved to zero, the LED turns blue.

• X1 and X10: Selects for each axis whether the rate control knob is working on the X1 scale(0.0 to 2.5 deg/min in Azimuth, 0.0 to 1.2 deg/min in Zenith), or the X10 scale (0.0 to 25.0and 0.0 to 12.0 deg/min respectively). They are only active when in MANUAL control.There are very few situations where one would use the X1 button.

• DRIVE: Control the "SWEO" Motion Controller for each axis. When enabled, they allowthe dish to be driven from either the MCP rate knob (if under LOCAL control) or thecomputer (if under COMPUTER control). The Azimuth drive cannot be enabled if thedish is not completely off jacks, the dish is in one of the Azimuth limits or the Azimuthrate control knob is not set to zero (inducated by a blue LED). Similarly the Zenith drivemay not be enabled if the dish is in one of the Zenith limits or the Zenith rate control knobis not set to zero. When the drives are disabled, the brakes are automatically applied. Theactual effect of enabling a drive is to remove the brakes. This is not advisable if there is arate being applied to the motors. The usual result is blown fuses, and a delay of half anhour or more.

• LIMITS: EXIT LIMIT: Applies a small (0.9 deg/min) rate to the drive if the dish has beendriven into one of the limits. Requires MANUAL control. This is the only way to drive outof a limit indicated by one of the limit indicators being illuminated). Note: this applies toboth Zenith and ground limits.

• PROCEED IN LIMITS: Applies a small (0.9 deg/min) rate to the Zenith drive when it isin the Zenith limit to drive it onto the stop, where the pin can then be inserted. RequiresMANUAL control.

• POWER: When power is supplied to the MCP by pressing the "ON" button, the gearboxlubrication pumps are running, the 400 Hz power supply needed for the position synchros ison and power is available to the SWEO Controllers which control the Azimuth and Zenithdrive motors.

• CONTROL: This panel selects between Local and Remote control. If Local is selectedand the RATE SOURCE is set to MANUAL, the computers cannot take control the dishwhich can be moved only from the MCP. If COMPUTER is selected, the dish may notbe driven from the MCP. The rate knobs on the MCP are deactivated, though the Power,Disable, Control and Jacks buttons are still active so that it is possible to stop the dish bypressing the DISABLE buttons which applies the brakes or by selecting MANUAL whichjust interupts the drive.

• LOCKING PIN: Drives the locking pin in and out. The IN/OUT buttons are interlockedvia relays so that the PIN can only be driven when the dish is on the Stop (indicated bythe Zenith Stop LED being red).

• Jacks: The dish moves in Azimuth on four rollers on a 17-m diameter track at a maximumrate of 24 degrees per minute. When not in use or in winds greater than 65 kilometresper hour, for safety the telescope is placed on eight hydraulically operated jacks locatednear each roller. To release the jacks, hydraulic pumps are turned on from the second–levelcontrol room. These build up a pressure of 6000 PSI (shown on gauges), enabling the jacksto be raised and the weight of the dish to be transferred back to the rollers. Each buttonactivates the hydraulic pumps on the Azimuth jacks. When the dish is not being used, itshould be placed on jacks.

• Emergency Stop: Removes all control system power, which applies the brakes in both axesand is ONLY to be used in an emergency. To reset, turn clockwise.

Chapter 4: Observing 31

4.5.2 MCP LED Description

Figure 4.5: Sub–system LEDs on the MCP.

On the top right section of the MCP there are 24 pairs (one spare) of LEDs. Figure 4.5 showsthe layout. The following describes the condition of that part of the system if the LED is red.

• Oil pressure: Failure in the Azimuth or Zenith gearbox lubrication system. No telescopedriving can occur without the pumps operating.

• 400 Hz supply: The 400 Hz supply for the dish position synchros is not turned on and thedish cannot be moved.

• Power TagOut: A local staff member has tagged out the power. Refer to contact person(s)listed on tag(s).

• Drive power: There is no power available to the SWEO Motion Control equipment.

• Brake power: There is no power to release the brakes. Indicates a fault in the power supply.In most cases this indicates that the "fuse" has been tripped. To reset this, turn the powerOFF and then ON.

• Emergency Stop System: One of the 12 emergency stop buttons on the telescope sctructurehas been pressed, or a safety key from the same unit has been removed, or there is someother fault condition. Driving is not possible in this state.

• Remote Control: Control of the MCP can be in either Remote Control or Local.

• Safety Timer: Disabling the Safety Timer is possible via remote control.

• Azimuth TagOut: A local staff member has Tagged Out the Azimuth drive. Refer to tag(s)for details.

• Azimuth Ready: The Azimuth drive is disabled.

• Azimuth On: The Azimuth drive is disabled.

• Azimuth Brake Release: The brakes have failed to release.

32 Parkes Users Guide

• Azimuth Limits: The dish has been driven into one of its wrap limits. It can only be drivenfrom this limit by pressing the assosiated (Azimuth, Zenoth) EXIT LIMIT button.

• Azimuth Wrap: The current Azimuth wrap sector, South or North (see Figure Figure 4.1).

• Azimuth Jacks: The dish cannot be driven in Azimuth because the jacks are either downor in some intermediate state.

• Zenith TagOut: A local staff member has tagged out the Zenith drive. Refer to tag(s) fordetails.

• Zenith Ready: The Zenith drive is disabled.

• Zenith On: The Zenith drive is off.

• Zenith Brake Release: The brakes have failed to release.

• Zenith Limits: The dish has been driven into either the Zenith limit or the horizon limit.It can only be removed from this limit by using the EXIT LIMIT button.

• Zenith Stop: The telescope is On Stop.

• Zenith Locking Pin: The pin has been driven in.

• 60V Power Supply: The fuse in the 60v control power supply has blown and is preventingthe MCP from operating.

4.6 Weather and wind restrictions

The Operator is responsible for the safety of the telescope and must be able to carry out correctsafety and emergency procedures to cope with all conditions. The Operator must monitor theweather at regular intervals. The showtel monitoring program, the VAISALA wind indicatorand the winds program help in this task. VAISALA is the wind speed and direction indicator.This is a real time indicator interfaced to the servo computer to initiate an automatic wind parkaccording to wind conditions. winds displays trends over the last hour. Every 120 seconds, thewinds display is updated with a bar indicating the average and maximum (gust) wind velocitiesover the last 120 seconds. The OPERATOR is required to make outside weather inspectionsregularly and whenever a computer wind park occurs.

4.6.1 Storm Stow

During lightning activity in the region, SHOWTEL may prompt the observer with the followingmessage "STORM WARNING". This indicates a storm front is approaching, with the posibilityof strong winds and power outage. To preempt this, proceed to park the telescope and awaitthe at least 10 minutes to ascertain if it is safe to recommence observing. In the future this willbe automatically done via the telescope protection system.

4.6.2 Automated Wind Park

The servo computer monitors the speed and direction of the wind from both Anemometers(one on the dish, the other in the paddock), and will stow the dish automatically above limitsdefined in Table 4.1 to ensure the safety of the telescope. These limits are monitored by servoand can be displayed on the maintenance page on dish0-pa (near the MCP) by typing CTRL P

M.

After being wind-parked, SERVO counts down from 10 minutes and during this time youwill not be able to re-commence observing. Whilst the telescope is being wind-parked, you mustnot try to override the automatic stow. The observer should be aware of the wind restrictions,and in the event that pkdesk has crashed they must be prepared to stow manually using theMCP. In this situation the wind may be monitored from the wind indicator in showtel or byusing winds.

Chapter 4: Observing 33

The conditions (wind velocities; km/hr) under which the telescope automatically stows areshown in Table 4.1 and can be monitored from the maintenance page of the servo display ondish0-pa (near the MCP; type CTRL P M).

Peak Gust Average

Ane #1 (Az front) 58 54 42

Ane #1 (Az front) 58 54 42

Ane #1 (Az back) 46 42 35

Ane #2 (Az front) 66 62 48

Ane #2 (Az back) 53 48 40

Table 4.1: Wind Park Algorithms

The Peak (2 consecutive readings), Gust (5 readings in the last 180), and Average (15 readingsin the last 20) values (in km/hr) must be satisfied for a wind park to occur.

The “Az back” for each Anemometer are for winds within Azimuths 150 degrees < Az < 210degrees (ie, winds within 30 degrees of the back of the telescope). The “Az front” values are forthe remaining 300 degrees “front-on”sector.

The wind must be below the values given above for at least 10 minutes before the telescopecan be unstowed. During a computer initiated wind park it is strictly forbidden to preventit using the MCP drive controls! Once an automatic wind park has occurred, the telescopemust not be unparked until permissible conditions have prevailed for at least 10 minutes. Ifconditions are poor, the telescope must be fully stowed.

During an automated wind-stow, the telescope drives to an Azimuth that has the wind atleast 60-degrees away from the back of the dish without driving into an Azimuth limit. If youare observing near one of the limits and there is an easterly wind this could involve driving upto 100 or so degrees.

4.6.3 Current Stow

The wind has a greater effect on the Zenith motor currents of the dish at high Zenith angles andif it is directed either towards the surface or the back of the dish. The main problem is that astrong wind onto the back of the dish can "hold it down" causing the motor currents to reverse(the counter weight is heavier than the dish). In this case, you might receive a ’HIGH/LOCurrent Stow’ (as reported by showtel). In a physical sense, the low current condition isintended to detect overbalancing of the telescope when a strong wind blows into the back of thedish. The threshold for the low current condition is three occurances in 120 seconds where thedifference between the Zenith motor currents is -2.5 Amp. Again, this can be monitored fromthe maintenance page of the servo window on dish0-pa (near the MCP; type CTRL P M).

4.7 Stowing and Unstowing

4.7.1 Stowing

Switch the MCP RATE SOURCE to "MANUAL".

Zenith:

• Drive the dish to the TOP limit (the red +1 deg. limit light turns on). The "Zenith Limits"LED should be red. Put Zenith dial to the Zero mark (a blue LED should come on).

• Press the "PROCEED IN LIMITS" button.

• After the dish has proceeded to the STOP (as indicated by the red "Zenith Stop" LED),press the LOCKING PIN "IN" button.

• The LEDs Zenith Ready, Zenith On, Zenith Brake Release, Zenith Limits, Zenith Stop andZenith Locking Pin should be red. You are now stowed in Zenith (check SHOWTEL).

34 Parkes Users Guide

Azimuth:

• Press the DRIVE "DISABLE" button. The "Azimuth On" and "Azimuth Brake Release"LEDs should be red.

• Unless told otherwise, DO NOT perform a full stow in Azimuth as described below. Proceedto Once completing the above...

• Press the JACKS "ON" button. The Azimuth drive "Disable" button turns red and thegreen "OFF" button begins to flash. Wait for the "ON" button to light half-bright. Thiscan take up to several minutes.

• Go up to the Azimuth track and move the 8 jack handles from the FREE to the STOWEDpositions.

• When back down at the MCP again, the LEDs for "Azimuth Ready", "Jacks" and buttons"Jacks On", Azimuth drive "Disabled" should be red. You are now stowed in Azimuth.

Once completing the above AND you are leaving the telescope vacant, press the red POWER"OFF" button (NOTE: this disables the Safety Timer as well, as does disabling both Azimuthand Zenith drives when stowed.)

4.7.2 UnStowing

• Check for Tags on MCP, contact person(s) listed on tag(s).

• Check whiteboard, announce movement using the Clear Call.

• Press the POWER "ON" button and switch RATE SOURCE to "MANUAL".

Azimuth:

• Unless you have fully stowed the telescope in Azimuth, proceed to "Press the AzimuthDRIVE..." below.

• Press the JACKS "OFF" button. The JACKS "ON" button begins to flash. Wait for the"ON" button to light half-bright. This can take up to several minutes.

• Go up to the Azimuth track and move the 8 jack handles from the STOWED to the FREEpositions. Within a few minutes of returning, the JACKS "OFF" button should be fullylit. The "Azimuth Jacks" LED should be green.

• Press the DRIVE "Enable" button. The "Azimuth On", "Azimuth Brake Release" and"Azimuth Jacks" LEDs should be green.

Zenith:

• Set Zenith control dial to the zero mark (blue LED should be on).

• Press the LOCKING PIN "OUT" button. The Zenith Locking Pin LED should turn green.

• Press the LIMITS "EXIT LIMIT" button. The Zenith drive "Enable" button should turngreen.

• When the top red +1 deg. limit light goes out, drive to about 2 degrees. The "ZenithLimits" LED should be green. Put dial back to Zero Mark (blue LED comes on).

• Switch RATE SOURCE to COMPUTER control.

When fully unstowed, except for "Remote Control" and "Azimuth Wrap" LEDs, all otherLEDs should also be green.

4.7.3 When Jack Levers won’t turn

The trouble is most likely caused by wind pressure pushing a pair of jacks at an uneven angle,not allowing enough room to rotate the jacks. By rotating the antenna in Azimuth, you takethe pressure of one pair of jacks and share it onto two pairs. If you are attempting to put thetelescope onto jacks in high winds and you can’t turn one of the jack levers around :

Chapter 4: Observing 35

• Go back and take off the jacks that you did succeed with. i.e. return every jack lever from"LOCKED" to "FREE".

• Go back to the second–level control room and turn the MCP OFF; This will turn off thehydraulic pressure.

• Wait until pressure is down and turn the MCP back ON.

• Rotate the Azimuth by 45 degrees, away from the wind (use the winds display).

• Attempt normal JACKS ON procedure; press the JACKS ON button, wait a few minutes,attempt to rotate levers again.

4.8 Power Supply via Mains/Diesel/UPS

4.8.1 Introduction

The Observatory has two sources of power. The principal power supply is provided from the11kV Country Energy mains. A 300kV diesel generator provides a backup supply to mostcircuits in the tower (and some elsewhere on site) in the event of mains failure. Some criticalcircuits have a further backup from a UPS (Uninterruptible Power Supply) which can last up to1 hour, supplying ctitical systems. Computers, electronics, clocks, masers and receiver systemsare connected to the UPS protected circuits. The lights, telescope drives and many other systemsare not protected by the UPS.

NOTE: The 300kEv generator resides between the generator hut and the Visitor’s Center.The old generator stil resides in the generator hut, but is no longer used.

There is also a timer high on the wall of the first level control room (see Figure Figure 4.6;above the winds and showtel displays) which shows the time since the last interruption to themains supply. If the mains supply is available, the timer will be updating. If there is no mainssupply to the Observatory, the timer display will be all zeros and the small red mains-failurelamp will be illuminated.

Figure 4.6: Timer in control room showing time since last power failure.

If the Country Energy mains fail, the generator should start automatically and provide powerso that after a short interruption you will be able to resume observing. The actions you willneed to take are described in detail in Section 4.8.8 [Resetting the UPS Alarm], page 39.

If the generator fails to start and the mains supply does not return (the room lights inthe control rooms go off and stay off, this is a CRITICAL situation and must be dealt withIMMEDIATELY, as described in Section 4.8.6 [Severe Power Failure - no mains or generator],page 37.

36 Parkes Users Guide

4.8.2 Monitoring Power - Monica

You can monitor the Mains and GenSet with Monica (Monica) by clicking on Parkes - Navigator- favourites - generators. Monica should be running on the third or fourth-screen on bourbonin the control room (or you can install using the link above). A screenshot of the generatorsdisplay is below.

Figure 4.7: The Parkes generator monitor page in Monica.

The likely scenarios are dealt with separately below.

4.8.3 Power failure: Brief mains glitch

As of August 2009, the MCP no longer disables itself during a Power Failure. A power outage ofsufficient length will disable the SWEO drives and apply the brakes, but the MCP will remainin computer control. If the outage is only a glitch of a few 10s of milliseconds - just enoughto flash the lights but short enough for the SWEO drives to stay on - the telescope drive willcontinue as if nothing happened.

When the outage is long enough for the SWEOs to be disabled - e.g. when the generatorstarts or stops - the drives will be disabled and the brakes applied. Once the power is stable thedrives may be re-enabled while the MCP remains under computer control. If the dish is still inlock capture range of the ME the telescope will reacquire lock and the drive can resume.

During any interruption, an alrm will sound in the control room indicating you will need toreset the UPS alarm beside the MCP, as described in Section 4.8.8 [Resetting the UPS Alarm],page 39. On the Monica display display, you should see the following:

• LS4 - Mains power available : true

• GPC31 - Generator start enabled : false

4.8.4 Power failure: Generator starts automatically

If there is a failure of the mains for longer than a second, the generator should start automatically.Once it is up to speed it will be switched to supply the telescope. The interruption to the supplywill trigger an alarm to sound next to the MCP (see Section 4.8.8 [Resetting the UPS Alarm],page 39), and the mains interruption timer will be reset to zero and will not update. Torecommence observing it will be necessary to enable both the azimuth and zenith drives, andswitch back to computer control.

On the Monica display display, you should see the following:

• LS4 - Mains power available : false

• GPC31 - Generator start enabled : true

Chapter 4: Observing 37

If both of these items are false, this indicates an ERERGENCY SITUATION and must bedealt with IMMEDIATELY, as described in Section 4.8.6 [Severe Power Failure - no mains orgenerator], page 37.

4.8.5 Power failure: Mains Return

When the mains power is available again, and has been stable for a period of around 1 minute,the suppy will automatically revert from generator to mains. The MCP will remain on andbecause the generator synchronises with the mains on transfer back to mains power, it happenswithout a break, so the UPS suffers no break in input power. This means that the alarm panelnear the MCP will not enter an alarm state at this time.

4.8.6 Severe Power Failure - no mains or generator

This is a CRITICAL situation and must be dealt with IMMEDIATELY.

If the mains power fails and does not return, and the generator fails to start or stops forsome reason, you must immediately intervene. The best indicator of this situation is that theroom lights in the control rooms will go off. If they stay off for more than 30 seconds or so thenthe only source of power is the UPS and urgent action is required. Another indicator of thissituation is the timer high on the wall of the first-level control room displays all zeros and doesnot update.

• Go over to the generator hut and see if the generator has been left in Local mode. If so,select Automatic. The generator should start up. <<<<<<< .mine

• If the generator is already in Automatic mode, call the Call-out person, then either MalSmith, Matt McFarland or Brett Preisig. =======

• If the generator is already in Automatic mode, call Matt McFarland, then the Call-outperson. >>>>>>> .r4833

• Notify your DCP.

• Stay in the tower and await further instructions.

Note: The phone system in the tower has its own UPS which will last for approximately 1hour. After that, the only operational phone will be the one in the first level control room onthe centre column labelled Emergency Phone.

The emergency phone has the following features.

• You DO NOT need to dial 0 to get an outside line, this phone is on a separate line connecteddirectly to the Telstra Telephone exchange.

• If there is a problem with the Telstra phone exchange, the emergency phone will not work.Use a mobile phone available if available.

4.8.7 Pre–empting an outage

NOTE: The generator is now located between the generator hut and Visitor’s Center. You nolonger require ear-muffs when starting the generator.

If there is a need to pre–empt a main outage (Thunderstorms, planned maintenance), youwill need to go to the generator hut. Once there, proceed inside to the left of the generatorwhere you will see the control panel for the generator as shown below in Figure 4.8.

38 Parkes Users Guide

Figure 4.8: Generator Control Panel.

Chapter 4: Observing 39

Figure 4.9: Switch for transfering power to/from Mains/Generator.

To manually switch over to the generator, move the "POWER SOURCE SELECTION (lo-cal)" switch, see Figure 4.9, to "GEN". Once this is done, the generator will start and bringitself up to speed so the changeover from Mains to generator can occur.

When you decide to switch back to Mains, go back over to the generator hut and switch the"POWER SOURCE SELECTION (local) switch from "GEN" to "MAINS".

Note: It is no longer necessary to halt observing to switch between the Mains and thegenerator.

If the power from the generator should fail in some way, the system will automatically switchback to mains power.

4.8.8 Resetting the UPS Alarm

In the event of a power outage, an alarm in the control room (see Figure 4.10) will soundindicating the UPS alarm next to the MCP needs to be reset.

Figure 4.10: UPS alarm in the control room.

To reset the UPS alarm beside the MCP (see Figure 4.11), perform the following:

• On the UPS alarm indicator next to the MCP, press the following sequence: RESET-TEST-RESET.

• If any lights remain lit after 60 seconds, there is a fault with the UPS. This can also beidentified in Monica by the ’Genset summary alarm’ set to OK. Here you need to contactthe Call–out person AND Matt McFarland and inform them which LEDs are lit.

• Please record any interruptions of Power Supply in a fault report2.

2 http://www.parkes.atnf.csiro.au/observing/feedback/report.php

40 Parkes Users Guide

Figure 4.11: UPS alarms on the first and second–floor control rooms.

Chapter 5: Observing Checklist 41

5 Observing Checklist

5.1 Observing Checklist UPSTAIRS

• Check with operation staff whether daily hardware changes are required for the project(rare, but, e.g., some recabling could be necessary because of a different setup of a concurrentproject).

• Rack #8: To make sure your required receiver is turned on, go upstairs to Rack #8 (closestto the stairs). There you will see a panel with orange buttons as shown in Figure 5.1 withthe labelling REMOTE SWITCH CONTROL PANEL. Depending on the reciever beingused, the following table lists which silver toggle switches should be ON/OFF:

| | 20CM | Other |

1 | Receiver Pan A/B | ON | ON |

2 | Receiver Pan C | | ON |

3 | CAMERAs | OFF | OFF |

4 | | | |

5 | GP-IB EXTENDER | OFF | f <= 6GHz: OFF; else ON |

6 | | | |

7 | | | |

Figure 5.1: Rack #8: HP 2 (top) and HP 1 (middle) synthesizers and the REMOTESWITCH CONTROL PANEL (black, bottom).

5.2 Observing Checklist DOWNSTAIRS

• Ask the previous observers to log out of all machines (PAVO, PISCES, LAGAVULIN andJURA).

• Exit all versions of TCS (on pavo/pisces), PKCOR (pkccc1), SDFB3/PDFB3 (pkccc3)and/or SDFB4/PDFB4 (pkccc4).

• Turn off LNAs of receivers installed in focus cabin for which you do not require (for MULTI,1050cm, 13MM):

• Use PKMC on Bourbon’s rightmost display (display #3)

42 Parkes Users Guide

• Click on "show" of the needed receiver(s)

• Click on LNA buttons to turn them RED

• TCS should perform this task, but turn on your receiver LNAs (for MULTI, 1050cm,13MM):

• Use PKMC on Bourbon’s right-most monitor

• Click on "show" of the needed receivers

• Click on LNA buttons to turn them GREEN

• Move receiver on axis

• Select your receiver on OPERFCC (bourbon’s left-hand side monitor)

• Press "place selected receiver on axis".

• SWITCH OFF FOCUS-CABIN CAMERA MONITOR (Generates RFI!!!)

• Depending on your required backend(s), you start pkcor on pkccc1, sdfb3/pdfb3 on pkccc3or sdfb4/psrdfb4 on pkccc4.

• Open a corr@pkcccN xterm on bourbon using the DFB3/DFB4/PKCOR icon on centralmonitor, user "corr", password (ask Ettore/John/Stacy)

• Start up the GUI: i.e., sdfb3

• Check the GUI window title has "Archive: RPFITS"

• IF THE CORRELATOR DOESN’T START there could be some not-killed processabout the correlator itself still on. In that case:

• Quit the GUI

• Enter corkill and (if using DFB3/4) then bcckill on the corr@pkcccN xterm.

• Restart the appropriate GUI.

• If the above does not work for DFB3/4, reboot the bcc boards:

• From the pkcccN xterm, login to the two bcc’s (l-bcc11 and l-bcc06) as follows:

• Use ssh root@l-bcc06 (password required)

• Enter reboot

• Similarly for l-bcc11.

• Set LO attenuations:

• On a SUN/Linux workstation, enter lorun ~/losetup/pXXX.cmd ("pXXX" is yourproject code)

• The script name could be different: ask operation staff for confirmation

• To check if it attenuators are correctly set:

• On logui (bourbon’s left-most monitor; screen #0):

• Press REFRESH in OPTIONS (to refresh to the actual values)

• Check C12att, C30att, C40att (for 64/128 MHz BW) and C50att for 256 MHzBW) are set to the desired levels (see pXXX.cmd file).

• Set SWITCH MATRIX:

This is usually managed by TCS, no user action required. Some non-standard configurationsrequire a special setup.

• if so directed by the support staff you will need to run an smrun script:

• On a SUN/Linux workstation, type smrun ~/smsetup/pXXX.cmd ("pXXX" is yourproject code)

• the script name could be different: ask operation staff for confirmation;

• to check whether the Matrix is correctly set:

Chapter 5: Observing Checklist 43

• on PKMC (on bourbon’s Display #3)

• click "show" of the "Switch Matrix";

• A1: your BW is connected to DFB3 A1 (DFB4 A1)

• B1: your BW is connected to DFB3 B1 (DFB4 B1)

• If Tsys is to be recorded using DFB3/4 => Set the Calibration signal (Tsys). On PKMC (onbourbon’s right-hand side monitor):

• Click "show" of the "Cal Control Unit"

• Turn off all cal signals

• Turn on cal signal "row of your receiver => column BEC-Sync0"

• If Frequency switching is to be used => Set the Calibration signal (freq sw). On PKMC(on bourbon, right-hand side monitor):

• Open the "Cal Control Unit"

• Turn on cal signal "row Conv Rack Freq SW => column MBCor FreqSW"

• Turn off all undesired cal signals

• Start TCS to manage the observations (under user "observer"):

• Check if tcs is running by a former observer and, if any, quit it

• type tcs

• For DFB3/4 spectral–line/continuum observing select:

• DIGITAL F’BANK (time binning)

• EXPERT MODE

• SELECT PROJECT (if present, via bottom menu)

• For Multibeam Correlator spectral–line/continuum observing select:

• MULTIBEAM CORRELATOR

• EXPERT MODE

• SELECT PROJECT (if present, via bottom menu)

• It is recommended to set the observation parameters by schedule, although it can bedone by TCS’ GUI. For schedule syntax, set the desired parameter in the tcs GUI andread the the result in the log panel.

• Focus: Enable

• Antenna: Enable If ANTENNA doesn’t enable, likely it means that either anotherTCS is still running with ANTENNA ENABLE (which takes the antenna control) orother software is controlling the antenna (like that used for PSR obs with the AnalogFilter Banks).

• Sched agend: CTRL

• Sched file: OWN and select the schedule file

• SCHEDULE files: Usually located in /p/observer/PXXX/Sched (or/nfs/online/local/tcs/sched/pXXX).

• SWITCH OFF FOCUS-CABIN CAMERA MONITOR (Generates RFI!!!)

• To check the correlator outputs, type spd on a pkcccN xterm of bourbon. Some basiccommands:

• sel 11 to see spectra (DFB only)

• sel pp11 to see profiles (DFB only)

• sel aa, bb first IF

• bins 1 - N time-binning mode only: it shows the first N bins of a time-cycle (DFBonly)

44 Parkes Users Guide

• x toggle "x" axis: channels <=> frequencies

• ch x-y show only channels from #x to #y. It is usually useful to skip first and lastschannels, e.g. ch 5-8185

• Additional commands for SPD can be found at the following: SPD Users Guide

• DATA LOCATION. On any SUN/Linux machine, data is located in directories

• /nfs/PKCCC3 4 => DFB3

• /nfs/PKCCC4 2 => DFB4

• /nfs/PKCCC1 1 => MBCOR

Chapter 6: Data Reduction and End of Observing 45

6 Data Reduction and End of Observing

6.1 ATNF Data Format

Raw data output from ATNF correlators is written in rpfits format. More information onrpfits can be found at http://www.atnf.csiro.au/computing/software/rpfits.html.

6.2 livedata & gridzilla

A guide to using the aips++ programs livedata and gridzilla can be found here (look under’Parkes Multibeam Reduction’). More detailed information on the specifics of these programsas related to the HIPASS and ZOA Hi Surveys can be found in Barnes et al. (2001), MNRAS,322 486. The gridzilla GUI contains a HELP menu item and the different sections of thelivedataGUI contains widgets, which when clicked on, present the user with a popup containinginformation relevant to that section.

With gridzilla it is possible to perform batch processing via a script (called batch.g) whichcontains the following:

include ’gridzilla.g’

files := shell(’ls *.sdfits’)

gridder := gridzilla(remote=T, files=files, selection=ind(files),

autosize=T,pixel_width=4.0, pixel_height=4.0,tsys_weight=T,

beam_FWHM=14.4, beam_normal=25, p_FITSfilename=test)

gridder->go()

await gridder->finished

print ’finished processing’

exit

Note the gridder line is split here over two lines, but should be only on one line. The scriptis run by typing glish -l batch.g .

6.3 ASAP

The ATNF Spectral Analysis Package (asap) is a new software package to reduce single-dish,single-pointing spectral line observations. At this stage it is tuned towards data from ATNFinstruments and reads rpfits, sdfits and is able to output sdfits, ASCII and CLASS formatfor processing within GILDAS and SPECX. A Cookbook, Tutorials and further information onasap is located here.

6.3.1 Example asap batch script: POSITION SWITCHING

In this example, observations at 22GHz are done in Position Switching Mode, where the sourceand a referenced position (free of line emission) are observed in sequence. The script below issaved into a file (called proc.py) and run from within asap by typing execfile(’proc.py’) orpython -i proc.py from the command-line. It reads in and processes all *RCW49*.rpf files inthe current directory.

import glob

from asap import *

fnames = glob.glob(’*RCW49*.rpf’)

vec = []

for f in fnames:

vec.append(scantable(f,average=False))

46 Parkes Users Guide

quotients = []

for scan in vec:

scan.set_unit(’km/s’)

scan.set_freqframe(’LSRK’)

scan.average_pol() #comment out this line to display both pols

quotients.append(scan.auto_quotient())

for q in quotients:

msk = q.create_mask([-100,100])

q.poly_baseline(msk,0)

av = average_time(quotients)

iav = av.average_pol()

plotter.set_legend(mode=-1) # No legend

plotter.set_range(-100,100,-5,30)

plotter.plot(iav)

Figure 6.1: 22GHz Stokes I spectrum of RCW49.

6.3.2 Example asap batch script: Beam Switching (MX Mode)

In Beam–Switching or MX mode, each beam of the 20CM or 6GHz Multibeam receivers is placedin turn on the source of interest. When not on-source, the other beams are still aquiring dataand so are used as reference data. In this example (taken from the P502 Methanol MultibeamSurvey), the RPFITS file contains two IFS; the first (IF0) contains the Methanol maser line at6668MHz and the second (IF1) contains Excited OH at 6035MHz. The IF selected depends onthe index used in selection.set_ifs(). This example only shows data associated with IF0.The script file is shown below.

scans = scantable("2009-03-20_1025_MMB-MX-G300.96.rpf",average=False)

Chapter 6: Data Reduction and End of Observing 47

scans.set_selection()

selection = selector()

selection.set_ifs(0)

scans.set_selection(selection)

scans.set_unit(’km/s’)

scans.set_freqframe(’LSRK’)

q = scans.mx_quotient()

msk = q.create_mask([-55,-30])

q.poly_baseline(msk,0)

av = q.average_beam()

iav = q.average_pol()

plotter.set_range(-55,-20,-0.5,2)

plotter.plot(iav)

Figure 6.2: Stokes I 6668MHz Methanol spectrum for 300.96+1.14 .

6.4 miriad

It is possible to process Parkes data using miriad. Initially, data is processed using livedataand gridzilla, where the latter produces a FITS file which can be loaded into miriad usingthe fits utility. As an example, here we load in a gridzilla–created fits file and use themiriad utility mbspect to display the profile of a galaxy, various parameters, plus create bothan ASCII file of the spectra and a colour postscript file. The basic script below allows one tocopy and past the code into a file (making it executable) for displaying a large number of sourcesquickly; it assumes the basename utility is available on your system.

#!/bin/sh

if [ $# -lt 1 ]; then

echo "Please supply a FITS file"

48 Parkes Users Guide

exit 0

fi

FILE=$1

BASE=‘basename $FILE .fits‘ #change suffix if different!

OPT="options=measure"

MSK="mask=4950,5450"

if [ -d "$BASE.mir" ]; then #remove existing image if present

rm -rf $BASE.mir

fi

fits in=$BASE.fits op=xyin out=$BASE.mir

puthd in=$BASE.mir/restfreq value=1.42040572 #insert rest freq of line

mbspect in=$BASE.mir xaxis=optical hann=2 order=-3 $OPT

$MSK device=/xs log=$BASE.spec

mbspect in=$BASE.mir xaxis=optical hann=2 order=-3 $OPT

$MSK device=$BASE.ps/cps

Running this script produces the following output and image.

#FR Clipped rms: 0.0066 Jy

#FN ( 654 out of 1024 channels)

# SPECTRAL FITTING

#MC xaxis: optical

#MX Maximum: 0.050 Jy at 5065.440 km/s

#MN Minimum: -0.028 Jy at 6141.707 km/s

#NP Number of spectral points: 1024

#SN1 Peak S/N ratio = 7.57

#CL Clipping inside range ( 0.000, 0.000) Jy

Moment: 0 1 2

#MM 9.660 5215.471 101.712

#SN2 Mean S/N ratio = 0.83

Robust moments: 0 1 2

#MR 9.744 5197.634 104.134

units: Jy km/s km/s km/s

Chapter 6: Data Reduction and End of Observing 49

Figure 6.3: Spectrum of a galaxy using the mbspect utility of miriad

For information on keywords used in the above script, please refer to the miriad user guide.

6.4.1 Gaussian fits within asap

Although miriad has utilities to perform gaussian-fits to spectra, you can import the ASCII filecreated from mbspect (using log=file) into asap. For example, place the following code intothe asapuserfuncs.py file (located in your $HOME/.asap directory).

def readxy(filename=None):

f = file(filename,’r’)

x = []

y = []

lines = f.readlines()

f.close()

for l in lines:

vals = l.split()

x.append(float(vals[0]))

y.append(float(vals[1]))

return x,y

Now when you run asap, you read in the ASCII file (with comments removed and only twocolumns) and fit a two–component gaussian and output a Postscript file of the plot as follows.

x,y = readxy(’fred’)

f = fitter()

f.set_data(x,y)

f.set_function(gauss=2)

f.fit()

f.get_parameters()

f.plot(components=[-1,0,1])

f._p.set_axes(’xlabel’,’velocity km/s (LSR-K)’)

f._p.set_axes(’ylabel’,’Y-label’)

f._p.set_axes(’title’,’Title’)

f._p.save(’fred.eps’)

50 Parkes Users Guide

6.5 Source finding programs

asap has the functionality to identify spectral lines within a data cube using linefinder.Similarly, the duchamp utility can also search for spectral-line sources, produce source lists,spectra and moment maps. Users are encouraged to view the online documentation for these.

6.6 Other Packages

A list of supported and non-supported data-reduction software can be found at the ATNFwebsite.

6.7 Australia Telescope Online Archive

Although DVDs of data can be supplied to observers, spectral–line (non-pulsar) data is automat-ically uploaded into the Australia Telescope Online Archive (ATOA). Using your OPAL account,you can download data directly from ATOA. There is usally a gap of a few days between takingyour data and seeing it in ATOA.

6.8 Media Storage

The site has CD/DVD, DLT IV, SuperDLT and DLT-S4 drives. Magnetic tapes are availableat cost price.

Since some projects obtain very large datasets, it will be more convenient to take your filesaway on a portable hard drive than on multiple DVDs. To get your files onto your portabledrive, you may use any of the workstations in the observers area by following the steps:

• log in to the computer using your ATNF username and password

• plug your portable hard drive into the USB port on the computer

• USB is the only supported interface for portable hard drives

• wait for a couple of minutes while the hard drive gets mounted automatically by the com-puter. The drive should be mounted at /media/usbn, where n is the partition number(numbered from 0). You can use the command df |grep media to check whether it hasmounted.

• the only supported filesystem types are ext2/3 and FAT32

• Transfer your files across from the local archive:

• change directory to your portable hard drive. For example: cd /media/usb0

• and then execute the command: cp /nfs/PKCCC3_4/*P345* . to copy all project P345data.

Do not transfer files directly from correlator machines! Please use the following NFS mountpoints as provided on all Linux machines in the control room:

Correlator Machine NFS mount

Multibeam pkccc1 /nfs/PKCCC1_1

DFB3(P) pkccc3 /nfs/PKCCC3_1 and /nfs/PKCCC3_2

DFB3(S) pkccc3 /nfs/PKCCC3_4

DFB4(P) pkccc4 /nfs/PKCCC4_1

DFB4(S) pkccc4 /nfs/PKCCC4_2

Table 6.1

An (S) above denotes spectral-line (non-pulsar) data and a (P) denotes pulsar-only data.

You can also copy your data to your laptop in a similar fashion to that described in PortableStorage. When your laptop is plugged in to a pink cable, you may access LAGAVULIN, so youcan copy your data with the command:

Chapter 6: Data Reduction and End of Observing 51

scp username@lagavulin:/nfs/PKCCC3_4/*P345* .

which would copy all project P345 data, and where username is your ATNF username.

6.9 Disk Cleanup

If a directory was created for you in /DATA on the Linux/Unix system, please backup anddelete this data BEFORE you leave. Otherwise, it will be deleted at any time after you leaveto make room for other observers.

6.10 Observer Report

At the end of your run, we request you fill in an Observers Report to help us make the Observa-tory a better place to work and play. The form is found here. The completed form is distributedwith your name visible to a selected list of Observatory staff whom are listed via a link on theabove form.

Chapter 7: TroubleShooting 53

7 TroubleShooting

This section describes some commonly encountered problems at the Parkes RadioTelescope andprovides receipes for overcoming them. It is by no means an exhaustive list of all problems, butwill hopefully provide a starting place. This section is constantly changing, check back regularlyfor updates. Also search the on-line fault reports and responses for problems and solutions. Inthe case of serious problems (those which endanger you or the telescope equipment), notify theCall–out person immediately.

7.1 Correlator issues

7.1.1 DFB issues

If you strike problems using the DFBs, it is recommended you follow the checklist below to tryand rectify the problem. Some of the more common error messages reported by TCS and/orthe DFBs when configured are listed below:

• CF RocketDialFailure for l-bcc06 and l-bcc11

• CFG$UnableToOpenFile

• CONFIG: CFG BadIntPerOrSwCalPer

• CONFIG: Mis-match ETD id for etd file sdfb3 - no ETDs sent

• XFER: ERROR l-bcc06 and l-bcc11

The checklist is contained in fault report 6515 and can be viewed here (internal access only).A laminiated sheet should be located above pisces in the lower control room.

7.1.2 Other Correlators

Error messages associated with the Multibeam, Wide-band correlators may include:

• CONFIG: ER ETDQueueOverflow from blk 7

It is usually best to stop observing and try recofiguring the correlator using the CONFIGbutton on the PKCOR GUI. If you need to restart the block control computer(s), they are’standard’ diskless PCs with the familiar white reset button. Occasionally the EVG (EventGenerator) cards in the BCCs get into an error state with a red LED showing, indicating loss ofclock frame. It is usually necessary to power-cycle the BCCs, not just reboot them, to clear thisred LED indication. (This can also occur with the EVG card in pkdesk). Any reset of a BCCrequires a manual reprogramming of the associated correlator, by clicking on the CONFIGbutton of the correlator GUI.

7.1.3 Block Control Computers

The location of each block control computer is summarized below:

• pkbcc02 - blocks 2,3 Multibeam correlator

• pkbcc04 - block 7, Multibeam, Wideband and DFB2 [rack-mounted PC inside Widebandcorrelator rack]

• pkccc3 - block 2 Run on host machine for DFB3

• l-bcc06 - block 6 Embedded within DFB3, on private network with pkccc3

• l-bcc11 - blocks 5,7 Ditto

7.2 Australia Telescope Distributed Clock Displays all zeros

Occasionally the AT Clock display will crash and display only zeros. The system simply needsto be reset which can be done by pressing and holding the system reset button for 2 seconds toreset the display.

54 Parkes Users Guide

7.3 Azimuth and/or Zenith Drives Disabled

Rarely the Azimuth and/or Zenith drives will disable for no apparent reason. If this happens,first assess the state of the telescope then;

• Stop the observation

• Put MCP in manual control

• Power cycle MCP

• Return MCP to computer control

7.4 PKDESK requires a restart or crashes

You may need to restart pkdesk in situations such as when the machine you’re running theobserving program (i.e. tcs) crashes and leaves an open socket connection to pkdesk (The"Primary host" line on the pkdesk screen shows the IP address of the host making the connec-tion to pkdesk). Currently the only way to clear this situation is the restart pkdesk by typingquit.

The pkdesk computer is located in the second-level control room in Rack 1. It has a blackpull-out keyboard with monitor as shown in [Figure 7.1], page 54. You may have to check thedisplay is set to display #2 (DESK) and press the spacebar to activate the screen. On thepkdesk console, simply type quit and hit <Enter>. pkdesk will shutdown and restart in 10-15seconds.

However, if you see messages on showtel (or kpdesk itself like:

• showtel beeps and complains UTC not updating

• showtel shows me status as BAD or NOCMD

• Antenna refuses to drive as requested

• On pkdesk you see incrementing "err" counts for the coord, me, servo and LAN columns

You may need to restart pkdesk. Type quit then <Enter> and wait 10 to 15 seconds whilepkdesk restarts automatically. showtel will complain "pkdesk NOT RESPONDING" whilethis happens, but should recover quickly once pkdesk starts again. If you need to reload theme and/or servo code again, follow the instructions on the laminated sheet (usually) locatednear the pkdesk keyboard/monitor (or see Section 7.9 [ME or SERVO stops/crashes], page 57).

Chapter 7: TroubleShooting 55

Figure 7.1: pkdesk location and display in Rack 1.

Recovering observing applications: tcs and pmctrl will lose their connections to pkdesk(the antenna) if pkdesk is restarted. For tcs;

• click on "antenna" button, select "disable", then

• click on "antenna" button, select "enable".

For pmctrl, you might have to quit completely and restart.

7.5 Mouse seems to have disappeared on BOURBON

Most likely the mouse is just on one of the other screens (there are three). Try moving themouse in one direction until it appears in the furthest screen.

7.6 operfcc Reports Y2 Axis Following Error

operfcc may report an error when selecting a new receiver, other than the multibeam. Theerror, which reads: “y2 Axis Following Error”, occurs when a new receiver is selected with thetelescope is at or near stow. To fix, type the following in the “Command:” window on theoperfcc GUI (may need to do twice):

• take

56 Parkes Users Guide

• stop

If the video camera for the focus cabin is on you should hear a click. Now re-select thereceiver.

7.7 Loss of 1MHz sampling clock and/or 0.2pps (5-second)pulse

This may happen whilst observing using the Multibeam pulsar filterbank. The PDP11/73Timing Computer (located in the upstairs control room, rack 1 supplies the 1MHz samplingclock and the 0.2pps (5-second) pulse for the Multibeam pulsar filterbank. An alternate sourceof the 5-second pulse is also provided from the pkdesk computer.

The Timing Computer derives its timing via a clock bus connection to the station clock.When it is working correctly you will see a green LED flashing at 11Hz on the events distributionpanel immediately above the computer. (You should also be able to see the 5-second pulse onoutput "EVD8" if you look carefully).

If this isn’t running the Multibeam pulsar filterbank may not work correctly and the TimingComputer needs to be started.

The console for this computer is displayed on the flat-screen display near the MCP whichalso shows terminals for servo, me, winds and showtel. The Timing Computer window hasa grey background. To restart the program;

• left-click in that window (to make sure your keyboard input goes to it and not anotherwindow)

• type ctrl c at least twice in succession (three times is also good!) and wait a few seconds.You should get the "." (period) prompt after a few seconds. If so skip the next step.

• If you can’t get the . prompt, or if you have the @ prompt, or if you have no prompt, you’llneed to reboot the computer. Locate it and press the restart button. The machine takes acouple of minutes to reboot - patience is required.

• Once you have the . prompt, type;

WPP <ENTER>

3 <ENTER>

to select option "3" (5-sec pulse + 11Hz pulse). You should see the 11Hz flashing greenLED start again after a few seconds.

7.8 Pulsar Data Acquisition Problems

Common problems encountered with the Pulsar data aquistion system are described in thepulsar observing documentation.

For convenience we have reproduced the text here.

7.8.1 Everything crashes

Occasionally, puma crashes for no obvious reason, bringing PMCTRL down with it. If thisoccurs in mid-observation (as it usually does), there are two possible ways to recover.

• The safe way is to restart PMDAQ and PMCTRL, manually eject the tape (by pressingthe eject button), remove and reinsert the tape. Then remount the tape and skip to EOD,restarting as normal. The down-side of this method is that you lose the data from theincomplete observation prior to the crash.

• A somewhat more risky method which saves the prior data is to restart PMDAQ andPMCTRL, leaving the tape in place. Then mount the tape and do a WEOF. It is possibleto proceed with normal observations from here, but this leaves the tape log in a bit of a messand file numbers will be wrong. Preferable is to then eject the tape, remove and reinsert

Chapter 7: TroubleShooting 57

it, mount it again and skip the required number of files. N.B. this will probably be onemore than stated for EOD, and so must be done by entering the number of files to skip onthe GUI (bottom right) and doing Tape Skip. File numbers should be correct after this.When the tape is next remounted, it may report a tape log error, but this is not normallya serious problem.”

7.8.2 puma dies

You may one day come across a bus error, or otherwise find that puma does not respond (e.g.,you can’t log on.) The CPU may have halted. The most straightforward way of recovering is topress the reset button on the front of puma (that’s the button on the upper left of the case, notupper right, which is the power button.) Note that for upwards of a minute it will appear asif nothing is happening on puma’s console (a vt320 across from the computer.) Don’t despair,eventually all should be well.

7.8.3 DMA timeout on puma

If puma has been rebooted, and maybe on other occasions, there can be a DMA timeout in thedigitiser interface to puma. This is indicated by a sequence counter error followed by a pumaINTERNAL ABORT and a general crashing sound. A fix which usually works is to power cyclethe digitiser. The power switch is a black switch at the back of the rack, mounted on the left wallof the rack adjacent to the digitiser. Another possible cause for this error is a broken connectionbetween the digitiser and puma - check the data cable and plugs.

7.9 ME or SERVO stops/crashes

After a mains failure, there are sometimes problems with the me (re)locking to the dish. Also,sometimes there is a rather large discrepancy (>150 arcsec) between the me and DISH andand showtel displays the message ’me BAD’. This last situation might be a fault with theObservatories 1PPS (1 Pulse Per Second) signal which is required by (amongst other things)the me computer (this is particularly bad and will require technical staff to fix).

For servo, problems will show themselves if showtel displays messages like “servo prob-lem?”, or “servo dead”. If the above fits your symptoms, then do the following:

• Go to the MCP and put the telescope under manual control.

• On the black keyboard/monitor in Rack 1, on the pkdesk console, type load me and hit<ENTER> OR load servo and hit <ENTER> - whichever process (me/servo) showtel iscomplaining about.

• pkdesk responds by telling you it is suspending proceedures and preparing to load theappropriate code.

•• (Staff Only) For me: Switch off the me computer at the rear panel switch for a few seconds,

then turn it on again.

• For servo in Rack 1: Execute the following switch sequence: HALT down, RESTART up(momentary self returning) and then, HALT up, RESTART up (again).

• Type go on the pkdesk computer to load the program code.

• pkdesk will display a stream of ’#’ to indicate loading.

• You should see the ’>’ on the upstairs me (or servo) console.

• If restarting pkdesk, the me and servo code restarts automatically.

• Now type ctrl p at the me (or servo) console to restart the program.

• Put the MCP back to computer control.

58 Parkes Users Guide

If after restarting, the me/servo screen is not updating correctly (a crash state is indicatedby an ’prompt) then you should:

• Put the MCP back to manual control.

• Type 173000G (me) or 1000G (servo) at the ’prompt (uppercase ’G’ is required.)

• You should now see the ’$>$’ prompt at which you restart the me software with a ctrl p.

• Re-write the screen with a ctrl p w.

• Put the MCP back to computer control.

If any of these proceedures fail to restart the me or servo, contact the technical staff or theCall–out person.

7.10 Safety Timer fails to reset

If after depressing the green reset button the safety timer fails to reset try pressing an a differentgreen reset button (upstairs control room, etc.). If this fails turn off the infra-red detector. Thedetector is located on the ceiling at the center column in the downstairs control room. It isisolated with a toggle switch located on the underside of the enclosure to which it is attached.Try to reset the timer.

If the timer still won’t reset try unplugging the two reset buttons on the control desk. Theoutlets for these buttons are under the desk. Try to reset the timer.

If all this fails call the Call–out person and Matt McFarland or Andrew Hunt.

7.11 SPD display shows rubbish

First try typing a to display the amplitudes. If this doesn’t work try exiting out of spd andrestarting. After the correlator has been reconfigured the spd display may have trouble redis-playing the data. A restart can fix this. If that doesn’t solve the problem, then it is symptomaticof a more serious problem. Try stopping the observation and reprograming the correlator.

Chapter 8: Appendicies 59

8 Appendicies

8.1 Trainers Guide to Training Observers

Below are some of the important procedures which should be explained to a new observer. Italso provides an example or two of some of the types of failures which may occur.

Before going through these proceedures, ask the observers to read the Parkes ObservatoryUser Guide, Chapters Four and Five.

As you are going through the telescope indicate what all the rooms and levels of the telescopeare and there purpose to the functioning of the telescope.

The checklist is:

• Usernames, Passwords, Door Combination

Check the observer knows relevant usernames and new passwords (if they have changed).Also see if they have a NEXUS account, but if not tell them the visitor username andpassword.

Also, check they know the door combination to gain access to the tower.

• Computing Resources

Tell the observer that computing equipment for non-observing people is available in theuser room in the Opera House and Upstairs Control Room (network connection for laptopsis also available in both areas).

The scheduled observer has priority on machines in the control room.

Non-CSIRO staff should use the Pink Cables to plug ther laptops into. This provides limitedaccess to the internal network.

If the observer has a laptop, check to make sure their wireless network card (if present) isturned OFF.

• Quarters

Make observers aware of Quarters breakfast, lunch and dinner times. If they wish to have abreak for lunch, contact either John Sarkissian or Stacy Mader who will be happy to relievethem for a while.

• winds

Show the observer the winds display - data for 2 hours. Each bar represents 120 seconds.The minimum is the average over the last 120 seconds and the maximum is the peak (orgust) in the last 120 seconds (which is why you sometimes see a plateau). Wind stowalgorithms operate on both average and peak values (see Table 4.1 and the Maintenancedisplay on servo; CNTRL P M).

The winds display is critical for unstowing from a wind park. Wind Parks are automaticand SERVO will not allow re-observing to commence until at least 10 minutes has passed.

• SHOWTEL

Explain the SHOWTEL display. Show observers how to switch between coordinate systems.

• Safety Timer and Infrared Detector

Show observer limits of the infrared detector in the control room.

For the Safety Timer, there are three main buttons. Green reset button, press within 14min, 40 sec, otherwise the alarm sounds. The yellow button is for DCP contact, this mustbe checked when the DCP phone is moved or when the DCP goes to sleep by the towerobserver pressing the DCP Button and the DCP then returning the call. DCP phone onlyrequired if one person in the tower. Explain what happens if 25 minutes passes beforeobserver gets to it or when 35 minutes is reached.

60 Parkes Users Guide

Press the yellow button if you are tired and need to locate the DCP quickly.

Press the red button if there is a fire or if there is a the mains power failure and the generatorwon’t start.

• Location of Drive Computers

Show the observer the location of servo, me and pkdesk. Show cheat sheet on how toreboot each if required. Note if there is an issue with the ME PDP11, either staff (if duringbusiness hours) or the call-out person should be notified.

• Manual Control Panel (MCP)

Show the observer the MCP. Show the user how to un-stow and stow the telescope. Explainthe difference between stow and park. Get the user to un-stow and stow the telescope, getuser to use the clear call system for telling people the telescope is moving. Explain thesoftware and hardware limits on the display (top hardware limit light, bottom softwarelimit light). Explain the north and south wraps (limit with cables). 15 minutes to do fullazimuth and 6 minutes to reach the zenith.

Explain white and yellow safety tags. Stress that the telescope should not be moved if tagon MCP. Only the person who owns the tag can remove their tag.

• servo & me Terminals

Show observer servo/me terminals on computer near the MCP. Show that to select awindow, the user must click on the window they want before entering commands.

With servo, explain computer instructions with park or stopping the dish. Other com-mands are on laminated sheets.

With me, only Andrew and Tim should do anything with this. Show the observer the meroom and problems with not locking due to birds, moths or other insects.

Show observer the Monica GUI indicating Generator/Main status.

There are three types of power failures.

1. Mains fails and returns almost immediately. Only have to reset the alarms near theMCP and the UPS room in the diesel shed. Telescope drives will also be disabled and mustbe re-enabled to restart observing.

2. Mains fails and the Generator doesn’t kick in straight away, this may take up to 6minutes. You still need to reset the alarm near the MCP.

3. Mains fails and the Generator doesn’t kick in. Ring Matt McFarland and the call-out person. Take the generator hut keys to generator hut. Go over and determine if thegenerator has been left in ’manual’, and if so, press the ’automatic’ button.

Remember to reset the UPS alarm, press the reset alarm, then the test alarm, then resetalarm button. This will set off the alarm in the upper control room next to the MCP,remember to reset it again.

• Fault Reports

Show the observer the web based fault, observer and wind park reports. Explain that thesereports should be filled out and stress importance.

• Call-out Roster

Show the observer the call-out board. Purpose of the call-out person, how to contact them.If unable to contact call-out person, try calling the friend or anyone from the telescope.Details in blue phone book.

• Important Notices amd Documentation

Indicate to the observer possible "Important Notice" which may be displayed, including thewhiteboard, notices above computers and the pin board.

Show the observer the location of the Manuals and Documentation in the control room andon the web.

Chapter 8: Appendicies 61

• Examples of Failure

If there is a Fire, the fire exhausters are located on the walls, they are not water based dueto electrical equipment. If you are unable to put out the fire, try proceeding to the MCPto stow or park the disk, call the call-out person to ring Fire Brigade.

If dish is low and storm comes in quickly and there is a power failure and the generatorwon’t start, call Call-out person then one of Mal Smith, Matt McFarland or Brett Preisig.

Stress that if they are unsure of any procedures associated with operating the telescope tocontact the call-out person.

8.2 Site Alarms

The Observatory has a number of alarms the observer should be aware of.

8.2.1 Tower:

• Zenith Warning Siren indicates the Telescope is entering/exiting the Zenith limit (∼ 1.2degrees).

• DC amplifier level alarm; upstairs control room rack #3.

• UPS alarm; main control room and upstairs control room near the Manual Control Panel(see Section 4.8.8 [Resetting the UPS Alarm], page 39).

• Safety Timer and Auto dialer (see Section 3.2.2 [SAFETY TIMER], page 16).

• Fire alarms (electronic sounder); above Fire indicator panel on ground floor (this includesthe emergency access alarms for the emergency exit door in the base of the tower and fireescape ladder).

• Aerated Waste Management pump/air failure alarm; centre column on ground floor (elec-tronic sounder).

8.2.2 Mechanical Workshop

• The Opera House and Workshops have an aerated waste management system pump/airfailure alarm located in the mechanical workshop near the welding bay.

8.2.3 Maser Hut

• Temperature alarm (sound/blue flashing light).

8.2.4 Generator Hut

• Green/Blue/Red lights indicating Mains/Generator suply status (see Section 4.8 [PowerSupply via Mains/Diesel/UPS], page 35).

• Diesel sump pump failure alarm; Flashing light and siren mounted on the corner of thegenerator hut above the Green/Blue/Red lights.

8.2.5 Visitor’s Discovery Centre and Cafe

• Green/Red/Blue lights on VDC roof; these are lights to indicate the current status ofthe VDC airconditioners. The green light on each unit comes on at power up with theevaporator fan contactor. The red and blue lights switch on with the two (stage 1 and stage2) compressor/compressor fan contactors. For certain types of observation (ie Pulsar), itmay be possible to observe (and identify) RFI when the contactors are activated.

• Duress almarm; under windows, on the North side (electronic sounder and blue strobelight). The duress alarm also services the Caf.

• Cafe sump alarm pump failure. Red flashing light and siren adjacent to the Cafe sump.

62 Parkes Users Guide

• Visitor’s Discovery Centre Aerated waste management system pump failure alarm, an or-ange flashing light and an electronic sounder located in the waste management enclosure.

• Fire Alarm; speaker-type sounders in the ceiling throughout buildings.

8.2.6 Opera House

• Fire alarm; electro-mechanical bell, outside the main entrance.

• DCP bell outside reception (see Section 3.5 [Definitions], page 20).

• Visitor’s Discovery Centre duress alarm extension; siren and blue flashing light above thefire isolation board.

8.2.7 Woolshed

• Fire alarm; electro-mechanical bell, outside West entrance.

• DCP Bell in meal room (see Section 3.5 [Definitions], page 20).

8.2.8 Quarters and Flat

• Fire alarm; Electro-mechanical bells both inside the Quarters hallways and outside theQuarters and Flat kitchen.

• Bioseptic pump/air failure alarm located on the dinning room wall.

• DCP bell in Quarters foyer and the Flat (portable unit; see Section 3.5 [Definitions],page 20).

• Kitchen sump pump failure alarm; Electric horn, South-West corner of building (outsideConference room).

• There is an orange flashing light on the carport at the Quarters to indicate the pressurebooster/fire pump is running.

• Aerated waste management system pump/air failure alarm; located in The Flat foyer.

Index 63

Index

55.7 MHz ripple . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

AApplying for Observing Time . . . . . . . . . . . . . . . . . . . . . . 7ASAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45, 46, 49ASAP,linefinder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50ATOA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Azimuth and/or Zenith Drives Disabled . . . . . . . . . . 54

BBlock Control Computers . . . . . . . . . . . . . . . . . . . . . . . . 53Booking Your Accomodation . . . . . . . . . . . . . . . . . . . . . . 5

CCall–out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Call-out Response to Alarm . . . . . . . . . . . . . . . . . . . . . . 19Clear Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18, 20command examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Conversion System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Correlator issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Correlators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Current Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Current Stow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

DDCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21DCP Duties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19DCP Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21DCP Response to Alarm . . . . . . . . . . . . . . . . . . . . . . . . . 19DFB issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Driving Rates, Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26DUCHAMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

EEMERGENCY CALL-OUT Person . . . . . . . . . . . . . . . 21Emergency Situations . . . . . . . . . . . . . . . . . . . . . . . . 18, 22Error Detector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Ggridzilla . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Llivedata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

MMaster Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29me . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26, 28, 57ME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Media Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50MIRIAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Monitoring Power - Monica . . . . . . . . . . . . . . . . . . . . . . 35

Multibeam, Wide-band Correlator issues . . . . . . . . . 53

NNon-standard situation/procedure . . . . . . . . . . . . . . . . 22

OObservatory Contact Details . . . . . . . . . . . . . . . . . . . . . . . 6Observer Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Observers Quarters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Observing Checklist DOWNSTAIRS . . . . . . . . . . . . . . 41Observing Checklist UPSTAIRS . . . . . . . . . . . . . . . . . . 41Observing Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Observing Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7One in the Tower . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Operator Duties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15operfcc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

PParkes, longitude & latitude . . . . . . . . . . . . . . . . . . . . . . . 3pkdesk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54pmdaq . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Power failure: Brief mains glitch . . . . . . . . . . . . . . . . . . 36Power failure: Generator starts automatically . . . . . 36Power failure: Mains Return . . . . . . . . . . . . . . . . . . . . . . 37Power Supply via Mains/Diesel/UPS . . . . . . . . . . . . . 35Pre–empting an outage . . . . . . . . . . . . . . . . . . . . . . . . . . . 37puma . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

RReceiver Calibration Signal . . . . . . . . . . . . . . . . . . . . . . . 10Receiver Fleet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Receiver Translator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Resetting the UPS Alarm . . . . . . . . . . . . . . . . . . . . . . . . 39RFI Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7rpfits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

SSafety Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Safety Timer fails to reset . . . . . . . . . . . . . . . . . . . . . . . . 58Schedule Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Sensitivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8servo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28, 32, 57Severe Power Failure - no mains or generator . . . . . 37Signal Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12spd displays rubbish . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58SPD User Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Standing Wave Reduction . . . . . . . . . . . . . . . . . . . . . . . . 13Storm Stow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Stowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Stowing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22, 33Surface Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Switching modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

64 Parkes Users Guide

TTelescope Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1The Call–out person . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25The Parkes RadioTelescope . . . . . . . . . . . . . . . . . . . . . . . . 3Transport to the Observatory . . . . . . . . . . . . . . . . . . . . . . 4

UUnstowing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23UnStowing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

VVisitors Centre and The Dish Cafe . . . . . . . . . . . . . . . . 5

WWeather and wind restrictions . . . . . . . . . . . . . . . . . . . . 32

Weather restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Wind Park . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

winds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32, 59