Recently I ran across some data for which the invalid positions component array comes back as integer rather than the byte array that I have been used to. A "wrong type" error occurs in subsequent modules that utilize invalid positions (ShowBoundary) if, for example, the 1's are then casted to byte(0). The User's Guide explains that for a smaller number of invalid positions, in order to save memory the array is structured differently (integer indices of only the invalid positions, rather than an array of bytes with same dimensions as the data field).
Is it expected then that a type-check must be made before the invalid positions array is altered ? In this particular case I bypassed the problem by removing the invalid positions rather than manipulating them, but I would like to know the philosophy behind all this.
