sign(NaN)

Issue #231 resolved
Steven R. Brandt created an issue

At present, Blaze produces 0 when given a NaN as an argument. In this case, Numpy (np.sign) produces a NaN instead. Would the be a more sensible behavior for Blaze?

Comments (5)

  1. Klaus Iglberger

    Hi Steven!

    Thanks a lot for the proposal. The idea is very reasonable and we'll try to implement the necessary modifications. Thanks again,

    Best regards,

    Klaus!

  2. Klaus Iglberger

    The feature has been implemented, tested, optimized, and documented as required. It is immediately available via cloning the Blaze repository and will be officially released in Blaze 3.6.

  3. Log in to comment