Resource limitation has a limited impact on the outcome of virus–fungus co‐infection in an insect host
Bibliographic record
Abstract
Abstract Infection by pathogens is strongly affected by the diet or condition of the prospective host. Studies that examine the impact of diet have mainly focused on single pathogens; however, co‐infections within a single host are thought to be common. Different pathogen groups might respond differently to resource availability and diverse infections could increase the costs of host defense, meaning the outcome of mixed infections under varying dietary regimes is likely to be hard to predict. We used the generalist cabbage looper, Trichoplusia ni and two of its pathogens, the DNA virus T. ni nucleopolyhedrovirus (TniSNPV) and the entomopathogenic fungus, Beauveria bassiana to examine how nutrient reduction affected the outcome of mixed pathogen infection. We challenged insects with a low or high effective dose of virus, alone or combined with a single dose of fungus. We manipulated food availability after pathogen challenge by diluting artificial diet with cellulose, a non‐nutritious bulking agent, and examined its impact on host and pathogen fitness. Reducing diet quantity did not alter overall or pathogen‐specific mortality. In all cases, TniSNPV‐induced mortality was negatively affected by fungus challenge. Similarly, B. bassiana‐induced mortality was negatively affected by TniSNPV challenge, but only at the higher virus dose. Dietary dilution mainly affected B. bassiana speed of kill when mixed with a high dose of TniSNPV, with an increase in the duration of fungal infection when cellulose was low (high quantity). One pathogen dominated the production of transmission stages in the cadavers and co‐infection did not affect the yield of either pathogen. There was no evidence that co‐infections were more costly to the survivors of pathogen challenge. In conclusion, dietary dilution did not determine the outcome of mixed pathogen infection, but it had more subtle effects, that differed between the two pathogens and could potentially alter pathogen recycling and host–pathogen dynamics.
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.001 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 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".