It'd be good to clarify the logic here. On the one hand, I'd love to replace the thresholds with functions that depend on area, on the other hand that's a bigger change than we can really do right now and the thing we need to do is find the settings that make the original approach as logical as we can. I agree that having the cutoffs differ is a problem and a single cutoff would make sense -- it looks like later in the code 1200 is used for both.

Perhaps we want "small_floe_minimum_area", so that only floes larger than that are tracked, and a "large_floe_minimum_area", so that a floe with area A can be cleanly divided as:

• A < small_floe_minimum_area --> don't track
• small_floe_minimum_area <= A < large_floe_minimum_area --> use the small_floe_settings
• large_floe_minimum_area <= A --> use the large_floe_settings.

Originally posted by @danielmwatkins in #551 (comment)