Skip to content

Bug: schema generation nests a high-level key in a value-dependent location #2

@ships

Description

@ships

This line shows how to save and load the information about each column's categorical precision:

https://github.com/SaferData/genjaxmix/blob/0cece36b6b30d015f863063764168f05e1453c8d/src/genspn/io.py#L50

however, the var_metadata key points to a dict of all the column names and their own parameters. This value means that undefined behavior will occur if the model is representing a column whose name is categorical_precisions. we should lift this key up a level.

However, we should do this outside of crunch time so we don't break existing schema loading.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions