The ultra-rapid EOP measurements use either modified IVS schedules (with Hobart in "tag-along" mode) or bespoke schedules. In either case, the usual slogit procedures can be used but you should make sure that the correct skd file is in /vlbobs/ivs/sched/ on ops-serv2 before starting & make sure it doesn't get overwritten by downloading the unmodified schedule.

Prepare the scheduLe and procedure files as usual but make sure that checkmk5 will not attempt to generate autocorrelations, and that preob and postob procedures look like this:

<code>
define  checkmk5      00000000000x
"sy=/home/oper/bin/auto_cor_check_web_1bit_8MHz_hb.sh &
"scan_check
"mk5=get_stats?
"mk5=status?
enddef
define  preob         00000000000x
onsource
disk2file=abort,,
!+5s
scan_check
mk5=get_stats?
mk5=status?
systemp12
mk5=dot?
clkoff
maserdelay
enddef
define  postob        00000000000x
scan_check
!+3s
sy=/home/oper/bin/data2vortex.sh &
clkoff
maserdelay
enddef
</code>

Also check that /home/oper/bin/data2vortex.sh is going to do the right thing, check that the directory on vortex is mounted on mk5hb.