Observatory Trials Certificates History Lookup
Return a sourced Kew or Neuchâtel observatory-trial, certificate, database, or terminology fact.
Description
Observatory trials produced historical rate records and certificates under their own competition rules.
Observatory trials produced historical rate records and certificates under their own competition rules. Those documents differ from modern certification programs.1
Return a sourced Kew or Neuchâtel observatory-trial, certificate, database, or terminology fact.
When to use Observatory Trials Certificates History Lookup
Use this tool to return a sourced Kew or Neuchâtel observatory-trial, certificate, database, or terminology fact.
Choose a supported lookup focus or prepare the measured values, documented evidence and caller-selected limits requested. Use the exact field names and confirm their units or date format.
How to use Observatory Trials Certificates History Lookup and understand its results
- Choose a supported lookup focus or prepare the measured values, documented evidence and caller-selected limits requested. Use the exact field names and confirm their units or date format.
- Enter historyFocus using the field table and calculation rules, then run the tool.
- Read historyFocus, keyDate, verifiedStatement. 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 |
|---|---|---|---|
| historyFocus | Observatory trial history focus | string; one of "kewTimeline", "kewWatches", "neuchatelTrials", "bulletin", "database", "scopeCaution" | Required |
Select one supported focus from the input table and run the lookup. Match the exact case-sensitive enum value; no trimming, synonyms or free-text search is applied. Return the selected focus and its stored trial-history statement and period/context label. keyDate, where present, can be a historical date, period or contextual label rather than a parseable date.
result=stored entry for exact selected focus Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| historyFocus | Observatory trial history focus | string |
| keyDate | Key date or category | string |
| verifiedStatement | Verified observatory-trial statement | string |
{
"input": {
"historyFocus": "kewTimeline"
},
"output": {
"historyFocus": "kewTimeline",
"keyDate": "1766–1915",
"verifiedStatement": "Royal Observatory Greenwich records trial activity from H4 in 1766 and preserves published watch and chronometer rate records through 1915."
}
}Limitations and assumptions
No archive is searched and no certificate, submitted movement, trial result or COSC status is authenticated. This is a fixed local table; it does not fetch sources or update statements at runtime.
Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Extremely large text inputs are rejected. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Six Position Orientation Code Lookup: Map the CH, CB, 9H, 6H, 3H, and 12H workshop test codes to physical orientations while separating them from the five-position COSC procedure. For a complementary task, use Positional Rate Variation Threshold Screen: Calculate the maximum-minus-minimum rate spread across measured positions and compare it only with an explicit caller-supplied range limit.
References
Similar or alternative tools
- Six Position Orientation Code Lookup
Map the CH, CB, 9H, 6H, 3H, and 12H workshop test codes to physical orientations while separating them from the five-position COSC procedure.
- Positional Rate Variation Threshold Screen
Calculate the maximum-minus-minimum rate spread across measured positions and compare it only with an explicit caller-supplied range limit.