Skip to content

[Feature]: TC analysis should support TC tracking data that is spread across multiple files #1002

@chengzhuzhang

Description

@chengzhuzhang

Is your feature request related to a problem?

Current Situation: Tropical cyclone (TC) tracking (i.e. via TempestExtremes) on high-resolution E3SM simulations (e.g., ne120 grid) is computationally expensive. Tracking storms over 10 years of output data can take ~80 minutes. Currently, e3sm-diags does not support reading TC track data spread across multiple files. Instead, users must: Either rerun the full tracking workflow to regenerate a single merged file each time.

If an analysis fails or needs to be repeated, users must rerun the entire tracking process from the beginning. This is inefficient and wasteful, especially for high-resolution cases.

Proposed Capability:

Enable e3sm-diags to accept and process multiple TC track files (e.g., one per year) as input without requiring a single merged file. zppy needs some update as well.

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions