#This is the second hypothesis as to why there are some files with zero bytes, and wheather it is real data erased, or just superfluous zero byte files.

# Our model is that the camera worked, but did not sync.  While the camera was chugging away, control C was pressed, and another picture taken.  The second picture also did not work, and produced no output.

#To model the successful picture we simply create pork.ppm
# For now we assume it is zero bytes.
`touch pork.ppm`;
#Now we run a script (hyp2.pl) that takes a command line parameter representing the length of sleep instead of taking a picture.  For this model we will always use zero.
`./hyp2.pl 0`;
#Now we check if a zero byte file was produced in the three output locations.

# RESULTS

#It was found that a zero byte output was produced, and zgv gave an error as no picture was available.  
#This hypothesis seems very likely, as we were control c'ing a lot of pictures that didn't sync.  If the next try worked, it would overwrite the 0 byte pork.ppm file and work normally. 
# However if the next picture failed, it would create a zero byte file.  We would expect this to happen when the radios were far away, but not everytime, because the camera produces a zero byte file sometime into its calculation.
# The camera would have to be examined to determine what happens when during a shot.

#CONCLUSION
#It seems likely this was the problem, and so it does not represent a loss of information.