paraview-interface-verify-data-range

Sub-skill of paraview-interface: Verify Data Range (+2).

5 stars

Best use case

paraview-interface-verify-data-range is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Sub-skill of paraview-interface: Verify Data Range (+2).

Teams using paraview-interface-verify-data-range should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/verify-data-range/SKILL.md --create-dirs "https://raw.githubusercontent.com/vamseeachanta/workspace-hub/main/.agents/skills/_archive/engineering/cfd/paraview/verify-data-range/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/verify-data-range/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How paraview-interface-verify-data-range Compares

Feature / Agentparaview-interface-verify-data-rangeStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Sub-skill of paraview-interface: Verify Data Range (+2).

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Verify Data Range (+2)

## Verify Data Range


```python
def validate_data_ranges(source, expected_ranges):
    """Validate that data arrays are within expected ranges.

    Args:
        source: ParaView source/filter
        expected_ranges: dict of {'array_name': (min, max)}
    """
    source.UpdatePipeline()
    data_info = source.GetDataInformation()
    checks = {"passed": True, "issues": []}

    for name, (exp_min, exp_max) in expected_ranges.items():
        array_info = data_info.GetArrayInformation(name, 0)  # 0=point, 1=cell
        if not array_info:
            array_info = data_info.GetArrayInformation(name, 1)
        if not array_info:
            checks["issues"].append(f"Array '{name}' not found")
            checks["passed"] = False
            continue

        data_range = array_info.GetComponentRange(0)
        if data_range[0] < exp_min * 0.5 or data_range[1] > exp_max * 2.0:
            checks["issues"].append(
                f"{name}: range [{data_range[0]:.3f}, {data_range[1]:.3f}] "
                f"outside expected [{exp_min}, {exp_max}]"
            )
            checks["passed"] = False

    return checks

# Example: validate typical CFD ranges
validate_data_ranges(reader, {
    'p': (-1e5, 1e5),       # Pressure (Pa, relative)
    'U': (-50, 50),          # Velocity (m/s)
    'k': (0, 100),           # Turbulent kinetic energy
    'omega': (0, 1e6),       # Specific dissipation rate
})
```


## Verify Screenshot Output


```python
import os

def validate_screenshots(output_dir, expected_count=1, min_size_kb=10):
    """Validate that screenshots were generated correctly."""
    checks = {"passed": True, "issues": [], "files": []}

    images = [f for f in os.listdir(output_dir)
              if f.endswith(('.png', '.jpg', '.tiff'))]

    if len(images) < expected_count:
        checks["issues"].append(
            f"Expected {expected_count} images, found {len(images)}"
        )
        checks["passed"] = False

    for img in images:
        path = os.path.join(output_dir, img)
        size_kb = os.path.getsize(path) / 1024
        checks["files"].append({"name": img, "size_kb": size_kb})
        if size_kb < min_size_kb:
            checks["issues"].append(f"{img}: {size_kb:.1f} KB — likely blank render")
            checks["passed"] = False

    return checks
```


## OpenFOAM Case Completeness Check


```python
def validate_openfoam_for_paraview(case_dir):
    """Check that OpenFOAM case is ready for ParaView visualization."""
    import os
    checks = {"passed": True, "issues": []}

    # Check polyMesh exists
    polymesh = os.path.join(case_dir, 'constant', 'polyMesh')
    if not os.path.isdir(polymesh):
        checks["issues"].append("No constant/polyMesh/ — mesh not generated")
        checks["passed"] = False

    # Check time directories
    time_dirs = [d for d in os.listdir(case_dir)
                 if d.replace('.', '').isdigit() and d != '0']
    if not time_dirs:
        checks["issues"].append("No result time directories — simulation not run")
        checks["passed"] = False
    else:
        checks["time_dirs"] = len(time_dirs)

    # Check for .foam file
    foam_files = [f for f in os.listdir(case_dir) if f.endswith('.foam')]
    if not foam_files:
        checks["issues"].append("No .foam file — create with: touch case.foam")

    return checks
```

Related Skills

data-validation-reporter

5
from vamseeachanta/workspace-hub

Generate interactive validation reports with quality scoring, missing data analysis, and type checking. Combines Pandas validation, Plotly visualization, and YAML configuration for comprehensive data quality reporting.

worldenergydata-source-readiness

5
from vamseeachanta/workspace-hub

Route agents to the canonical worldenergydata source-readiness skill and summary script. Use when asked for worldenergydata data completeness, data locations, latest known data dates, scheduler freshness, source-readiness status, or acceptance-criteria inputs across the repo ecosystem.

sodir-data-extractor

5
from vamseeachanta/workspace-hub

Extract and process Norwegian Petroleum Directorate field and production data from SODIR

metocean-data-fetcher

5
from vamseeachanta/workspace-hub

Fetch real-time and historical metocean data from NDBC, CO-OPS, Open-Meteo, ERDDAP, and MET Norway. Use for buoy data retrieval, tidal observations, marine forecasts, and multi-source data fusion.

energy-data-visualizer

5
from vamseeachanta/workspace-hub

Interactive visualization for oil and gas production data analysis using Plotly dashboards

bsee-data-extractor

5
from vamseeachanta/workspace-hub

Extract and process BSEE (Bureau of Safety and Environmental Enforcement) data including production, WAR (Well Activity Reports), and APD (Application for Permit to Drill) data. Use for querying production data, well activities, drilling permits, completions, and workovers by API number, block, lease, or field with automatic data normalization and caching.

verify-Codex-run-commit-vs-working-tree-before-closing

5
from vamseeachanta/workspace-hub

After a Codex implementation run, verify the claimed file set against the actual commit and working tree before treating the issue as fully complete.

tax-return-data-capture-and-archival

5
from vamseeachanta/workspace-hub

Capture structured tax return summaries as YAML for year-over-year comparison, with fallback to manual PDF download and relocation when automation fails

repo-separation-for-sensitive-data

5
from vamseeachanta/workspace-hub

Architecture pattern for splitting confidential data and reusable algorithms across repos

metadata-only-wiki-sweep-workflow

5
from vamseeachanta/workspace-hub

Disciplined inventory process for cataloging documents by filename/path without content claims, using parent-centric grouping to prevent stub proliferation

metadata-only-inventory-sweep

5
from vamseeachanta/workspace-hub

Execute constrained file inventory sweeps with metadata-only stubs and validation, useful for staged documentation work on large file sets

handle-blocked-financial-sites-data-export

5
from vamseeachanta/workspace-hub

Workflow for extracting data from blocked financial sites when browser automation is restricted