F
FluxGapFillUNIVERSAL IMPORT · LOCAL SCIENCE · PHASE 1
Files stay local
Loading Python
Phase 1 · universal import foundation

Bring your processed flux data.
FluxGapFill maps the rest.

Start from computed fluxes or half-hourly/hourly environmental data—not raw high-frequency sonic/IRGA signals. EddyPro, Campbell TOA5, AmeriFlux/FLUXNET-style files, generic delimited files and Excel workbooks can enter the same transparent project schema.

EddyProCampbell TOA5AmeriFlux / FLUXNETCSV / TXT / TSVExcelManual mapping fallback100% browser processing

1. Project data

Primary processed flux/environmental file plus optional supplemental weather data.

No alternate-format files to test?Use the bundled synthetic examples:

2. Project policy

Time handling is explicit because logger conventions differ.

Privacy behavior. Selected files are copied only into the temporary Pyodide filesystem/memory for this browser session. Refreshing or closing the page removes the working copies; original files on your computer are unchanged.
Variable mapping

Verify before processing

FluxGapFill proposes mappings and units but does not silently assume unknown fields. Correct any suggestion here before loading the project.

Choose files and run inspection first.

Primary file

Not inspected

RoleSource columnUnitDetection
Inspect a primary file first.

Supplemental file

Optional

RoleSource columnUnitDetection
No supplemental file selected.

Input preview

First records only. Preview does not alter the file.

Inspect a file to preview it.
Data overview

Quality, completeness and gap structure

Standardized midpoint grid after mapping, unit normalization, QC screening and optional supplemental alignment.

Records
Time step
LE missing
H missing
LE longest gap
H longest gap
Period
External source

Measured fluxes

Downsampled only for visualization; calculations use every record.

Project details

Project
Primary source
Period
Records
Resolution
Supplemental source

Predictor availability

Variables visible to current/future analysis modules.

VariableCompleteN
Capability-aware workspace

Use what is ready. Add data where needed. Skip the rest.

Each analysis module checks required variables independently, so missing footprint or carbon information never blocks gap filling or ET work.

Optional site information

Needed by selected advanced modules; leave blank if not applicable.

How optional modules behave

Ready means the required data are already in the project. Needs data identifies exactly what is missing. Use “Add data” to return to the import workspace, or “Skip” to hide that module for this project. Skipping never deletes data.
High-frequency raw EC processingOut of scope
Processed flux / environmental dataSupported
Server-side storageNone
Process a dataset to evaluate module readiness.
Current science engine

Validate models on realistic calendar outages

Existing Phase-1 package retains the validated MDS/RF/XGBoost workflow while the universal project foundation is introduced.

Validation design

Quick mode uses one window per duration. Increase windows for a stronger benchmark.

Adaptive fill policy

Use the best validated method by gap duration or force one method.

Provenance is retained. Measured data are never overwritten.

Blocked-validation performance

FluxGapModelRMSEMAEBiasWindows
Run validation to populate this table.

Selected model by duration

No site-specific validation has been run yet.
Results

Gap-filled fluxes with provenance

Measured observations remain unchanged; reconstructed values retain method labels and validation diagnostics.

Final LE and H

Method provenance

Run gap filling to populate provenance.

Daily ET from final LE

Temperature-dependent latent heat of vaporization.

Export

Take the complete audit trail with the data.

Exports are generated locally in the browser. No result file is uploaded to FluxGapFill.

Gap-filled products

Diagnostics

Preparing scientific runtime

Loading Python…