Bibliographic record
Abstract
The Roman calendar was first developed as a lunar calendar, so it was difficult for the Romans to reconcile this with the natural solar year. In 45 BC, Julius Caesar reformed the calendar, creating a solar year of 365 days with leap years every four years. This article explains the process by which the Roman calendar evolved and argues that the reason February has 28 days is that Caesar did not want to interfere with religious festivals that occurred in February. Beginning as a lunar calendar, the Romans developed a lunisolar system that tried to reconcile lunar months with the solar year, with the unfortunate result that the calendar was often inaccurate by up to four months. Caesar fixed this by changing the lengths of most months, but made no change to February because of the tradition of intercalation, which the article explains, and because of festivals that were celebrated in February that were connected to the Roman New Year, which had originally been on March 1.
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.006 | 0.014 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.006 | 0.011 |
| Scholarly communication | 0.009 | 0.005 |
| Open science | 0.001 | 0.004 |
| Research integrity | 0.001 | 0.004 |
| Insufficient payload (model declined to judge) | 0.006 | 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".