-
Notifications
You must be signed in to change notification settings - Fork 150
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
Data Model Renaming #423
Comments
I would be interested in reaching some convergence between what I want to achieve in PowerSystems and PowerModels' data structure and naming. |
By all means. All proposals are welcome in this thread. |
We may want to start with including energy, and time symbols here, define suffixes for all entities (e.g. To which degree should we attempt to future-proof the data model (e.g. angle range of phase-shifting transformers or tap range of OLTC transformers)? |
My goal would be to come up with something like a style guide for parameter names, similar to what we did for variables in #26, then update the data model to be consistent with those conventions. I would not be overly concerned with future-proofing. I think just covering the all the parameters we have will provide fairly robust guidelines. |
Making the convention consistent with PowerSystems/Simulations would be a great goal @claytonpbarrows |
@frederikgeth when we do this renaming, should we rename |
In favor of being explicit in terms of power and current for ratings instead of 'thermal'. (A thermal limit eventually should be the maximum acceptable conductor temperature.) |
Revisit the names for everything in the data model and update to consistent and clean naming conventions.
@frederikgeth, this is not coming anytime soon, but we can bike shed about it in this thread.
The text was updated successfully, but these errors were encountered: