Am 26.03.2025 um 14:17 schrieb Allin Cottrell:
...
Merely in terms of what's easiest to achieve consistency, we could
omit the current calls to gretl_matrix_na_check(). I can see a case
for the opposite policy, namely generalizing this check, but that
would involve more work and I'm not sure it would be optimal. Most of
the time matrices don't contain any non-finite values, and we'd have
to spend a bunch of cycles checking every element of big matrix
arguments.
Here's a thought. Not sure if it's worthwhile, but we could have a
"set" variable that turns on NA-checking for matrix arguments. That
would make it easier to determine where, in some complicated contexts,
things first go wrong.
Here's a small update for this devel list on further off-list
discussions about these issues since March:
checking other numerical software turned out that the world is very wild
out there; the various programs employ all sorts of error handling, and
they're all at least as inconsistent as gretl is. So it's not so obvious
what to do. (Also because the various error incarnations originate from
different underlying libraries/places, so it's not so easy to harmonize
them at an upper level.)
Just four everbody's general information, this thread didn't just die out.
cheers
sven