User Tools

Site Tools


lbaops:lbaobservingnotes:mk5emu

Differences

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

Link to this comparison view

lbaops:lbaobservingnotes:mk5emu [2015/12/18 16:38] (current)
Line 1: Line 1:
 +=====  eVLBI to JIVE =====
 +
 +For eVLBI to JIVE, setup the front end, DAS etc as normal - paying special attention to which DAS profile is needed (usually it is not the standard vsop profile). All control of the LBADR is done remotely from JIVE. To allow this to happen, a interface program needs to be run - mk5emu.pl. ​
 +
 +This just needs to be run on the appropriate LBADR machine (as vlbi). Simple run
 +
 + > mk5emu.pl
 +
 +cdisko is not needed, but can be left running to monitor the recorder and kill a transfer if something goes wrong. mk5emu can be started well ahead of time and left running. But it is not advisable to leave it running if you are using the LBADR for some other recording.
 +
 +The recording mode (bandwidths,​ channel selection) and so data rate is hardcoded into mk5emu.pl. To change you need to edit the perl script to change the vsib_record settings by hand. Refer to the vsib_record notes for a detail explanation.  ​
 +
 +The values which need to be changed are:
 +
 + my $chans = '​xxxx';​
 + my $bandwidth = 16;
 + my $vsib_mode = 3;
 +
 +
 +Typical settings would be:
 +
 +
 +| xxxx | 16 | 2 | 512 | Normal ATNF dual DAS 512 Mbps, 8 channel setting |
 +| xxxx | 16 | 3 | 256 | Single DAS 256 Mbps, 4 channel setting |
 +| oxox | 16 | 3 | 128 | 128 Mbps, 2 channel dual pol. Typically for Hobart |
 +| ooxx | 16 | 3 | 128 | 128 Mbps, 2 channel single pol (Rcp usually) |
 +| xxxx | 8 | 2 | 256 | 256 Mbps, 8 channel |
 +
 +
  
lbaops/lbaobservingnotes/mk5emu.txt · Last modified: 2015/12/18 16:38 (external edit)