User Tools
operations:minutes2014_08_06
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.
| Next revision | Previous revision Last revision Both sides next revision | ||
|
operations:minutes2014_08_06 [2014/08/07 05:14] liza created |
operations:minutes2014_08_06 [2014/08/08 00:15] liza |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| 1. Resent experiments that were reviewed: | 1. Resent experiments that were reviewed: | ||
| - | R1635 | + | * R1635 |
| - | CONT1403 | + | * CONT1403 |
| - | CONT1405 | + | * CONT1405 |
| - | CONT1406 | + | * CONT1406 |
| - | CONT1410 | + | * CONT1410 |
| - | R4636 | + | * R4636 |
| - | R4637 | + | * R4637 |
| - | R1639 | + | * R1639 |
| - | R4643 | + | * R4643 |
| - | The recent AUSTs experiments are still awaiting correlation and will be reviewed as soon as available. Remasks: | + | The recent AUSTs experiments are still awaiting correlation and will be reviewed as soon as available. Remasks: |
| - | * Pointing: pointing offset should be <0.02 degree. If more, investigation should be done asap. Start the pointing procedure if time permits (to check pointing in other directions), log the offset & inform on-call person. If pointing fit repeatedly doesn't converge, dBBC is a likely culprit, especially at Yg. | + | * Pointing: pointing offset should be <0.02 degree. If more, investigation should be done asap. Start the pointing procedure if time permits (to check pointing in other directions), log the offset & inform on-call person. If pointing fit repeatedly doesn't converge, dBBC is a likely culprit, especially at Yg. |
| - | * RFI: if autocorrelation amplitudes look strange, it is likely to be caused by RFI, especially in the two last channels in the S band in Hobart. Report it. | + | * RFI: if autocorrelation amplitudes look strange, it is likely to be caused by RFI, especially in the two last channels in the S band in Hobart. Report it. |
| - | * Windstow: a substantial amount of data is lost due to an antenna that get stuck in the windstow position after the wind | + | * Windstow: a substantial amount of data is lost due to an antenna that get stuck in the windstow position after the wind calms down, please check the anemometer when stow is reported. How to get the antenna out of the stow: |
| + | |||
| + | On the pcfshb VNC session: | ||
| + | halt | ||
| + | disk_record=off | ||
| + | (just to make sure the recorder is stopped) | ||
| + | antenna=off | ||
| + | (should turn the drives off, check HMI on timehb) | ||
| + | terminate | ||
| + | (This will exit the field system software) | ||
| + | Then re-start the field system in a terminal with fs. Then in eRemoteCtrl: | ||
| + | proc=r1653hb | ||
| + | setupsx | ||
| + | antenna=open | ||
| + | antenna=operate | ||
| + | (check HMI and see if drives power up) | ||
| + | schedule=r1653hb | ||
| + | (schedule should start. Wait for next source command and see if antenna slews) | ||
| + | |||
| + | One may also need to open VNC session on timepc and manually switch drived off and on in HMI. | ||
/home/www/auscope/opswiki/data/pages/operations/minutes2014_08_06.txt · Last modified: 2014/08/08 00:23 by liza
Page Tools
