Updating SVT online download code (e.g. stuff like svtsim_maps.c that is shared between offline svtsim library and online svtvme library)

• make desired changes in offline CVS, up through 'cvs commit'

• it is usually desirable to test changes by running some data through svtsim

• log into b0dap30

• setup cvs -qonline

• cvs checkout svtvme; cd svtvme

• or else do 'cvs update -d' in your own private existing svtvme directory

• source setup_local

• make ; make ppc

• this checks that you can compile the existing code

• make svtsim

• this merges offline CVS svtsim code into your working svtvme area

• make; make ppc

• let's see if it still compiles

• you may also want to try some more rigorous checks that the code is correct, e.g. reproducing the CRCs stored in some existing .mapset files, using crcmaps.py

• to do this, you can cksum the CRCs, as follows (say X='bmorg_1_2mm_CDFref_20020509003129')

• python python/crcmaps.py X | grep crc | cksum

• grep crc /cdf/code-common/cdfonline/svt_config/X.mapset | cksum

• cvs commit

• now the online CVS repository contains these changes

• you can view the history with cvsweb

• ~cdf_svt/svtvme_update_k5

• this logs in as cdf_svt, does a 'cvs update' in the real development svtvme library, and recompiles everything in sight

• note that the real SVT crates boot from this area, so if you screw up, and the SVT crates are rebooted, CDF can't take data