On 01/30/2013 06:53 PM, David Mertens wrote:
There are a couple of places where these sorts of warnings are baked
into printf statements in the .pd files. The proper solution is to
replace all of these with a proper warnings system, like a barf that
didn't die. The quick fix is to hack on the .pd file. I don't think
there's a way to stop it programatically, unfortunately.
David
On Jan 30, 2013 4:27 PM, "Chris Marshall" <[email protected]
<mailto:[email protected]>> wrote:
I'm getting a bunch of
WARNING: matmult does not handle bad values.
every time the matmult routine is called which
makes it *exceedingly* difficult to view the
output with all the text cruft. The error does
not appear to even go to STDOUT so I couldn't
redirect it.
Anyone know a good way to stop the warnings
or is this a candidate Known_problem (a.k.a., bug).
Thanks,
Chris
_______________________________________________
Perldl mailing list
[email protected] <mailto:[email protected]>
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
You could try "removing" the bad flag from the input piddle that you
pass to matmult - e.g. $foo->setbadtoval(0) - which might be a good idea
to ensure that any bad values don't get treated as actual numbers and
propogated into your matrix.
Doug
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
