Discovery · side-by-side comparison
NASA and DOE
Similarity 0.45 (moderate). Moderate: overlapping task language; often related functions in different settings. Classified as Potentially reusable capability: DOE reports this as deployed while NASA reports pre-deployment. Functional similarity is moderate. Reuse still needs the evidence listed below.
Why they matched
| Component | Contribution to score |
|---|---|
| Expected benefits | +0.409 |
| Same AI classification | +0.037 |
| Total | 0.447 |
Most distinctive shared terms: detection
| Field | Semi-Automatic Landslide Detection (SALaD) | Machine Learning for geophysical data inversion |
|---|---|---|
| Agency |  NASANational Aeronautics and Space Administration |  DOEDepartment of Energy |
| Bureau | GSFC: Goddard Space Flight Center | NETL - National Energy Technology Laboratory (FECM) |
| Stage | Pre-deployment | Deployed |
| Topic | Science | Energy and the Environment |
| AI classification | Classical / predictive ML | Classical / predictive ML |
| Sourcing | Not reported | Developed in-house |
| Vendor (reported) | Not reported | Not reported |
| System name | Not reported | Not reported |
| Problem | Semi-Automatic Landslide Detection (SALaD). NASA's Semi-Automatic Landslide Detection (SALaD) system combines three leading-edge technologies: open-source Python packages and modules, object-based image analysis (OBIA), and machine learning (ML). | Leak detection. |
| Outputs | Predictions | Synthetic seismic and gravity data. |
| Benefits | Semi-Automatic Landslide Detection (SALaD) | Faster/better leak detection. |
| Data description | Not reported | Seismic and gravity data, potentially geological models and leak locations for training labels. |
| PII | Not reported | No |
| ATO | Not reported | No |
| Public code | Not reported | https://edx.netl.doe.gov/ |
Exploratory reuse assessment
What the inventory can and cannot show| Functional similarity | moderate (0.45) | 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: link provided · System names: Not in inventory | Some support |
| Technical uncertainties | AI classification: same; sourcing: unknown / in_house | 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?
- Public code is linked. Is it maintained and documented enough to adopt?
- Does either system's Authorization to Operate cover use by another agency?