IDEN

Bandingkan sumber

Seri yang mengaku mengukur hal yang sama, berdampingan. Tidak ada yang digabung dan tidak ada sumber yang dinyatakan benar; perkiraan dan aktual tidak pernah dianggap bersaing.

BI-Rate decisions vs BI-Rate · Sama

A
BI-Rate decisions id_rate_bi
Sumber
Bank Indonesia press releases (Bank Indonesia)
Satuan · frekuensi
% · m
Riwayat
2026-05-20 – 2026-09-23 · 6 data
Jenisnya
actual
B
BI-Rate birate
Sumber
Bank Indonesia BI-Rate table (Bank Indonesia)
Satuan · frekuensi
% · m
Riwayat
2025-12-17 – 2026-09-23 · 11 data
Jenisnya
actual
Tanggal bersama
6
Berbeda melebihi pembulatan
0
± 0.005
Rata-rata |B − A|
0,0000
Terbesar |B − A|
0,0000
2026-05-20
Tanggal bersama terakhir
0,0000
2026-09-23
5,405,60Jun 26Sep 26A BI-Rate decisi 5,75B BI-Rate 5,75
TanggalABB − A
2026-09-235,75005,75000,0000
2026-08-195,75005,75000,0000
2026-07-225,75005,75000,0000
2026-06-185,75005,75000,0000
2026-06-095,50005,50000,0000
2026-05-205,25005,25000,0000

Terakhir 6 tanggal bersama · Data ↓

Padanan yang dinyatakan

PasanganStatusBersamaBerbedaB − A terakhir
id10y / idgb_10y
Indonesia 10-year government bond yield
Tumpang tindih terlalu sedikit100,0000
id_rate_bi / birate
Bank Indonesia policy rate
Sama600,0000

Pasangan dinyatakan di config/data_lineage.yaml.

Id penyedia sama: periksa apakah mengukur hal yang sama

Dua kunci membaca id seri penyedia yang sama. Bisa jadi kolom berbeda dari satu tabel (arus harian dan totalnya), jadi dicantumkan untuk dinilai orang, bukan sebagai konflik.

Juga: pemeriksaan silang antarsumber dari berkas cockpit · paritas kolektor dengan cockpit

Cara pasangan dibandingkan
Source conflict detection (Sprint 5). Two series that claim to measure the same thing are compared;
they are never merged, and neither is declared right.
Candidate pairs:
    declared      series people listed as equivalent (config/data_lineage.yaml `equivalents`): the conflict list
    same id       two stored series with the same provider and provider series id (catalog): listed separately
                  for review, because two keys can read different fields of one provider table (a daily flow
                  and its running total share an id), so a shared id alone does not make them the same thing
Any two series can also be compared on request. The cockpit file's own cross-checks and the collectors'
parity check are separate pages (Research > Tools) and are linked, not recomputed.
For a pair: frequency, unit, history and, on the dates both have, B minus A. Values "differ" only beyond
rounding: half a unit in the last decimal place of the coarser series (from the stored values, up to 6
places). If more values agree after moving B by a few days (up to SHIFT_DAYS either way), the pair is
reported as using different date conventions.
A FORECAST or CONSENSUS series and an ACTUAL one are not competing observations: such a pair is shown
with that label and never listed as a conflict.