Frequently asked questions

What is Tare Program?

Tare Program is a post-processing service for long-baseline GNSS clock comparison. You send agreed comparison files for links we assign. We apply a proprietary off-line transformation and return the same files with values updated. Optional summary statistics if named at onboarding. The method is proprietary and patent-pending. You receive results only: no algorithm, parameters, or code.

Who is it for?

Organizations that already form long-baseline GNSS clock comparisons: time labs, research groups, government agencies, and timing vendors. We review applications and assign links. Not a consumer product and not a live desk feed.

What data can be submitted?

Only data your organization is authorized to share; non-classified and export-compliant. Accepted formats: IGS clock files (.clk, .clk.gz), CGGTTS time-transfer files (.cggtts), and structured CSV as specified at onboarding. Max 500 MB per file; compression accepted. Raw receiver logs, proprietary binary formats, and streaming feeds are not accepted. Full details are in the service terms.

How does a cycle work?

We assign opaque link IDs at onboarding. You submit files for those links. We return corrected files in the same format, typically within five business days of a complete submission. Train/holdout dates are locked before we run. One cycle per link unless we agree otherwise. A historical batch is the same job, one-shot.

What do I receive?

Corrected files in the format you sent. You keep your copy of before; we send after. You compute RMS (or any agreed metric) on your side. We do not return the correction term, parameters, or code. We do not warrant operational timing performance or that your panel will match published percentages.

How is data handled?

Submitted data is processed in a controlled, offline environment. Transfer is encrypted. The transformation runs on systems that do not expose the method. Your data is used only to produce your deliverable and is not shared with third parties.

What does it cost?

Fee is by assigned link and cycle. Academic and commercial list prices. Quoted at onboarding. Each assigned link is a separate fee. Repeat cycles on a link already onboarded are quoted separately. Payment before the first cycle. Terms are in the service agreement.

Who owns the data and the method?

Your submitted data remains yours. The method is Banlys intellectual property. No license is granted. You may not reverse-engineer the correction from the files we return.

Are published results what I will see on my links?

They are representative of the protocol and the GNSS clock-comparison domain—not a guaranteed effect size on your panel. Published runs are fixed, public IGS-class exhibits (pinned windows, null tests in the evidence room). Your first cycle uses the same train/holdout frame on your agreed inputs. Public statistics show what we observed on those panels; your cycle answers whether similar movement appears on yours.

What do the published numbers show?

In published IGS-class holdout runs: typical RMS reduction ~45%, remainder commonly 17–22 ns. One strict window (IGS Final 2024-250 to 2024-279): 115.6 ns to 22.1 ns (80.8%). Your panel may differ.

Public demonstration uses International GNSS Service (IGS) data. Same data, same metric—only the transformation applied. No method is disclosed.

How do I start?

Use the account form. We review your organization, dataset description, and links. If we take the work, we send a service agreement, payment instructions, and file-naming for your assigned links. Applications are typically reviewed within 5–10 business days.

What happens after I apply?

We review within 5–10 business days. If we take the work, we send a service agreement and payment instructions. After payment and a signed agreement, we send upload access, the metadata template, and file-naming convention. First cycle is the check: you score after vs the before you kept.