Software

One desktop scientific workflow.

BAITSSS Desktop organizes project inputs, hourly simulation, Results, and scientific exports.

BAITSSS Desktop is under active development.
01 · Product walkthrough

BAITSSS Desktop in 4–5 Minutes

Current BAITSSS Desktop development build.Project → data → run → Results
02 · Workflow

From Project to Results

01

Define project and area

Create or reopen a project, define the point or spatial AOI, and select the simulation period.

02

Prepare and verify environmental data

Organize Landsat vegetation information, NLDAS weather, terrain, soil, land cover, and required model inputs.

03

Configure and run the model

Review scientific settings and run the continuous hourly water and energy balance.

04

Monitor, stop, resume, and recover

Track progress and completed model hours. Stop and resume from checkpoints when needed.

05

Inspect and export Results

Review mapped ET, pixel time series, soil-water conditions, modeled irrigation requirement, run information, and exports.

03 · Execution

How BAITSSS Runs the Model

Sequential state · parallel spatial work

Each completed hour becomes the next hour’s starting state.

BAITSSS advances time sequentially because each hour starts from the surface and root-zone state produced by the previous hour. Within an hour, spatial work can be divided into blocks and distributed across persistent CPU workers. The blocks are collected before the hour is completed, and that state becomes the starting point for the next hour.

04 · Results

What BAITSSS Produces

01

Evapotranspiration

Mapped and time-series ET, with separate vegetation and soil contributions.

02

Soil-water status

Surface-layer and root-zone water conditions carried through the simulation period.

03

Modeled irrigation requirement

Modeled irrigation requirement is separate from known or recorded irrigation applied in the field.

04

Analysis records

Maps, pixel time series, run information, scientific exports, settings, assumptions, and input provenance.

05 · Performance

Computational Scale

Execution caseObserved timeInterpretation
168 h, single 30 m Landsat pixel2.19 s transformed execution coreControlled single-pixel benchmark
3,336 h, single pixel124.48 s total run timeSingle-pixel production run
275,098 model cells × 24 habout 52 sPreliminary spatial engineering observation
275,098 model cells × 168 habout 308 sPreliminary spatial engineering observation

The spatial measurements are preliminary engineering observations. Final large-area benchmarking is still being completed.

06 · Development status

Current Software Status

Current satellite support: BAITSSS Desktop currently supports Landsat 7, 8, and 9. Other satellite platforms are not yet incorporated and remain part of future development.

Current

  • Project workflow and AOI definition
  • Data preparation and readiness
  • Landsat 7, 8, and 9 satellite input support
  • Hourly execution and multiprocessing spatial route
  • Checkpoint and restart
  • Results workflow and scientific export
  • Run identity and provenance

Still being tested or completed

  • Support for additional satellite platforms
  • Final large-AOI spatial benchmark
  • Broader spatial testing across scenes and projects
  • Clean-machine release testing
  • Final installer and release packaging
  • Broader user testing