This page should define sign conventions etc for PAVO@CHARA dual combiner operation. It has been attempted at least 3 times, but the sign convention hasn't been carefully recorded. What *should* occur is that + for the cart and + for the PAVO beamsplitters move the fringes in the same direction. e.g. If PAVO needs to move -1300 on the cart to center the fringes, then moving -1300 on the beamsplitters should be equivalent. This means that if you want to move the cart -1300 and still have fringes, you have to compensate by moving the beamsplitter +1300.

So... labeling the B1 cart offset for fringes B1_PAVO and B1_CLIMB etc...

If beam 1 is the fixed DL, then:
Move the PAVO B1 splitter 10*(B3_CLIMB-B3_PAVO)
Move the PAVO B2 splitter 10*(B3_CLIMB-B3_PAVO + B2_PAVO - B2_CLIMB)

If beam 2 is the fixed DL, then:
Move the PAVO B1 splitter 10*(B3_CLIMB-B3_PAVO + B1_PAVO - B1_CLIMB)
Move the PAVO B2 splitter 10*(B3_CLIMB-B3_PAVO)

If beam 3 is the fixed DL, then:
Move the PAVO B1 splitter 10*(B1_PAVO - B1_CLIMB)
Move the PAVO B2 splitter 10*(B2_PAVO - B2_CLIMB)


Attempt1: 090710 through 090714. CLIMB + PAVO. Only recorded the offset, and not clearly. The existence of foregrounds was definitely not recorded properly, but this (single-baseline) data could work with foreground_type=1
Attempt2: 091103. epsAur091103.html has some notes... but not much. Can not find any text files describing sign convention. The existence of foregrounds is only described in pavo_diary.txt on Mike's computer.
Attempt3: 100924. Finally, the delay cart offsets were put into the PAVO headers.