Task Lighting Lux Requirement Lookup by Task Type
Measured task illuminance vs caller verified task/age/contrast reference lux, not live lighting standard or recommended generic task list. Exact caller verified numeric reference; signed deviations retained. Caller independently establishes matching units, evidence, method edition and applicability; output is not compliance, diagnosis, work-safety approval, geological identity or validated hazard prediction.
Description
Illuminance in lux measures light arriving at a surface.
Illuminance in lux measures light arriving at a surface.1
A task reference needs its location, measurement protocol and source before an observed lux difference is interpreted. Use this tool to compare an observation with an exact caller-supplied numeric reference.
When to use Task Lighting Lux Requirement Lookup by Task Type
Use this tool to compare an observation with an exact caller-supplied numeric reference. Establish the observation protocol, units, task and reference population or review criterion before entering measurements.
How to use Task Lighting Lux Requirement Lookup by Task Type and understand its results
- Establish the observation protocol, units, task and reference population or review criterion before entering measurements.
- Enter callerVerifiedTaskIlluminanceKeys, callerVerifiedTaskIlluminanceValues, queryTaskIlluminanceKey, observedTaskIlluminanceValue, using the field meanings and rules below, then run the tool.
- Read callerReferenceValue, signedObservedMinusReference. Interpret the fields using their units, signs and evidence conventions below.
- If input validation fails, correct the reported field and run again. Before applying the result, check reference scope, model assumptions and any missing evidence or placeholder values.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| callerVerifiedTaskIlluminanceKeys | Caller verified task illuminance keys; caller assertion or measurement requiring independent evidence | list of string | Required |
| callerVerifiedTaskIlluminanceValues | Caller verified task illuminance values; caller assertion or measurement requiring independent evidence | list of number | Required |
| queryTaskIlluminanceKey | Query task illuminance key | string | Required |
| observedTaskIlluminanceValue | Observed task illuminance value | number | Required |
Enter nonempty aligned caller reference IDs and numeric reference values, an exact query ID and an observed value on the same unit and protocol basis. Reference values and the observation are finite signed numbers; there is no nonnegative check here and they need not be integers. IDs must be unique and nonblank, with at most 128 UTF-16 units each. The implementation uses case-sensitive exact matching without trimming, returns the matched reference value and subtracts it from the observation. An absent query or duplicate key fails. No regional dataset is installed, retrieved or authenticated.
reference=values[indexOfExact(queryId,ids)]; signedDifference=observed−reference Use the exact units, boundary rules, ordering and missing-evidence conventions above.
| Output field | Meaning | Value type |
|---|---|---|
| callerReferenceValue | Caller Reference Value; follow the units, sign, ordering and evidence convention stated above | number |
| signedObservedMinusReference | Signed Observed Minus Reference; follow the units, sign, ordering and evidence convention stated above | number |
{
"input": {
"callerVerifiedTaskIlluminanceKeys": [
"a",
"b"
],
"callerVerifiedTaskIlluminanceValues": [
2,
4
],
"queryTaskIlluminanceKey": "b",
"observedTaskIlluminanceValue": 5
},
"output": {
"callerReferenceValue": 4,
"signedObservedMinusReference": 1
}
}Limitations and assumptions
The numerical reference, unit basis and observation come from the caller. No authoritative regional table, standard edition, calibration or management rule is installed, retrieved or verified.
All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse evidence arrays fail validation; the specific bounds and alignment requirements are stated above. Extremely large inputs or outputs can also be rejected. An input error is distinct from a successful result reporting false, no matches or missing evidence.
Alternative or Complementary methods
Use Contrast Ratio Paper-Screen Reading Comfort Checker for this related task: Paper-to-screen luminance can be compared through a signed natural-log ratio.
Use Anthropometric Eye Height Seated Monitor Fit Checker when its separate inputs and assumptions fit the question: Eye and monitor-center heights determine a signed vertical viewing angle.
References
Similar or alternative tools
- Contrast Ratio Paper-Screen Reading Comfort Checker
Paper-to-screen luminance can be compared through a signed natural-log ratio.
- Anthropometric Eye Height Seated Monitor Fit Checker
Eye and monitor-center heights determine a signed vertical viewing angle.