Capabilities

What BAITSSS can do as one integrated scientific system.

BAITSSS connects field definition, environmental data, hourly water and energy balance, evapotranspiration, soil water, modeled irrigation, thermal analysis, spatial Results, selected pixel science, scientific export, and reproducible run management within one Windows desktop workflow.

Integrated system

Established capability

One project from field definition through scientific Results.

The maintained BAITSSS workflow combines project setup, AOI definition, Landsat and environmental preparation, hourly forcing, scientific execution, long run recovery, Results inspection, selected pixel analysis, and export without separating the science from the project record.

ProjectAOILandsatBase dataWeatherHourly scienceModeled irrigationThermalResults30 m pixelExportReproducibility

Field, projects and data

Established capability

Define the study, preserve the run, and prepare aligned inputs.

Projects keep their identity, simulation period, data sources, validation state, and independent runs while the spatial and environmental inputs are prepared for the model grid.

Desktop projects and independent runs

Windows desktop scientific application
Create, open, switch, and manage persistent projects
Maintain multiple independent projects
Run multiple independent simulations within one project
Preserve project identity and simulation period
Freeze scientific configuration at run start
Keep previous runs and Results rather than overwriting them

AOI and model grid

Define, inspect, save, and reopen an Area of Interest
Review the AOI against map and raster context
Maintain geographic alignment across reopen and project switching
Validate CRS, extent, grid, and spatial compatibility
Use a 30 m Landsat based model grid for spatial projects
Preserve point and single cell spatial identity where supported

Landsat and vegetation

Landsat 7, 8, and 9
Scene discovery and period based processing
AOI aware and model grid aligned preparation
NDVI and LAI representation
Seasonal vegetation progression between observations
Source scene and processed product traceability
Landsat preview and spatial inspection

Environmental base data

DEM and elevation
NLCD land cover
Soil Field Capacity
Soil Available Water Capacity
BAITSSS base data library for supported layers
Supported automatic static layer selection
Review and replacement where supported
Validation before an unverified replacement becomes authoritative

Weather and reference ET

NLDAS hourly meteorological forcing
Complete hour coverage checks for the requested period
Missing data and readiness validation before Run
Continuous hourly forcing through the simulation
Internal reference ET preparation
Weather forcing and run period retained with the run authority

Installation and portability

Packaged Windows desktop system
Application and scientific runtime distributed together
User projects separated from replaceable application files
Updates and reinstalls preserve user projects and completed Results

Scientific computation

Established capability

Hourly energy, vegetation, water, irrigation, and thermal behavior are coupled.

Core BAITSSS science

Hourly two-source energy balance
Vegetation ET and soil ET
Total evapotranspiration
Two-layer soil-water balance
Surface soil water and root-zone soil water
Hour to hour state progression
Coupled vegetation, energy, water, irrigation, and thermal behavior

Thermal capability

Internally modeled soil temperature
Internally modeled canopy temperature
Thermal Results and scientific inspection
Observed Landsat surface temperature at a selected 30 m model pixel when a valid acquisition exists
Exact Landsat acquisition datetime retained for comparison
Independent comparison between observed Landsat thermal and modeled thermal behavior

Boundary: observed Landsat thermal is not assimilated directly into the maintained BAITSSS model trajectory.

Execution modes

Whole AOI spatial execution
Multiprocessing spatial execution
Supported point and single cell execution
Short diagnostic runs
Long seasonal runs
Visible run progress and status
The selected run remains the authority for its own Results

Water and irrigation

Established capability

Evaluate evapotranspiration, soil water, and modeled irrigation under defined management settings.

Modeled irrigation and management

Modeled irrigation requirement
Management Allowed Depletion control where exposed
Rooting depth configuration where exposed
Initial soil moisture adjustment where exposed
Irrigation configuration where exposed
Supported advanced scientific settings

Scenario comparison

Supported management and scientific settings are frozen into each run. The same field can be rerun with different supported settings so scenarios remain independent and traceable rather than modifying an earlier run.

Scientific evaluation

Compare BAITSSS outputs with independent ET or flux observations
Compare with soil-water observations
Compare modeled thermal behavior with thermal observations
Compare modeled irrigation with irrigation or water records
Use other appropriate independent scientific evidence

Execution and long runs

Established capability

Long simulations are designed to stop safely, resume, recover, and protect storage.

Stop, pause, resume, and recovery

Committed-hour checkpoints
Safe Stop at a committed hour boundary
Safe Pause at a committed hour boundary
Resume existing from the next uncommitted hour
Committed hours remain preserved
Recoverable failed run when a valid checkpoint exists
Recovery from the last valid committed checkpoint after interruption

Long-run storage and disk protection

Runtime disk space protection
Bounded storage for long simulations
Lossless storage of older hourly spatial outputs
Historical Results remain accessible
Storage optimization is not allowed to change scientific pixel values

Finalization

Run-specific final Results generation
Final hourly simulation CSV
Finalization tied to the selected run
Supported restart or recovery of finalization from valid partial state

Results and pixel analysis

Established capability

Move from mapped field behavior to the complete history of a selected 30 m model pixel.

Results visualization

Run-specific Results selection
Mapped total ET
Field-scale spatial variability
Hourly and seasonal time series where supported
ET total, vegetation ET, and soil ET
Surface and root-zone soil water
Modeled irrigation
Supported vegetation and weather context
Scientific map and selected pixel interaction
Point and single cell Results where supported

Selected-pixel science

Select a 30 m model pixel
Retrieve its complete hourly history
Works with whole AOI spatial runs
Works with supported single cell runs
Preserves the selected run as the Results authority
Includes observed Landsat thermal when a valid acquisition applies
Preserves pixel identity and coordinates for traceability

Thermal observation traceability

When observed Landsat surface temperature is available for the selected pixel, the scientific export retains the observed temperature and acquisition time while companion metadata preserves scene, source, quality, and thermal provenance.

Export and reproducibility

Established capability

Keep analysis outputs clean while preserving the scientific record behind them.

Scientific export and reporting

Hourly CSV export
Selected-pixel CSV export
Run Results CSV export
Clean scientific analysis tables
Separate provenance and metadata JSON
PNG export for supported Results
General and Publication figure modes where exposed
Simulation Report PDF where exposed

Run information and provenance

Run settings and scientific configuration
Run diagnostics and status
Run-specific inputs and outputs
Run-specific checkpoints and completion state
Persisted data source and validation state
Thermal acquisition and source provenance

Reproducibility safeguards

Frozen scientific configuration per run
Provisional sources cannot silently replace verified sources
Selected pixel identity remains traceable
Numerical equivalence claims require evidence rather than architectural similarity
Project and Results persistence is separated from replaceable application files

Research and evaluation

Established capability

Use one field-scale environment for research, teaching, demonstration, and independent evaluation.

BAITSSS supports reproducible scientific analysis without changing the underlying model science for presentation purposes.

Research

Evaluate model behavior, spatial variability, management scenarios, input sensitivity, site transferability, and comparison with independent scientific observations.

Teaching and demonstration

Use the same project, model, Results, selected pixel, and export workflow for scientific instruction and demonstration while retaining traceable inputs and run settings.

Evidence-based continuity

The maintained desktop route preserves the established BAITSSS scientific formulation across supported workflows.

Research & Education Evidence Access & Participation

In development

Local Weather Station forcing route

This route is being developed as an alternative to the established NLDAS forcing workflow. It is not presented as currently available until end-to-end execution through BAITSSS is proven.

Local station intake

Local hourly weather-station input
Required latitude, longitude, and elevation
Strict hourly timestamp and full-period validation
Complete weather and NDVI coverage checks

Conditioning and reference ET

Conditioning into BAITSSS forcing
Internal reference ET calculation

Planned execution path

After intake, conditioning, and reference ET are proven, the route is intended to execute through the normal BAITSSS scientific engine. This is still in development.