Skip to content

Frequency could crash with an explanation #9

@micah-prime

Description

@micah-prime
  • metevents version: 0.3.0
  • Python version: 3.9
  • Operating System: Mac OS

Description

StormEvents.find will crash if there is a fully missing timestep (not NAN). This should crash, but we should add an error describing why. Currently when determine_frequency is called, it returns None in this case.

We could change the default behavior of determine_frequency to raise a RunTimeError, but have a kwarg into the function to not raise an error if the user wants to get the None returned

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions