Skip to content

time format for setup #7

Description

@liuquan18

Hi,

   brilliant tool to extract extremes and tracks.

   I have issues of time format when I use block.setup(force=True) on my own data (model output). I have tested with ERA5 data, same issue occurs: 

   _"ValueError: Cannot convert from timedelta64[ns] to timedelta64[h]. Supported resolutions are 's', 'ms', 'us', 'ns'"_

   I can easily comment out line 338 in contract.py, to avoid problems. but I don't know if this would bring me with problems. 

For example, my data contains data only in summer (JJA). when I comment out line 338, then some tracks continuing from August 31 (last point in this year) to June 1st (first point next year), which they shouldn't. I don't know if this is because I have commented out time check, or the code itself can not deal such problems. I can avoid the problem by using groupby year, but because the package is class based, groupby makes the codes looks quite ugly.

   I am looking forward for your reply.

Best,
Quan

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions