in reply to Calculate log of matrix values

Rather than having to testing for 0 (or undef) in all your further calculations, it may be easier (and mathematically acceptable) to replace your zeros with a very small number, say 1e-308:

map $_//= 1e-308, @$_ for @matrix;

which should have negligible affect upon any calculations, but avoid lot of special casing.


With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

Replies are listed 'Best First'.
Re^2: Calculate log of matrix values
by BillKSmith (Monsignor) on Aug 09, 2013 at 18:07 UTC
    The POSIX HUGE_VAL would be closer to the mathamatical concept. It would never be mistaken for "unassigned". Attempts to use it in an expression would always throw an exception. A huge negative would be even better, but we do not seem to have that option.
    Bill
      Attempts to use it in an expression would always throw an exception.

      I think you've misunderstood my post. If I wanted to causes exceptions, I'd leave the zeros in place. or replace them with #NaN.

      My point was that by replacing the zeros with a very, very small number, you can avoid exceptions, or the need for conditional tests to avoid exceptions, as it will allow most calculations to operate correctly whilst introducing negligible changes to the final results.


      With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.
        I did misunderstand your intention. However I still do not understand your solution. If I assume that the zero data is really a small positive number that displays as '0.00', its log should be a negative number whose magnatude exceeds any of the other logs. (e.g. log(0.001) = -6.9) Setting the log to zero assumes that the raw value is e (2.71...). Note: All other values are between .001 (log(.01) = -4.6) and .99 (log(.99) = -.01).
        Bill
      HUGE_VAL does not help here, we need kind of a TINY_VAL. 1 / HUGE_VAL does not work:
      $ perl -MPOSIX=HUGE_VAL -e 'print log(1 / HUGE_VAL)' Can't take log of 0 at -e line 1.
      لսႽ† ᥲᥒ⚪⟊Ⴙᘓᖇ Ꮅᘓᖇ⎱ Ⴙᥲ𝇋ƙᘓᖇ