User Tools

Site Tools


operations:starting_monitoring

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

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
operations:starting_monitoring [2012/06/21 19:06]
Warren Hankey [Starting and Monitoring IVS sessions]
operations:starting_monitoring [2012/07/25 23:34] (current)
Jamie McCallum
Line 13: Line 13:
 (As a backup, pmSTALM can be used but it checks for fewer error conditions. This is described [[operations:​documentation.pmstalm| here]].) (As a backup, pmSTALM can be used but it checks for fewer error conditions. This is described [[operations:​documentation.pmstalm| here]].)
  
-At least 5 min prior to to the scheduled start, start the schedule with e.g. <​code>​schedule=r4447hb</​code> ​as usualNote: do NOT specify a start line number. Unless you try to start late within five minutes of the scheduled start and get errors like;  m5 -900 no scans; m5 -900 not while recording or playing; m5 -900 can't get device info.(The Mk5 is looking for the previous scheduled scan to check, which doesn'​t exist.) This results in the next scheduled recording ​not working. In this case start schedule with line <​code>​schedule=r4447hb #​1</​code>​)+For Hobart and Katherine, start the schedule with e.g. <​code>​schedule=r4447hb</​code> ​if there is longer than 5 minutes until the nominal start of the scheduleFor Yarragadee, ALWAYS ​start the schedule with <​code>​schedule=r4447yg,#​1</​code>​This is necessary because the snp file has been edited to deal with the transmission stows which confuses the fs.  
 + 
 +Unlessyou try to start late within five minutes of the scheduled start and get errors like;  ​//m5 -900 no scans//;// m5 -900 not while recording or playing//;// m5 -900 can't get device info//. The mk5 is looking for the previous scheduled scan to check, which doesn'​t exist, and can't start the next scheduled ​scan recording. In this case start schedule with start line number ​<​code>​schedule=r4447hb,#​1</​code> ​Otherwise: do NOT specify a start line number.
  
 [[operations:​startmessage|Then send a start message to IVS]]. ​ [[operations:​startmessage|Then send a start message to IVS]]. ​
/home/www/auscope/opswiki/data/attic/operations/starting_monitoring.1340305600.txt.gz · Last modified: 2012/06/21 19:06 by Warren Hankey