Skip to content

Handling da.histogram when range is not specified #4544

Description

@jakirkham

Currently da.histogram is unable to handle the case where range is not specified or for that matter when range consists of lazy values. It would be nice for da.histogram to handle this case by simply using the min/max of the data as the default range (as is done in np.histogram). Further it would be good if da.histogram avoided (accidentally) computing lazy values used for the range.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions