[FEAT-UI/Lambda]: User inputs need for JPM are in the JPM UI

Open
#665 9 comments 0 reactions 1 assignee View on GitHub

@martyheynbah is already working on this.

Since Jun 29, 2026.

Assessment

This issue has not been assessed yet.

Description

2SP

Confirm that we have all of the data necessary in the JPM UI to run the JPM Lambda
Image

Confirm this using Triet and the eurotop script in the stormsim repo
Here is the current known data needed:

[
config = {
    “inputs”:  {“data_file”: “jpm_input.parquet”},   # N×4 parquet: [timestamp, response, skew_tides, DSW]
    “outputs”: {“local_directory”: out_folder, “filename”: “sp1”},
    “jpm_params”:  {                                  # InputData fields
        “flag_value”: [],
        “slc”: 0.0
    },
    “jpm_options”: {                                  # Options (pydantic) fields
        “ua”: 0.37, “ur”: 0.58,
        “integration_mode”: “ITCS”,                   # ITCS for surge/Hm0/Tp; ATCS otherwise
        “uncertainty_mode”: “combined”,
        “tide_mode”: “none”,
        “percentiles”: [16, 84],
        “return_table”: True,
        “use_aep”: False
    }
}]

if data is missing please document and add the necessary input fields to the UI

Dominant language
No language data
Stars
2
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from USACE/chart-docs

All issues in USACE/chart-docs

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.