Peningkatan Kesadaran Masyarakat Menghadapi Bencana Di Desa Tabing Rimbang Kabupaten Barito Kuala
Bibliographic record
Abstract
Disasters in South Kalimantan Province did not only occur at the provincial level but also at the village level such as in Tabing Rimbah Village, Mandastana District. Disasters that occur such as floods, fires, and winds. Service activities need to be carried out because they see various areas have the potential for disasters. The purpose of the service is to increase public awareness in dealing with disasters. Service activities are carried out so that public awareness in dealing with disasters increases. The community also becomes more alert and has prepared in dealing with disasters that can occur at any time. Service activities are carried out at the village level because the village is the smallest element in government that has a large enough role in dealing with disasters at the village level. The method used and applied to the service activities of lectures and discussions between participants and resource persons in the field of disaster and disaster communication is active. The people who were invited were representatives of each KK as many as 30 people. The community as participants in service activities is expected to be more active in tackling disasters in Tabing Rimbah Village. Service activities are expected to increase public awareness in dealing with various types of disasters, especially disasters in Tabing Rimbah Village such as floods, fires, and winds that almost routinely occur every year. Awareness raising was carried out through training activities and interactive discussions attended by village heads, community leaders, officials, and the community. The training materials provided are related to types of disasters, how to cope with disasters, knowledge about disaster-resilient villages, and disaster communication. The findings of this service activity are increasing public awareness in dealing with various types of disasters so that people will be more prepared and alert when disasters come so that casualties and property in affected areas can be minimized.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.001 |
| Science and technology studies | 0.004 | 0.001 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.020 | 0.002 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".