Bibliographic record
Abstract
The primary sources for analyzing Sultana 's sailing operation and performance were the Bruce and Inglis logbooks – primarily Bruce’s, as he tended to provide more detail about sail sets and changes, given his role on board. I prepared and used transcriptions of Bruce's logs of seven voyages: the transatlantic crossing from England to America from August to October 1768; a short coastal passage from Boston to Newport in December 1768; Virginia to Halifax in August 1770; Halifax to Virginia in October 1770; Virginia to Newport, October–November 1770; Boston to Philadelphia in October 1771; and the transatlantic crossing from Boston to England, October–December 1772. Important supplementary sources were the interviews conducted with experienced period replica schooner operators Drew McMullen, Aaron Thal, and Jan Miles, and the ensuing discussions of issues raised with Jan Miles and Nick Burningham.1 The overarching goal was to understand as much as possible about how the vessel was sailed: what sails were set in what conditions and why, and Sultana 's operational parameters in terms of wind direction, sea state, and speed. Such an effort relies on the principles established for the specialty of experimental archaeology, adapted to the exigencies of replica ship operation in the real world, as opposed to anything approaching laboratory conditions. The first task was to condense Bruce's log to information pertaining directly to sailing performance: wind direction, wind strength, course made good over the day's run, the day's run in nautical miles, the times of sail changes, and the details of those sail changes. For ease of use, I then converted the original point-system directions and bearings into degrees and minutes. I also eliminatedall days from this modified log for which no sailing performance data was provided. For wind strength, I used Bruce's and Inglis's terminology. As it is impossible to correlate, exactly, their terminology to the modern Beaufort Scale, I would introduce less uncertainty and/or error into the interpretations by sticking to their terms. As is typical of eighteenth-century verbiage, Bruce's and Inglis's ‘weather categories’ are not strictly consistent. For example, I am confident that ‘light breezes and calms’ is the same as ‘light breezes mixed with calms.’
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.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.002 | 0.001 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.013 | 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".