[Enhancement]: Add E3SM Diagnostic Viewer links to simulations

[tomvothecoder]

Is your feature request related to a problem?

SimBoard users need a convenient way to navigate from a simulation details page to the corresponding E3SM Diagnostics Viewer output.

E3SM Diagnostics generates HTML viewer pages for diagnostic results. The viewer organizes diagnostic output into browsable pages, groups, rows, and columns, and can include plots, scripts, and related output files.

For the MVP, SimBoard should link to these existing viewer pages instead of ingesting diagnostic plots or metrics.

Describe the solution you'd like

Add an E3SM Diagnostics Viewer link section to the SimBoard simulation details page.

The link should be derived from simulation metadata and the expected diagnostics output location when possible. The initial implementation should focus on linking to existing public diagnostics viewer output, not ingesting diagnostic data into SimBoard.

Potential UI states:

• Success: Open Diagnostics Viewer
• Missing diagnostics URL: Diagnostics unavailable
• No applicable diagnostics metadata: hide the section

Additional context

This issue is part of the Phase 1 MVP diagnostics and evaluation integration work.

Phase 1 focuses on linking SimBoard simulations to existing external evaluation resources:

• E3SM Diagnostics Viewer output
• PACE performance records
• E3SM IICE cross-comparison views

This issue covers the E3SM Diagnostics Viewer link only.

Out of scope for this issue:

• Full diagnostics ingestion
• Extracting metrics from zppy or E3SM Diagnostics output
• Storing diagnostic plots in SimBoard
• Building SimBoard-native diagnostic visualizations
• Re-running diagnostics for older simulations
• Cross-site diagnostics archive consolidation

[tomvothecoder]

Hi @chengzhuzhang, I am scoping this feature to link E3SM Diagnostics Viewer output to SimBoard case runs.

Can you help answer these questions? It will influence the architecture design.

Questions

1. Are E3SM Diagnostics outputs stored in a standard NERSC filesystem location?

   • What is the path pattern?
   • Does it vary by campaign, machine, user, model version, or diagnostics configuration?

2. Is there a stable web URL pattern for E3SM Diagnostics Viewer output?

   • Can the URL be derived from the filesystem path?
   • Are these URLs public and expected to remain stable?

3. Are all relevant diagnostics viewer outputs publicly accessible?

   • If not, which require NERSC authentication or filesystem access?
   • Should SimBoard hide restricted links or show access guidance?

4. Can SimBoard reliably link a case execution to diagnostics output using LID?

   • SimBoard parses LID from e3sm_timing and stores it as execution_id.
   • PACE parses the same value and stores it as job_id.
   • Example: 52448807.260505-035011

   Does E3SM Diagnostics include this same LID, or is output stored under a path containing case name + LID?

5. If diagnostics output does not include LID, what is the best stable identifier for matching?

   • Case name
   • Campaign
   • Machine
   • Run timestamp
   • Output archive path
   • zppy run path
   • Provenance metadata

6. Which diagnostics target should SimBoard link to for the MVP?

   • E3SM Diagnostics Viewer only
   • zppy-generated diagnostics index pages
   • all available diagnostics bundles
   • only campaign-approved/reference diagnostics

7. If multiple diagnostics outputs exist for the same case execution, which one should SimBoard link to by default?

8. Is there a reliable completion marker for diagnostics output?

   • index page
   • metadata file
   • provenance file
   • completion marker
   • expected directory structure

9. Should SimBoard derive diagnostics links from path conventions, or store minimal diagnostics metadata?

   • Prefer derived links if path conventions are stable.
   • Store minimal metadata if paths vary by campaign, machine, user, or diagnostics configuration.

   Possible minimal fields:

   • execution_id
   • case_name
   • diagnostics_viewer_url
   • diagnostics_output_path
   • provenance_path

10. Are there known cases where diagnostics output exists but cannot be linked reliably from simulation metadata?

• Historical v1/v2/v3 simulations
• Diagnostics generated long after the simulation
• Diagnostics run by a different user
• Multiple diagnostics runs for the same simulation
• Moved, regenerated, or deleted diagnostics outputs