vgosDb is now installed on ops7, through the nuSolve package (ftp://gemini.gsfc.nasa.gov/pub/misc/ slb/nusolve-latest.tar.gz). To build vgosDbMake, it was first necessary to install the HOPS package and then link it in the configure stage.

wget ftp://gemini.haystack.mit.edu/pub/hops/hops-3.14-1729.tar.gz
tar zxvf hops-3.14-1729.tar.gz
cd hops-3.14/
./configure 
make 
sudo make install

wget ftp://gemini.gsfc.nasa.gov/pub/misc/slb/nusolve-latest.tar.gz
tar zxvf nusolve-latest.tar.gz
cd nusolve-0.4.2/
./configure --with-qt-dir=/usr/local/Trolltech/Qt-4.8.6/ --with-hops-dir=/home/observer/i686-3.14/
make 
sudo make install

The next steps are setting up each of the vgosDbMake, vgosDbCalc, vgosDbProcLogs and nuSolve. Run each without any arguments and update the paths as relevant. For ops7, most of the apriori files, etc, are under /data/vlbi/.

vgosDbMake requires access to the master TXT file, expecting it to be found under /data/vlbi/master. To create a VGOS database, run

vgosDbMake /mnt/magilla/AUSTRAL/aua009/1609/

Read the output messages carefully - you may notice a complaint about it not finding the correlator report file. It expects to find this under the /mnt/magilla/AUSTRAL/aua009/control/ directory and used this to get the experiment label. If it is not present,

To deal with an ad-hoc session not in the master file, you will need to set the output database name explicitly.

vgosDbMake -d "16DEC02XT"  /mnt/magilla/AUSTRAL/ds337/6337/

This