spine-o-bot

In GitLab by @jkiviluo on Jul 3, 2020, 14:16 I'm ok either way. I was thinking that the code snippet would be the first step - something we can do...

In GitLab by @manuelma on Jul 6, 2020, 20:45 @mihlema and myself did some brainstorming about this on slack. Based on that, I wrote a proposal [here](https://gitlab.vtt.fi/spine/model/-/wikis/Specific-data-structure-for-running-custom-programs-in-SpineOpt). I think the...

In GitLab by @DillonJ on Jul 10, 2020, 10:12 So I had a go at implementing the decomposition structure using the approach described here : https://gitlab.vtt.fi/spine/model/-/wikis/Custom-programs-in-SpineOpt I think it works...

In GitLab by @manuelma on Jul 10, 2020, 11:32 The proposal was never meant to address 2, and I agree we should focus on that first, but that's a different...

In GitLab by @DillonJ on Jul 10, 2020, 12:57 Perhaps we need to think it through more - and work through some use cases. For example, during our case studies...

In GitLab by @DillonJ on Jul 10, 2020, 13:00 basically, alternative run_spinemodel codes that are somehow selectable?

In GitLab by @manuelma on Jul 10, 2020, 13:04 I think I am already sold on that we don't need the program generator data side, at least not right now....

In GitLab by @mihlema on Jul 10, 2020, 15:43 > So we need a way to make models coexist in the same db, while sharing the 'spatial' structure of nodes,...

In GitLab by @manuelma on Jul 10, 2020, 15:49 Those are good points, I generally agree. About this, `roll_temporal_structure(this_model)`, the problem is currently `roll_temporal_structure` takes no arguments, as the temporal...

In GitLab by @DillonJ on Jul 10, 2020, 16:01 One point is that I'm not sure that there is a direct link between between the model object in the datastore...