Bugs in binary writing/reading of parameters

[MatthewWhiting]

There's a problem here, in param.cc:

    if(this->flagFDR){
      outfile.write(reinterpret_cast<const char*>(&this->alphaFDR), sizeof this->alphaFDR);
      outfile.write(reinterpret_cast<const char*>(&this->FDRnumCorChan), sizeof this->FDRnumCorChan);
      if(this->beamAsUsed.origin()==PARAM){
	outfile.write(reinterpret_cast<const char*>(&this->fwhmBeam), sizeof this->fwhmBeam);
	outfile.write(reinterpret_cast<const char*>(&this->areaBeam), sizeof this->areaBeam);
      }
    }

The state of the beam doesn't get written to the binary file, so the reading function will not know about it. Need to fix

[MatthewWhiting]

Also

outfile.write(reinterpret_cast<const char*>(&this->smoothEdgeMethod), sizeof this->smoothEdgeMethod);

should be written with the string interface.

[MatthewWhiting]

Also, would be good to write out the full Detection class, rather than just the Object3D information (which really means just the pixel locations). This way we could just load in the binary catalogue and not have to worry about looking at the ascii one, unless we wanted to re-parameterise.

[MatthewWhiting]

[1345] fixes the original problem on this ticket, as well as adding in the flagUserGrowthThreshold to the binary file.

[MatthewWhiting]

Ticket #218 has been created to handle the Detection class output to binary files, so this one can be closed.