DIRECTIONS FOR PROCESSING MUTUAL EVENTS WITH LIMOVIE
by Dave Herald


August 7, 2009 ************************  Update

The LimovieAverage program is used to process measurements from Limovie to bin the measurements (to 
reduce noise) and normalise the measurements on the basis of a comparison object (to adjust for 
changes in atmospheric transparency over the course of an observation.) The program is particularly 
relevant for processing measurements of Mutual phenomena of Jupiter's satellites.

The ZIP file contains three files:
LimovieAverage.exe  - the program
LimovieAverage.chm  - the Help file
LimovieAverage.exe.config - a configuration file.

Unzip the files into a directory of your choice. To use the program, merely run LimovieAverage.exe.

It is assumed that you have the .Net framework V2 or greater installed on your computer. If you have 
Linux or Macintosh, the program will almost certainly run if you have MONO installed (although this 
has not been tested.)

Before using the program, READ THE HELP FILE! It explains a number of things you need to know to use 
the program correctly!

You may have to "unblock" the Help file in order for it to work properly.  To do so, right-click on the
File Name (it's the HTML file with the "?" in the file name) and go to Properties.  
In the lower right there should be a Box labelled Unblock.  Click that box and then Apply and OK.
You should now be able to Open the Help File. 



May 18, 2009    *****************************  Initial Directions
The first line is used to indicate whether PAL or NTSC is used. Also for whether Frames or Fields are measured. 
[I recommend frames be measured for these long events)

The second line is for when the CSV is from an integrated camera. When integration is occurring, you need to 
match the averaging to the integrated frames. This is to set the first frame of an integrated group. Note that 
it is zero-based. For example, if you were integrating 8 frames, and the first three frames of the CSV file 
were for a 'previous' frame, you would specify '3' here.

The third line specifies the number of frames in an integration. Set to 1 for a non-integrated video. 
[This is used to calculate the time to associate with each combined measure.]

The fourth line is to set the number of frames to be binned. If the input signal was an integrated signal, 
this should be the number of frames of the integration - or larger. If the video is non-integrated, you can 
select any value here.

The final line is to set the UTC of the read-out time of the first frame. The code will do the necessary 
subtraction to refer to the mid-time of the exposure allowing for binning frames in the code, and the output 
delay in the camera when integrating.

The code generates new CSV files in the same directory as the source CSV file, but with textual addition of 
'_binxx' where xx is the number of frames binned.

The columns in the CSV file that is generated are:
1. UTC of the middle of the bin
2. Average of the object measures in each bin
3. Average of the comparison object in each bin
4. = (2), adjusted by a 5-point running average of the values in (6)
5. = (3), adjusted by a 5-point running average of the values in (6)
6. = (3) divided by the overall average of the values in column (3).

For plotting purpose:
- for a raw data plot, use columns 1, 2 and 3
- for a plot corrected for variations in the comparison object, plot column 1, 4 and 5.

********************************************************