Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

PEtab extension for NLME

Offen
#566 20 Kommentare 5 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
25/100
Issue-Typ
Feature
Klarheit
Muss geklärt werden
Aktivitätsstatus
Veraltet
Bereich
data

Rechercherichtung

Start with the linked Google spreadsheet and the PEtab format context in this issue; no repository files or tests are identified. Clarify supported NLME use cases and agree on the extension's scope before locating implementation and validation work.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

extension

Which problem would you like to address? Please describe.
Currently, PEtab does not allow to express nonlinear mixed effects models (i.e containing fixed (population) and random (patient-specific) effects). These models are very common to represent inter-patient variability in pharmacological models. IIUC, such models are often represented in software like NONMEM, which was developed in the late 70s. I believe the field could benefit from a software independent model storage and exchange format.

Describe the solution you would like
In this spreadsheet, I have summarised a suggestion for a PEtab extension to introduce random effects in addition to the current format, which only allows to express fixed effects (happy to jump on a brief call to discuss in person).

Describe alternatives you have considered
There is a format called PharmML (Fig 2 here), which can express mixed effects, too. However, I don't think it is widely used yet, perhaps because the XML format is hard for humans to read and understand.

Additional context
I have no experience with NLME. While I have briefly discussed the suggestion linked in the spreadsheet with NLME experts, it would be good to get broader insight into a variety of use cases.

Vorherrschende Sprache
Keine Sprachdaten
Sterne
67
Forks
16
Ø Merge
1 T. 19 Std.
Gemergte PRs (30 T.)
1

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus PEtab-dev/PEtab

Alle Issues in PEtab-dev/PEtab

Ähnliche Issues

Weitere Issues zu Data Engineering

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.