2024 Session II (c242)

Stations

• Nn has pad N09
• Apex joining for the first time
• Ef is out

Observing Notes

• Fringe test was successful in detecting fringes between Nn, Pv, On, Ys, Mh.
• Pv stowed at ~07:15 UTC until scan 576, stopping again at 20:20 UTC, back at scan 743, then stopped after an hour.
• Nn stowed due to wind at 16:20 UTC and until 23:40 UTC(c242a)
• Apex out initially due to power failure, on source ~13:30 UTC
• Ys lost scans 209-222
• Oct 12 Nn stopped at 14:07
• Pv on sky since 14:30 UTC (scan 320).
• c242c/d Ys very foggy, cloudy
• Pv stopped due to strong wind at 19:45 UTC.
• Oct 13 Nn started with scan at 05:45 but had acquisition problems 07:30-08:30

APEX Module

APEX data are on BHC%0141 in CF502. In order to hand-carry GMVA data from APEX to Bonn, data were consolidated from two Mark6 modules (2 x 8 disks) onto a more readily transportable set of 8 loose disks. Data of one polarization are in the standard per-disk subdirectory 'data', data of the other polarization are in 'GMVA_slot2'.

To mount the "two modules" contained on BHC%0141, use:

d281
# assuming that BHC%0141 is in slot 1:
fuseMk6 -r '/mnt/disks/1/*/data' /`hostname -s`_fuse/1
fuseMk6 -r '/mnt/disks/1/*/GMVA_slot2' /`hostname -s`_fuse/2

During unrelated tests at MPIfR, unfortunately the filesystem metadata of 1 out of the 8 disks got erased. During a later trip to APEX the missing 'GMVA_slot2' files of that disk were copied out from the still existing module there and are now integrated back into BHC%0141. The missing 'data' files of that disk were less trivial to recover.

root@mark6-08: gmva2024_2> losetup -o $((512*2048)) /dev/loop1 /dev/sdh
root@mark6-08: gmva2024_2> xfs_metadump -g -f -o -w -a /dev/loop1 apex-module-intact-disk.xfs_metadump