Floating point math can lead to situations in which combined GridExtents fail a requirement that checks correspondence between CellSize+Extent on the one hand and pixel cols/rows on the other.
This is likely desirable behavior if it happens only when bad data has been passed into MAML. It is very undesirable if it occurs in certain edge cases that are able to compute results properly, as happens whenever the Extent/CellSize ratio becomes too large and floating point arithmetic's approximations fail us.
The upshot of this is that we get slightly less guarded execution but avoid false positive errors
Floating point math can lead to situations in which combined
GridExtents fail a requirement that checks correspondence betweenCellSize+Extenton the one hand and pixel cols/rows on the other.This is likely desirable behavior if it happens only when bad data has been passed into MAML. It is very undesirable if it occurs in certain edge cases that are able to compute results properly, as happens whenever the
Extent/CellSizeratio becomes too large and floating point arithmetic's approximations fail us.The upshot of this is that we get slightly less guarded execution but avoid false positive errors