2. say i am working in the Graphics module with a chronology containing multiple
trees, and i export a composite to its own *.fhx file. when i retreive this file
and view it, it looks just like a chronology with only one tree. but i've
realized that the format of the actual fhx file is very different--just a list
of event years, useful for stuff like epoch analysis. what's interesting is
that the Statistics module still attempts to read the file (albeit incorrectly)
and spits out some wild results--completely erroneous data--it could be a good
way to randomly generate fire history information for instructional purposes!
anyway, what i'm trying to do is create four composite chronologies for four
different locations so i can statistically compare them in the Statistics
module. so i thought having a single "tree" for each site