List view
This milestone release will focus on improvements to testing, both in terms of automation script usage and the conventions and structure around writing tests. It will also include various implementations of new testbeds for ogd-common modules.
No due date•2/4 issues closedThis release milestone will include significant work to improve interfaces by directly allowing filtering at the event level.
No due date•0/5 issues closedThis includes expansions and adjustments to current event schema, in conjunction with attempt to develop a standard with OGD community. Things we're very likely to add/change: * App and Log versions use `SemanticVersion` type * Add a `time_since_launch` (or similar name) field to record how much session time elapsed up to given event * Add `event_code` field, to record a numeric code representing the event type (`event_name` would be technically redundant, but more human-readable). * Some kind of `annotations` field, likely as another JSON-encoded element, which would map annotation/annotator names to annotation values. For example: * An 'affective state' annotation from human-coding tools that marks an event as part of a period of "struggle", "confusion", "frustration", or "success" * A 'player type' annotation that marks events for a given player with one-hot encodings for type 1, 2, and 3; i.e. there are 3 annotations, and a 1 or 0 for each.
No due date•0/3 issues closedThis milestone release will include changes to allow for smarter, nicer configuration options. This includes smart "Load" functions that can find config files without relying on execution within a known source code checkout, as well as more options for file formats. It also expands the level of detail and general philosophy of our dataset metadata outputs. Where we previously had a dataset `.meta` file with basic info about the dataset, and an independent `README.md` included with each file, we will now have a "manifest" file that gives structured, machine-friendly details about the dataset, how it was generated, etc. The `README.md` will use the manifest as a primary source of info on the features included in the dataset.
Overdue by 14 day(s)•Due by April 10, 2026•6/16 issues closedMajor release with significant refactorings to get the common files ready for running tools from packages, plus doing better I/O on configs and data.
Overdue by 1 month(s)•Due by March 13, 2026•147/153 issues closed