read_multi_gix.pl instructions (2008-12-19/maturun):
----------------------------------------------------

Note:
	More features are offered by the newer http://flux/cgi-bin/gixwrite.pl
	
Description:
	read_multi_gix.pl is used to automatically fetch .GIX files belonging 
	to a given date range from blazar and to process them into .dat files.
	The .GIX files can also be filtered by Contobs observer name.
		
	The program also reads calibration information and produces appropriate
	output files.
	
	It's advisable to run read_multi_gix.pl in a new directory so that you
	won't accidently append extra data to your old .dat files that fall into
	the processed date range.
	
	As with read_contobs_data.pl /data/ should also be mounted on the machine 
	that you process your .GIX files on; kurp is one candidate.
	
Usage:
	read_multi_gix.pl [-nw] [-nd] [-g]

	Option '-nw' skips warnings about existing .dat files in the current working
	directory.

	Option '-nd' skips downloading. Useful if you already have all the necessary
	.GIX files in your current working directory.

	Option '-g' prompts the user to specify .GIX-file versions that should
	be used; e.g. use 070504.GIX;1 and 070504.GIX;3, but skip .GIX;2

        '-c' option will copy .GIX-files from debian-contobs directory
        '/home/kurpitsa/contobs' and not from blazar
	
Details:
	As you first start the program, you'll be asked to specify starting
	date in YYMMDD-format after which you'll be asked for end date. This
	date information is used to fetch YYMMDD.GIX;* files from blazar.
	
	After specifying the date range read_multi_gix.pl will ask for Contobs
	observer name e.g. 'maturun', 'al' or 'mko' - what ever was entered to
	Contobs when one began the observations. If you answer 'ANY', then all
	.GIX files belonging to the date range will be accepted.
	
	read_multi_gix.pl will now start downloading the .GIX files and processes
	them with neo_read_contobs_data.pl extracting all the necessary information.
	
	You can press "Ctrl+C" at any time to abort the program while it's running.
	
	After processing the ending date, you'll be informed of the files that
	were just written.

Output files:
	'YYMMDD_to_YYMMDD_all.dat' contains all the observations including the
	calibration values.
	
	'YYMMDD_to_YYMMDD_all.dat.cal' is the same as above, but with CAL sources
	shown as separate measurements. This might ease comparing your paper log
	entries with the written .dat file. This .dat.cal file shouldn't be used
	for anything else (yet) since none of the old programs support this format.
	
	'YYMMDD_to_YYMMDD_all.cal' has only the calibration entries written to it
	in case you are only interested in those.
	
	'YYMMDD_to_YYMMDD_all.dat.bak' is the most traditional output file and has
	no information about the calibrations that were made during the measurements.
	
About the automatic calibration values:
	If there are no calibrations within 6h of a source measurement or all
	calibrations within that time have an error > 4.0, then no calibration value
	will be added to the YYMMDD_to_YYMMDD_all.dat for that target and a 'NoCal!'
	warning will be printed instead.
	
Known limitations:
	If a .GIX files has only calibrations in it, then those values can't be used,
	since Contobs doesn't store any timestamps for calibration measurements.

	tau values must still be added manually - at least for now.

Author and the person to send all those feature requests and bug reports to:
	maturun@kurp.hut.fi
	
P.S:
	Have fun! You can use:
	'grep -i dr21 YYMMDD_to_YYMMDD_all.dat > YYMMDD_to_YYMMDD_all.dr21'
	to avoid copy & pasting DR21 entries manually to a .dr21 file.