Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standardize and improve RouteE Metadata #4

Open
nreinicke opened this issue Oct 23, 2023 · 0 comments
Open

Standardize and improve RouteE Metadata #4

nreinicke opened this issue Oct 23, 2023 · 0 comments

Comments

@nreinicke
Copy link
Collaborator

nreinicke commented Oct 23, 2023

Moved from internal repository.

Right now, RouteE models contain metadata that can be lost when flattening a model into a lookup table. After some discussion, it sounds like it would be a good idea to standardize how metadata is represented in both RouteE models and RouteE lookup tables.

In addition to a standard format, it would also be beneficial to add some more information about where a model came from and how it was trained. Some metadata we could potential add:

  • A training dataset tag - we could add a dataset tag so we can determine what dataset was used to train a model
  • Real world adjustments tag/coefficients - It would be a good idea to add a tag that indicates whether or not a model has had real world adjustments applied. This is mostly important for lookup tables since the base RouteE models can apply real world adjustments with the apply_real_world_adjustment parameter
  • Training dataset stats - it may be beneficial to add some metadata describing the training dataset. This could include stats such as number of cycles, average cycle length, etc.

If anyone has thoughts or potential additions, feel free to leave them here!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant