MétaCan
Menu
Back to cohort
Record W4384347902 · doi:10.59697/jsik.v6i2.167

PENERAPAN DATA MINING PENGELOMPOKAN DATA PENGGUNA AIR BERSIH BERDASARKAN KELUHANNYA MENGGUNAKAN METODE CLUSTERING PADA PDAM LANGKAT

2022· article· id· W4384347902 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueJurnal Sistem Informasi Kaputama (JSIK) · 2022
Typearticle
Languageid
FieldComputer Science
TopicData Mining and Machine Learning Applications
Canadian institutionsKootenay Association for Science & Technology
Fundersnot available
KeywordsCluster (spacecraft)Cluster analysisHumanitiesComputer scienceArtOperating systemArtificial intelligence

Abstract

fetched live from OpenAlex

Permasalahan pelanggan memang sangat kompleks, oleh karena itu harus ditangani secara baik, jelas, dan tuntas. Pelayanan yang baik dari suatu perusahaan dapat menunjukan profesionalisme perusahaan itu sendiri, artinya keseriusan, kepastian waktu, ketepatan waktu dan hasil kerja yang dapat dipertanggung jawabkan dalam menyelesaikan semua permasalahan dapat membuktikan kualitas suatu perusahaan. Clustering merupakan proses partisi satu set objek data ke dalam himpunan bagian yang disebut dengan cluster. Objek yang di dalam cluster memiliki kemiripan karakteristik antar satu sama lainnya dan berbeda dengan cluster yang lain. Clustering sangat berguna dan bisa menemukan group atau kelompok yang tidak dikenal dalam data. Dari 2056 data keluhan pelanggan iperoleh hasil Cluter 1 yaitu 12, 5, 5, pada cluster 2 yaitu 4, 5, 5 dan cluster 3 yaitu 8, 2, 2. Dengan jumlah anggota cluster 1 883 anggota, cluster 2 635 anggota dan cluster 3 yaitu 538 anggota. Dari hasil cluster Matlab tersebut terdapat kesamaan hasil yaitu jenis keluhan pada cluster 1 dengan cluster 2 yaitu kode 5 jenis keluhan pipa bocor dengan peanganan kerusakan menyambung pipa air (gibout join).

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.005
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Science and technology studies, Scholarly communication, Open science, Research integrity
Consensus categoriesOpen science
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.658
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0050.000
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0010.002
Science and technology studies0.0050.000
Scholarly communication0.0020.006
Open science0.0200.036
Research integrity0.0000.003
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.063
GPT teacher head0.301
Teacher spread0.238 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it