Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.apo.nmsu.edu/Telescopes/ARCSAT/Operations/closure.html
Дата изменения: Sat Jan 18 01:20:27 2014
Дата индексирования: Sun Apr 10 00:31:28 2016
Кодировка:

Поисковые слова: п п п п п п п п п п
APO Telescope Documentation


 

 
Home
Operations
Observing Aids
Observing Schedule
Public Outreach
Publication Acknowledgement
Telescope and Instruments
User's Manual (TBD)

Archive PT Documents (TBD)
Archive Science Programs (TBD)
 

 

CLOSURE OF THE ARCSAT DUE TO HAZARDOUS
OBSERVING CONDITIONS

These policies are consulted whenever there are questions or concerns for closing the enclosure due to hazardous conditions or situations.

Summary:

  • telescope operations will be suspended whenever conditions pose a risk to facilities or personnel;

  • the Chief Telescope Engineer has full responsibility and sole authority to make this decision. This may include making subjective assessments of the degree of risk;

  • attempts to change the decision of the Chief Telescope Engineering are a violation of the Observatory safety rules and will not be tolerated; and,

  • observatory management will discuss related policy concerns or suggestions at an appropriate time, but will not consider appeals nor intervene in specific decisions of the Chief Telescope Engineer.

Policy: Operation of ARCSAT shall be suspended whenever, in the opinion of the Chief Telescope Engineer, weather, atmospheric conditions, signs of imminent mechanical malfunction, or any other situation exists which poses a risk to either the facility or on-site personnel.

This policy will be enforced conservatively, i.e., even though it may be probable that operations could be continued safely, the telescope will be closed unless the risk is considered negligibly small by the Chief Telescope Engineer.

Rationale: The long-term scientific return from ARCSAT and associated facilities requires avoiding equipment damage in the pursuit of short-term scientific goals. Also, the need to provide a safe working environment is self-evident. Differencse of opinion on telescope closure usually results from situations in which the danger seems relatively small. However, our operational procedures must consider the long-term accumulated risk and be appropriately conservative.

Policy: The Chief Telescope Engineer has full responsibility and sole authority to suspend operations for the reasons described in the previous policy.

In some instances, measurable quantities (e.g., wind speed) and preset limits will guide such decisions (these quantitative closure limits are listed on the APO Weather Status web pages). In many circumstances, an informed but somewhat subjective judgement will be necessary. Regardless of their position within ARC, academic rank, or other qualifications, those scheduled to use the telescope are unable to overrule the Chief Telescope Engineer or "assume responsibility" for such decisions themselves.

Rationale: Our policy is consistent with practices at other major observatories, which recognize and protect against the possibility of conflicts of interest.

Policy: Users of ARCSAT must not attempt to influence the Chief Telescope Engineer to continue telescope operations which are or might be suspended due to safety concerns.

This prohibition is to be interpreted very broadly; polite expression of differing opinion, angry argument, extended musings on the unfortunate consequences of the lost observing time, continued expression of disappointment, frequent requests to check for possibly improved conditions and so forth are all included in this ban.

Rationale: It is hazardous to have the decisions of the Chief Telescope Engineer influenced in the direction of taking greater risks in marginal situations; the variations in people's personalities, levels of self confidence and so forth are such that this might happen in some cases.

For changes or edits, contact:

Project Director: Suzanne Hawley (slh/astro.washington.edu)
Chief Telescope Engineer: Bill Ketzeback (bketzeba/apo.nmsu.edu)

 

 

for questions or comments contact archive server