You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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:
If anyone has thoughts or potential additions, feel free to leave them here!
The text was updated successfully, but these errors were encountered: