Permanent_Action_Items

Combined revision comparison

...

• Stations should make sure that the EVN status table is up-to-date:
  https://wwwhttp://old.evlbi.org/sites/default/files/shared/user_guide/EVNstatus.txt
• Stations should make sure that the SCHED catalogue information is up-to-date.
• Stations should keep current their information in the TOG wiki page showing the number and capacities of on-hand disk packs. Contact Rottmann to gain access.

...

• All stations should monitor Tcal during sessions. This can be done by using ONOFF.
• All stations should forward FS error log files to Himwich in the event of a crash, including details of what the FS was doing when the crash occurred.
• All stations should provide feedback on inidivual observations via the EVN Feedback facility based on Mattermost
  (http://oldhttps://www.evlbi.org/session/feedback.htmlarticle/feedback-system), by following links to the session and then experiment.). Feedback should be provided as soon as possible after an experiment, but at the most within 7 days of its completion. The reports should be short, accurate and quantitive. Comments should focus on any failures during the run that may lead (or have led) to loss of data.
• Observing logs are to be deposited on the VLBEER server (vlbeer.ira.inaf.it) within 72 hours after the completion of an experiment, as soon as possible (< 24 hours after the experiment) in the case of eVLBI observations.
• If a station fails to observe a given experiment for which it is scheduled, a dummy log should be posted on VLBEER (see http://www.oso.chalmers.se/evn/dummy.log for an example).
• Log name convention. All log names should be in lower-case. For observing logs the naming convention is: <project><station>.log, The name of an EVN experiment or project is defined within the block schedule.  For example, the observing log from Noto (nt) for project number "GY001B" is to be named: gy001bnt.log
• All stations: report Mark5C bugs to Ruszczyk,

...

• All stations should look at pipeline results available from the EVN data archive pages at JIVE, in particular amplitude corrections found by selfcal on strong, compact calibrators. JIVE support scientists should include a comment on the quality of amplitude calibration results, especially to indicate cases where a problem may have occurred and the amplitude correction factors are unreliable.
• NME calibration files should be made available as early as possible. All stations should look at NME reports sent by JIVE. NMEs should be pipelined as early as possible and email sent to EVNtech when the results are available, to ensure feedback is provided well in advance of the next session.
• Stations must aim to produce ANTABFS-,- and RXG-files within 2 weeks after the end of a session.  JIVE should inform the TOG Chair of any problems, so that Directors can be asked to prioritise calibration if insufficient time is available at stations. The naming convention for the ANTABFS-file is: <project><station>.antabfs e.g. gy001bwb.antabfs
• For eVLBI, RXG-files from the previous session can often be used. LOG- and ANTABFS-files for eVLBI experiments should be made available at vlbeer as soon as possible (< 24 hours after the experiment) as rapid analysis is often a high priority for these experiments.

...

Other changes:

1. /body/ul[9]/li/a/@class: "external" ⇒ " external"
2. /body/ul[9]/li/a/@href: "http://old.evlbi.org/user_guide/EVNstatus.txt" ⇒ "https://www.evlbi.org/sites/default/files/shared/EVNstatus.txt"
3. /body/ul[9]/li/a/@title: "http://old.evlbi.org/user_guide/EVNstatus.txt" ⇒ "https://www.evlbi.org/sites/default/files/shared/EVNstatus.txt"
4. /body/ul[11]/li[3]/a/@class: " external" ⇒ "external"
5. /body/ul[11]/li[3]/a/@href: "https://www.evlbi.org/article/feedback-system" ⇒ "http://old.evlbi.org/session/feedback.html"
6. /body/ul[11]/li[3]/a/@title: "https://www.evlbi.org/article/feedback-system" ⇒ "http://old.evlbi.org/session/feedback.html"