chore: expose dynamic network propertys#1249
Conversation
|
All good about exposure of network attributes.
Not quite sure what a NetworkData class would improve. Let's discuss when I'm back.
No, it wouldn't be good style.
Does it hurt much to keep the compatibility? Would allow import of archived networks with newer PyPSA versions. |
It does not, I added |
|
(@lkstrp I’m afraid I’m thinking about this suggestion without enough context.) That said, in general there are plenty of use cases where it’s useful to work with the objective term (and more broadly n.model) manually:
|
Changes proposed in this Pull Request
n.model/n.objective/n.objective_constant/n.pypsa_versionare read-only without a settern.nameis also wrapped around but can be setNetworkDataclass which will separate logic from data, which will make things more stableiobackwards compatibility forv0.13.1andv0.18.0Checklist
doc.