spine-o-bot

In GitLab by @Tasqu on May 7, 2020, 05:12 This would be my first attempt as well, since there might be other features the user might want to tweak between...

In GitLab by @mihlema on Jun 11, 2020, 11:51 changed title from **{-Complex rolling structures might not be possible with current temporal structure-}** to **{+Linking related optimizations+}**

In GitLab by @mihlema on Jun 25, 2020, 10:57 I have been thinking about this a little bit also with respect to #183. I think I am in favor in...

In GitLab by @Tasqu on Jun 25, 2020, 11:55 Personally, I'm not against using separate input DBs for different `models`, albeit it sort of undermines the point of having a...

In GitLab by @mihlema on Jun 30, 2020, 08:18 I think we can't assume that each model handles the same `variables`. Even for Benders decomposition this is not the case...

In GitLab by @mihlema on Jun 30, 2020, 08:20 ## Linking models using different algorithms ### Problem identification At the moment, `run_spinemodel` does not support the linking of multiple models....

In GitLab by @jkiviluo on Jun 30, 2020, 11:57 I think your alternative #1 is much more simple than e.g. having multiple databases. Defining which units are in which model...

In GitLab by @manuelma on Jun 30, 2020, 20:56 I have to say this looks quite interesting. In principle, any program (or algorithm) can be represented using a tree-structure, so...

In GitLab by @jkiviluo on Jul 1, 2020, 11:16 While that looks really cool, I'm afraid how much work there will be to make it functional and versatile. Current graph...

In GitLab by @manuelma on Jul 1, 2020, 11:29 I agree it may require more resources than we actually have, unfortunately. I like your idea @jkiviluo, but I think we...