Visibility Period Count Reliability Floor Checker
Independent count of separated visibility periods vs caller release-specific floor; count does not prove reliability or replace observations count. Caller independently establishes frames, units, epoch, covariance and instrument context; not an identity, association or astrometric quality certification.
Description
Visibility-period counts summarize observational coverage under a catalog convention.
Visibility-period counts summarize observational coverage under a catalog convention.1
A supplied reliability floor does not replace a full astrometric quality assessment. Use Visibility Period Count Reliability Floor Checker to evaluate the supplied inputs under the model explained below.
When to use Visibility Period Count Reliability Floor Checker
Use Visibility Period Count Reliability Floor Checker to evaluate the supplied inputs under the model explained below. Establish the units, measurement scope and model assumptions before entering values.
How to use Visibility Period Count Reliability Floor Checker and understand its results
- Establish the units, measurement scope and model assumptions before entering values.
- Enter Observed distinct visibility periods, Caller release specific minimum using the field table and validation rules below, then run the tool.
- Read Signed visibility period reserve, Caller period floor reached; interpret the units, signs, ordering and unknown-value placeholders described below.
- Correct reported input errors and rerun. Apply successful results according to their specific meanings and check the assumptions before using them in a decision.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| observedDistinctVisibilityPeriods | Observed distinct visibility periods | number | Required; constraints below |
| callerReleaseSpecificMinimum | Caller release specific minimum | number | Required; constraints below |
Enter integer observed distinct periods 0–10000 and integer release-specific floor 1–10000. Subtract floor from observed and compare inclusively. No catalog-release default or complete reliability assessment is installed.
reserve=observed−floor; reached=observed≥floor Use the field order, units and branch conditions described above.
| Output field | Meaning | Value type |
|---|---|---|
| signedVisibilityPeriodReserve | Signed visibility period reserve | number |
| callerPeriodFloorReached | Caller period floor reached | boolean |
{
"input": {
"observedDistinctVisibilityPeriods": 8,
"callerReleaseSpecificMinimum": 9
},
"output": {
"signedVisibilityPeriodReserve": -1,
"callerPeriodFloorReached": false
}
}Limitations and assumptions
A supplied reliability floor does not replace a full astrometric quality assessment. Apply the exact scope and assumptions explained above.
All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are explained above; extremely large inputs or outputs can also be rejected. Input errors differ from successful false results, empty match lists and unknown-evidence placeholders.
Alternative or Complementary methods
Use Six-Parameter Solution with Pseudocolour Presence Checker for a related task: A six-parameter astrometric record includes a pseudocolour under the declared parameter convention.
Use High Proper Motion Star Threshold 180 mas/yr Flag Checker for a related task: A high-proper-motion flag compares a measured magnitude with a chosen catalog threshold.
References
Similar or alternative tools
- Six-Parameter Solution with Pseudocolour Presence Checker
A six-parameter astrometric record includes a pseudocolour under the declared parameter convention.
- High Proper Motion Star Threshold 180 mas/yr Flag Checker
A high-proper-motion flag compares a measured magnitude with a chosen catalog threshold.