quintel / etmoses

Online decision support tool to create local energy situations for neighbourhoods, cities and regions with a time resolution of 15 minutes created and maintained by Quintel – Not maintained
https://moses.energytransitionmodel.com
MIT License
11 stars 3 forks source link

The topology and the technology matrix #1489

Open grdw opened 7 years ago

grdw commented 7 years ago

Issue created from comment here

It might be worth exploring whether it still makes sense for technology_profile to be a column on testing_grounds. Perhaps this might be better placed in the topology row (since it maps directly to the topologies.graph - the technology_profile doesn't make much sense without the graph...)?

grdw commented 7 years ago

I'm really excited to do this. This enable to freely rename Topology nodes + you could very easily adapt the existing Topology editor to be used as an interface to select parts of the Technology Profile Matrix as once stated in an issue.

I do have some things that need to be researched like the maximum amount of data one column can hold before it becomes too large and Mysql starts complaining. A Les like Lochem might break?

I also had another idea. Where we would for each Topology end-node create a unique id. Than instead of the technology_profile_matrix column we would create a table called installed_technologies. And use that unique topology end-node id to couple the technologies with a topology end-node.

Also removing end-nodes becomes possible. With a big fat warning ofcourse saying "you're throwing away all your technologies if you do this".

Table installed_technologies

id | topology_id | end_node_id | technologies | created_at | updated_at |
-------------------------------------------------------------------------

However, I'm not sure if that's practical or faster or anything. 😆