Closed kmader closed 9 years ago
@kmader Looks good to me. Do you need testCrossCorrelation
to be public
, though? It's still private
in your patch.
@StephanPreibisch Any objections to merging?
I had made it static so it could be accessed by other static methods, but it could be made public as well. I guess ideally the mpicbg.stitching
are the functions we should be using, but the PairWiseStitchingImgLib
is still based on imglib1
@kmader So you don't need to call testCrossCorrelation
from your own code, then? I was assuming you did, since you mentioned it by name in the PR summary. My general advice would be to make public only those methods you actually need to access from your code, since each public method is a commitment to backwards compatibility and makes the code structure more "rigid."
Particularly the
testCrossCorrelation
andfindPeaks
which are both needed to use the stitching functionality outside of theStitching_3D
plugin