Tool name, e.g. daymet, narr, pm, amadeus, geocoder.
Tier: core
Why this slot matters
Without the tool name, a consumer cannot tell which piece of software produced the value, so the run cannot be re-executed and the tool's known behaviours and biases cannot be looked up. It is the entry point for every reproducibility check on the run.
In plain terms
This simply records which program was used — like noting the make and model of an appliance before describing its settings. Everything else about the run only makes sense once you know what tool ran.
URI: envar:slot/tool_name
Applicable Classes
| Name |
Description |
Modifies Slot |
| ToolRun |
A single tool invocation that produced an output from one or more inputs: too... |
yes |
Properties
Type and Range
Cardinality and Requirements
Examples
See Also
Annotations
| property |
value |
| tier |
core |
| justification |
Without the tool name, a consumer cannot tell which piece of software produced the value, so the run cannot be re-executed and the tool's known behaviours and biases cannot be looked up. It is the entry point for every reproducibility check on the run. |
| explanation |
This simply records which program was used — like noting the make and model of an appliance before describing its settings. Everything else about the run only makes sense once you know what tool ran. |
| covered_by |
None |
Schema Source
Mappings
| Mapping Type |
Mapped Value |
| self |
envar:tool_name |
| native |
envar:tool_name |
LinkML Source
name: tool_name
annotations:
tier:
tag: tier
value: core
justification:
tag: justification
value: Without the tool name, a consumer cannot tell which piece of software produced
the value, so the run cannot be re-executed and the tool's known behaviours
and biases cannot be looked up. It is the entry point for every reproducibility
check on the run.
explanation:
tag: explanation
value: This simply records which program was used — like noting the make and model
of an appliance before describing its settings. Everything else about the run
only makes sense once you know what tool ran.
covered_by:
tag: covered_by
annotations:
omop_gaia:
tag: omop_gaia
annotations:
extent:
tag: extent
value: absent
status:
tag: status
value: asserted
where:
tag: where
value: no column
note:
tag: note
value: No gaia table records a tool-name field; the gaia-db image name
is not carried on any native output.
degauss:
tag: degauss
annotations:
extent:
tag: extent
value: partial
status:
tag: status
value: asserted
where:
tag: where
value: output filename stem (e.g. ...daymet_1.0.0.csv / ...geocoder_3.3.0...csv)
note:
tag: note
value: Tool name is embedded in the output CSV filename, recoverable but
not a first-class field.
amadeus:
tag: amadeus
annotations:
extent:
tag: extent
value: absent
status:
tag: status
value: asserted
where:
tag: where
value: no column
note:
tag: note
value: No native Amadeus output file records the tool name.
cher:
tag: cher
annotations:
extent:
tag: extent
value: absent
status:
tag: status
value: asserted
where:
tag: where
value: no column
note:
tag: note
value: C-HER's table_dictionary carries dataset/resource metadata, not
a per-run producing-tool name.
codata:
tag: codata
annotations:
extent:
tag: extent
value: out_of_layer
status:
tag: status
value: asserted
where:
tag: where
value: no column
note:
tag: note
value: Tool-run provenance is instance-layer; CODATA EVs/CDIF operate
at the conceptual/represented layer and are excluded from scoring.
description: Tool name, e.g. `daymet`, `narr`, `pm`, `amadeus`, `geocoder`.
title: Tool Name
examples:
- value: daymet
description: DeGAUSS Daymet extraction tool
from_schema: https://w3id.org/linkml/microschemas/envar
see_also:
- https://degauss.org/
rank: 1000
domain_of:
- ToolRun
range: string