Mechanics and kinematics of fluid uptake and intraoral transport in the leopard gecko
Bibliographic record
Abstract
Abstract Drinking permits amniote vertebrates to compensate for water loss. Lizards (non‐ophidian squamates) use their tongue to imbibe water, but for most lizards the tongue is also employed in other activities. To determine how these various demands can be accommodated alongside the tongue’s role in drinking, it is necessary to firstly determine the tongue’s function in water uptake and intraoral transport in a lizard that does not use this organ for chemoreception or food prehension. We selected the leopard gecko (Eublepharis macularius) for this purpose. We build upon previous morphological observations of the anatomy of its tongue and oral cavity and explore its drinking behaviour through high‐speed cinematography and cineradiography. This allows us to follow the movement of radio‐opaquely labelled water in association with tongue, jaw and throat movements. The tongue is modified to collect water and to release it into the anterior region of the buccal cavity. Repeated tongue cycles are associated with the shifting of the imbibed water into paired ventrolateral chambers and ultimately to its passage to a single, midline posterior chamber prior to swallowing. Tongue movements, capillarity and pressure changes due to hyolingual movements cause water to be moved posteriorly along specific pathways prior to swallowing, bypassing the airways and dorsal surface of the mid‐ and hind tongue. In this licking‐based lingually driven approach to drinking, only small volumes of water can be gathered at a time, with a drinking bout consisting of 20–30 tongue cycles before emersion and swallowing occur. This mechanism differs from drinking in turtles and snakes, which do not employ licking and may take in larger quantities of water. We advance the hypothesis that all lizards have conserved this pattern of tongue‐based water uptake and precisely directed intraoral fluid transport, with specializations for tongue‐based food capture and/or lingually based chemoreception being superimposed thereupon.
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.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
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".