public:meetings:2010_03_23_ilto

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:meetings:2010_03_23_ilto [2010-04-02 14:34] – Harm Munkpublic:meetings:2010_03_23_ilto [2017-03-08 15:27] (current) – external edit 127.0.0.1
Line 1: Line 1:
-====== ILTO meeting March 23, 2010 (ILT Technical Operations) ======+====== ILTO meeting March 23, 2010 (ILT Operations) ======
  
-The ILT Technical Operations meeting is held at the start of a LOFAR observing semester. The purpose of the meeting is to discuss operations procedures for the ILT, covering all aspects from observation scheduling to station maintenance. The audience for this meeting are (technical) personnel involved in running and maintaining the station. +The ILT Operations meeting is held at the start of a LOFAR observing semester. The purpose of the meeting is to discuss operations procedures for the ILT, covering all aspects from observation scheduling to station maintenance. The audience for this meeting are (technical) personnel involved in running and maintaining the station. 
  
 The first meeting was held on March 23, 2010, at ASTRON in Dwingeloo. At this meeting, roll-out issues were discussed as well, as several international stations were either under construction or to be constructed. The first meeting was held on March 23, 2010, at ASTRON in Dwingeloo. At this meeting, roll-out issues were discussed as well, as several international stations were either under construction or to be constructed.
Line 14: Line 14:
  
 {{:public:meetings:lofar_at_nancay.pdf|Presentation by I. Thomas on the LOFAR station under construction at Nancay (France)}} {{:public:meetings:lofar_at_nancay.pdf|Presentation by I. Thomas on the LOFAR station under construction at Nancay (France)}}
 +
 +{{:public:meetings:lofat_at_effelsberg.pdf|Presentation by W. Reich on the LOFAR station at Effelsberg (Germany)}}
  
 {{:public:meetings:lofar_at_garching.pdf|Presentation by B. Ciardi on the LOFAR station at Garching/Unterweilenbach (Germany)}} {{:public:meetings:lofar_at_garching.pdf|Presentation by B. Ciardi on the LOFAR station at Garching/Unterweilenbach (Germany)}}
Line 45: Line 47:
  
 The following allocation of time for individual stations will be used: The following allocation of time for individual stations will be used:
-• 10% time for maintenance (~16 hrs/week, the equivalent of two workdays). In this mode, the station is controlled by ASTRON’s RO, but the local station controller can be requested to run tests on the station. +  * 10% time for maintenance (~16 hrs/week, the equivalent of two workdays). In this mode, the station is controlled by ASTRON’s RO, but the local station controller can be requested to run tests on the station. 
-• 90% time available for +  * 90% time available for 
-• 81% time for array observations. In this mode, the station is controlled by ASTRON’s RO, and all data flows to CEP +  * 9% time available for stand alone use (the name “private local use” is used in the presentation, but this term might be confusing.) In this mode, the station is disconnected from CEP: data is stored locally at the station. 
-• 9% time available for stand alone use (the name “private local use” is used in the presentation, but this term might be confusing.) In this mode, the station is disconnected from CEP: data is stored locally at the station.+
 All station use, including stand-alone mode, is scheduled. (See “Station control” for targets of opportunity.) If stand-alone mode can be scheduled for all stations at the same time is doubtful. Experience will show if and how stand-alone mode is to be scheduled. All station use, including stand-alone mode, is scheduled. (See “Station control” for targets of opportunity.) If stand-alone mode can be scheduled for all stations at the same time is doubtful. Experience will show if and how stand-alone mode is to be scheduled.
 If during an array observation, or during a maintenance period a station is not used, it can on request be made available for stand alone use. This extra stand alone use is on top of the allocated 9%: in other words, it will not be subtracted from the allocated 9%. If during an array observation, or during a maintenance period a station is not used, it can on request be made available for stand alone use. This extra stand alone use is on top of the allocated 9%: in other words, it will not be subtracted from the allocated 9%.
-Station Control+== Station Control ==
 Station control resides either at ASTRON’s RO or at the local station controller. Control is always handed over from the current controller to the new controller. Station control is never taken over. Station control resides either at ASTRON’s RO or at the local station controller. Control is always handed over from the current controller to the new controller. Station control is never taken over.
 This protocol is also used for target of opportunity (ToO) observations. The requestor must contact the current station controller to request the handover of station control. If the current station controller cannot be contacted in time, the station cannot be used for the ToO observation. Note that both ASTRON’s RO and a local station controller can request a station for ToO observations. This protocol is also used for target of opportunity (ToO) observations. The requestor must contact the current station controller to request the handover of station control. If the current station controller cannot be contacted in time, the station cannot be used for the ToO observation. Note that both ASTRON’s RO and a local station controller can request a station for ToO observations.
Line 60: Line 62:
  
 == Scheduling == == Scheduling ==
-Scheduling is done is different stages. The first schedule is computed at the start of an observing semester, resulting in an overview of projects that will be executed during that semester. Some observing constraints can be taken into account at this stage (rise-set times, day-night observing, maintenance periods).+Scheduling is done in different stages. The first schedule is computed at the start of an observing semester, resulting in an overview of projects that will be executed during that semester. Some observing constraints can be taken into account at this stage (rise-set times, day-night observing, maintenance periods).
 The final stage of scheduling is done on a weekly basis, and possibly even daily, additionally taking LOFAR system availability constraints (e.g. station statuses), capacity (e.g. long term storage), and stand-alone mode requests into account. The final stage of scheduling is done on a weekly basis, and possibly even daily, additionally taking LOFAR system availability constraints (e.g. station statuses), capacity (e.g. long term storage), and stand-alone mode requests into account.
 ILT and station status ILT and station status
Line 85: Line 87:
 == ILT Operations and maintenance cookbook == == ILT Operations and maintenance cookbook ==
 Based on the experience gained with station construction, having documents available with best practices is very valuable. We will start a comparable collection on station operation and maintenance in a cookbook on the LOFAR Wiki, accessible from the operations page. Based on the experience gained with station construction, having documents available with best practices is very valuable. We will start a comparable collection on station operation and maintenance in a cookbook on the LOFAR Wiki, accessible from the operations page.
- 
  
  
  • Last modified: 2010-04-02 14:34
  • by Harm Munk