Fabian Fröhlich

I see your point. My Primary issue is that interactive simulations are quite cumbersome at the moment. ExpData doesnt have any `ByName` setters or getters and the most of the...

> Yeah, could be more comfortable, agreed. > > > ExpData doesnt have any ByName setters or getters and the most of the members are immutable tuples > > Let's...

> Maybe off-topic with respect to setting parameters, but regarding convenient interactive use of `ExpData`: > If find it currently pretty inconvenient that I am expected to decide on the...

> I may have missed it. I know that I can change timepoints and the other members will grow / shrink accordingly, but I thought I need to re-set all...

> > How about we permanently add an ExpData instance to model where all parameters/fixpars are set and remove respective members from Model. > > Exactly what I meant. So...

> Okay, then it's not what I meant. I would avoid having those getters/setters twice. So if we want to keep them directly on the Model instance (which would be...

> As this is currently important in a project of @lcontento , we discussed the following ideas: > Technically, one can encode a spline directly in the SBML by hacking...

> I'm not sure what's meant with a "more general fashion". What should be more general? The python-sided parser? Or the C++-implementation for simulation? For splines, we had 2 use-cases...

> > it may be worthwhile setting this up in a more general fashion that also allows functions other than splines > > @FFroehlich : Greatly in favor of generalizing...

Static analysis won't tell us where those issues are? If things work for `-O3` (which is the default, right?) shouldn't they also work for `-O2`?