Discovery · side-by-side comparison
NASA and DOE
Similarity 0.42 (moderate). Moderate: overlapping task language; often related functions in different settings. Classified as Similar use case: The descriptions overlap. The inventory alone cannot show whether either system could be shared.
Why they matched
| Component | Contribution to score |
|---|---|
| System outputs | +0.273 |
| Problem description | +0.106 |
| Same AI classification | +0.037 |
| Expected benefits | +0.000 |
| Total | 0.416 |
Most distinctive shared terms: soil, soil moisture, moisture, cover, machine learning, machine
| Field | Simultaneous emulation and downscaling of modeled soil state variables with machine learning | Soil Moisture Modeling |
|---|---|---|
| Agency |  NASANational Aeronautics and Space Administration |  DOEDepartment of Energy |
| Bureau | GSFC: Goddard Space Flight Center | LM HQ - Office of Legacy Management (LM) |
| Stage | Pre-deployment | Pilot |
| Topic | Science | Energy and the Environment |
| AI classification | Classical / predictive ML | Classical / predictive ML |
| Sourcing | Not reported | Purchased from vendor |
| Vendor (reported) | Not reported | University of Montana |
| System name | Not reported | LMGSS |
| Problem | We propose a lightweight, computationally efficient machine learning (ML) model capable of emulating the LIS-based soil moisture and soil temperature and downscaling them from a native 10 km resolution to 1 km resolution. Our approach is extendable to other variables as long as a non-linear relationship between meteorological forcing and the variable of interest can be conceptualized as modulated by local conditions (elevation, soil type, land cover, vegetation). Then, a branched neural network (NN) architecture structurally represents this relationship. As a part of the project, different NN architectures and input combinations have been tested and assessed using SHapley Additive exPlanations (SHAP) values and ablation analysis. Currently, the downscaled product is being validated and compared to other high-resolution products. | Machine learning solves issues with soil moisture by enhancing accuracy and efficiency in data analysis |
| Outputs | The model outputs are emulated LIS-like soil moisture and soil temperature (predictions), as well as downscaled soil moisture and soil temperature. | Multi-layer soil moisture model/prediction |
| Benefits | Using the proposed method, it is possible to obtain LIS-like quality predictions for soil state variables in seconds, as well as provide unprecedented for LIS downscaled to 1 km data relevant to a wide variety of applications. The low computational cost of the inference and the ability to resolve fine-resolution features expedite obtaining the crucial information for decision-making. | The ability to determine evapotranspiration rates on disposal cell cover using publicly available data from satellites. |
| Data description | Not reported | Data is held back from the models to validate model outputs. |
| PII | Not reported | No |
| ATO | Not reported | No |
| Public code | Not reported | Not reported |
Exploratory reuse assessment
What the inventory can and cannot show| Functional similarity | moderate (0.42) | Some support |
| Inputs and outputs | Both describe outputs; compare below | Some support |
| Mission or administrative function | Different topic areas | Weak or missing |
| Documentation available | Code: none linked · System names: Not in inventory | Weak or missing |
| Technical uncertainties | AI classification: same; sourcing: unknown / vendor | Verify outside inventory |
| Data-access constraints | Data descriptions: Not in inventory / Reported | Verify outside inventory |
| Privacy and security | PII: blank / no · ATO: blank / no | Verify outside inventory |
| Legal or policy constraints | Not in inventory. Requires independent verification. | Verify outside inventory |
No pair is marked as a validated reuse opportunity. That needs technical, legal and operational evidence beyond this inventory.
Questions for a human reviewer
- Do NASA and DOE solve the same problem for the same kind of user, or only use similar words?
- Are the inputs (data types, formats, volumes) compatible?
- A vendor product is involved. Do licence terms allow use by another agency, and is it available on a government-wide vehicle?
- Does either system's Authorization to Operate cover use by another agency?