2) Behaviour of invalid() in "Compute"
I also have had some problems with the invalid() function in compute. I
was trying things like "byte (invalid(a) || ( ( a < 1e32 ) ? 0 : 1 ) )"
to preserve the existing invalid positions if present. Does anyone
know if invalid() behaves correct if there is no "invalid positions"
component.
In my opinion it should always return 0 in this case, however it seems
to currently abort with a SISSEGV.
Definitely a bug and should be looked into.
3) I would like to add isnan and finite (and maybe more) to the "Compute"
module. Is there any good reasons against?
Hey why you're in there, could you add strcat? That's the only one
that isn't in Compute that I'm always looking for. Of course sprintf
would be a nice one too.
4) If in "Replace" you replace the "invalid positions" component, there
is no automatic call to DXStatistics to recompute the statistics. Should
this be done or should it be up to the user?
This is proper behavior--at least the documentation supports this.
Replace hasn't ever updated fields based on components. But maybe
this is the wrong behavior. Greg--can you comment on why derived
components shouldn't be updated at the end of the Replace module?
David
--
.............................................................................
David L. Thompson Visualization and Imagery Solutions, Inc.
mailto:[EMAIL PROTECTED] 5515 Skyway Drive, Missoula, MT 59804
Phone : (406)257-8530
