Scrim Front versus Rear Reveal Ratio Lookup
Audit independently measured front/rear scrim lighting ratio under caller reveal target; not a guarantee of perceived transparency, weave-independent concealment or inferred fixture intensity.
Description
Scrim reveal depends partly on front and rear illumination.
Scrim reveal depends partly on front and rear illumination. A measured ratio is a lighting-plan check, not a transparency guarantee.1
Enter positive front lux, nonnegative rear lux and minimum. Return ratio and inclusive flag.
When to use Scrim Front versus Rear Reveal Ratio Lookup
Use Scrim Front versus Rear Reveal Ratio Lookup when you need to evaluate the supplied records under the calculation and evidence rules below. No weave, viewing geometry or perceived concealment is modeled.
Prepare the actual venue, production, inventory or financial records requested. Confirm units and supply applicable local limits or verified catalog values.
How to use Scrim Front versus Rear Reveal Ratio Lookup and understand its results
- Prepare the actual venue, production, inventory or financial records requested. Confirm units and supply applicable local limits or verified catalog values.
- Enter observedFrontLitScrimLux, observedRearSceneLux, callerRevealRatioMinimum using the field table and calculation rules, then run the tool.
- Read rearToFrontMeasuredIlluminanceRatio, meetsCallerRevealLightingPlan. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| observedFrontLitScrimLux | Observed front lit scrim lux | number | Required |
| observedRearSceneLux | Observed rear scene lux | number | Required |
| callerRevealRatioMinimum | Caller reveal ratio minimum | number | Required |
Enter positive front lux, nonnegative rear lux and minimum. Return ratio and inclusive flag.
ratio=rearLux/frontLux; pass=ratio≥minimum Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| rearToFrontMeasuredIlluminanceRatio | Rear to front measured illuminance ratio | number |
| meetsCallerRevealLightingPlan | Meets caller reveal lighting plan | boolean |
{
"input": {
"observedFrontLitScrimLux": 20,
"observedRearSceneLux": 100,
"callerRevealRatioMinimum": 4
},
"output": {
"rearToFrontMeasuredIlluminanceRatio": 5,
"meetsCallerRevealLightingPlan": true
}
}Limitations and assumptions
No weave, viewing geometry or perceived concealment is modeled.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors. A successfully returned false flag is an evaluated outcome; its meaning is explained above.
Alternative or Complementary methods
Use Blackout Duvetyne Light Leak Layer Checker: Independent optical layer transmissions multiply in a simple stack model. Real seams and scattering can dominate leakage. For a complementary task, use LED Wash Par Can Replacement Equiv Lookup: Replacement lighting estimates need matched-area illuminance rather than wattage alone. Whole fixtures introduce rounding in both output and power.
References
Similar or alternative tools
- Blackout Duvetyne Light Leak Layer Checker
Independent optical layer transmissions multiply in a simple stack model. Real seams and scattering can dominate leakage.
- LED Wash Par Can Replacement Equiv Lookup
Replacement lighting estimates need matched-area illuminance rather than wattage alone. Whole fixtures introduce rounding in both output and power.