|Description||eVLBI on Cir X-1|
|DAS Mode||vsop.pro (telescope)|
This is an eVLBI experiment. Do NOT run the disk recorders!
Connect DAS directly to VSIC
Hobart wire up as per above scheme (is VSOP profile, Rcp&LCP). Two channels will be dropped during evlbi transfer (to get rate to 128 Mbps).
vsib_record must be run at by hand currently. Log onto each recorder as vlbi and run the command
> vsib_record -t 36000s -W <TCP WINDOW> -p <PORT> -H pkvsi2-ext -o <TELESCOPEID>
|Telescope||TCP Window (kB)||Port||ID|
> vsib_record -t 36000s -W 512 -p 52102 -H pkvsi2-ext -o At
For Hobart, compression needs to be used to get the rate to 128 Mbps. use compression
-c oxox to get the lower frequency, dual pol. E.g.:
> vsib_record -t 36000s -W 512 -p 52102 -H pkvsi2-ext -c oxox -o Ho
On pkvsi2, go to /import/bd1/evlbi/tests/vt11c3/. Edit the .input file to have the correct start time (in the first table), and start the correlator with:
mpirun -p4pg p4pg.pkvsigateway /home/vlbi/evlbi/correlator/mpifxcorr/src/mpifxcorr /import/bd1/evlbi/tests/vt11c3/<input file name>
Wait for the startup messages to scroll through and stop - near the end there should be some saying “waiting for connection”. Once the correlator is waiting you can start the vsib_record processes at the observatories. The start time in the correlator input file should be after the time you get all these going.
If you want to add an extra antenna (eg hobart) to the array, you'll need to add an extra line to p4pg.pkvsigateway. Dupplicate the second line. For this instance you'll obviously also need a different correlator input file. Similarly, if for some reason we want to drop an antenna, remove the second line from p4pg.pkvsigateway.