Bibliographic record
Abstract
o r y o fWorthington Force is well known.During the second phase of Operation Totalize a battlegroup formed by the tanks of the British Columbia Regiment and the infantry of the Algonquin Regiment was ordered to capture a piece of high ground known as Point 195.In the pre-dawn darkness of 9 August 1944 the battlegroup set out on its mission.Rather than capturing Point 195, they found themselves on a different piece of high ground, near Point 140, some six kilometres northeast of their objective.Soon after daybreak the battlegroup was heavily attacked by German units in the area.Lieutenant-Colonel D.G. Worthington, the commanding officer of the BCRs and the overall commander of the force, made the fateful decision to stay put and await reinforcements.Unfortunately, nobody came to their rescue.Though small bodies of troops were able to escape, Worthington Force was destroyed losing 240 men killed, wounded and captured, 47 tanks and numerous other armoured vehicles and half-tracks.The odyssey of Worthington Force is one of the great enigmas of the Normandy campaign.In their advance to Point 140 the battlegroup crashed through the last major German defensive line, effectively opening the way to Falaise.Reinforcing this breakthrough with additional troops might have caused the entire German front north of Falaise to collapse.But nobody knew where to find Worthington Force.Communications with the battlegroup were lost before noon on 9 August and the limited attempts to find it were focussed on the vicinity of Point 195.Intermittent radio communications between the battlegroup and rear elements were made during the course of the day as were contacts with elements of the Polish Armoured Division, the artillery and aircraft of 2nd Tactical Air Force but the location of the battlegroup was never relayed to HQ 4th Canadian Armoured Brigade (4th CAB).How did Worthington Force get lost?C.P. Stacey, the official historian of the Canadian army, speculated "it seems clear that the regiment, fighting its first battle, and advancing across country with few landmarks and dealing with scattered opposition as it did so, simply lost its way." 1 After setting out for Point 195 in the early morning hours of 9 August the battlegroup encountered enemy fire diverting it from its intended route.As dawn broke high ground, assumed to be their destination, was sighted directly ahead.Stacey surmised that the battlegroup mistook a straight section of the road running from Estrées-la-Campagne to Mazières for the main Caen-Falaise highway.After crossing this road the battlegroup found a defensible position on the high ground and dug in.The battlegroup was repeatedly attacked by German forces until early evening when the position was finally overun ending the desperate battle.How could this happen?That a battlegroup could get lost and ultimately destroyed before reinforcements could arrive was unprecedented in Normandy, and perhaps in the course of the Second World War.The closest example was the destruction of elements of the British 22nd Armoured Brigade at Villers-Bocage on 13 June 1944, but it was never lost and its casualties were much lower than those of Worthington Force. 2 Until now this was our best understanding of the destruction of the battlegroup.Recently, new photographic evidence has emerged.
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.000 | 0.000 |
| Science and technology studies | 0.009 | 0.003 |
| Scholarly communication | 0.003 | 0.002 |
| Open science | 0.000 | 0.002 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.032 | 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".