MétaCan
Menu
Back to cohort
Record W3161279880 · doi:10.31258/jil.13.2.p.162-178

PEMODELAN PERUBAHAN PENGGUNAAN LAHAN DI KABUPATEN KAMPAR

2019· article· en· W3161279880 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 Ilmu Lingkungan · 2019
Typearticle
Languageen
FieldAgricultural and Biological Sciences
TopicAgricultural Development and Management
Canadian institutionsWiLAN (Canada)
Fundersnot available
KeywordsLand useGeographyMarkov chainEnvironmental sciencePaddy fieldForestryAgroforestryMathematicsCivil engineeringStatisticsEngineering

Abstract

fetched live from OpenAlex

This study aims to analyze the drivers of land use change in Kampar District and to make modeling of land use changes in 2028. This study uses a survey method. To find out the factors driving the changes in land use in Kampar District were analyzed using binary logistic regression with a stepwise method. Forward land use prediction in 2028 with 3 scenarios was carried out by modeling using Markov Chain and Cellular Automata (CA). The results showed that the density population, altitude, slope, distance to the main road, distance to the river, and distance to the subdistrict city are the driving factors that influence changes in the use of forest land to plantations, forests to open land, mixed plantations to built up land, and mixed plantations to plantations in Kampar District The results of land use modeling in 2028 using CA-Markov with 3 scenarios indicate an increase or reduction in several types of land use, especially forests, plantations, paddy fields and built up land use, forest land use decreases widely in scenario I, and scenario II , on the contrary experience an increase in area in scenario III; plantation land use shows the addition of the three scenarios created; Likewise the developed land shows addition to all three scenarios; Furthermore, there is a reduction in paddy fields in scenario I and scenario II, but in scenario III the use of paddy fields does not experience any addition or reduction

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.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.590
Threshold uncertainty score0.951

Codex and Gemma teacher scores by category

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

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.011
GPT teacher head0.184
Teacher spread0.173 · 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