MétaCan
Menu
Back to cohort
Record W2139785321 · doi:10.1002/jcc.21726

Combination of the CHARMM27 force field with united‐atom lipid force fields

2010· article· en· W2139785321 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueJournal of Computational Chemistry · 2010
Typearticle
Languageen
FieldBiochemistry, Genetics and Molecular Biology
TopicLipid Membrane Structure and Behavior
Canadian institutionsUniversity of Calgary
FundersCanadian Institutes of Health Research
KeywordsForce field (fiction)Lipid bilayerNucleic acidChemistryMolecular dynamicsField (mathematics)Atom (system on chip)Computational scienceComputer scienceComputational chemistryMembraneMathematicsBiochemistryArtificial intelligence

Abstract

fetched live from OpenAlex

Computer simulations offer a valuable way to study membrane systems, from simple lipid bilayers to large transmembrane protein complexes and lipid-nucleic acid complexes for drug delivery. Their accuracy depends on the quality of the force field parameters used to describe the components of a particular system. We have implemented the widely used CHARMM22 and CHARMM27 force fields in the GROMACS simulation package to (i) combine the CHARMM22 protein force field with two sets of united-atom lipids parameters; (ii) allow comparisons of the lipid CHARMM27 force field with other lipid force fields or lipid-protein force field combinations. Our tests do not show any particular issue with the combination of the all-atom CHARMM22 force field with united-atoms lipid parameters, although pertinent experimental data are lacking to assess the quality of the lipid-protein interactions. The conversion utilities allow automatic generation of GROMACS simulation files with CHARMM nucleic acids and protein parameters and topologies, starting from pdb files using the standard GROMACS pdb2gmx method. CMAP is currently not implemented.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.005
Threshold uncertainty score0.229

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.004
GPT teacher head0.232
Teacher spread0.227 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it