Ruben Tikidji-Hamburyan
Ruben Tikidji-Hamburyan
@mstimberg Could you please give us an example of how to resolve a name clash? For example, if `iklt` in Rothman&Manis model has standard `m` and `h` instead of `w`...
Thinking about two questions above, it _seems_ that `eqs = Equations('dx/dt = ({x}/mV-x)/tau : 1', x='v')` should be OK, just extremely confusing. Brian can(must) flag it with warning, but should...
Aha, That is a great point @mstimberg! I use unitless or a mixture of "unitfull" and unitless models quite often. This ability to hide units in sub-expressions may be really...
`neurons.dendrite.ina.m` is what I think can make notation less messy. However, it isn't clear to me why you want to introduce `local:` flag? The structure of definitions should be enough...
> I don't quite see why multi-compartment vs. single-compartment makes a difference here, to be honest. The equations will not look any different. Because we may have different subunits of...
> I feel that this would limit things quite a bit to this specific way of constructing equations, though. Maybe in this case you can introduce a flag `global` if...
I like your `tau_scale=Equations('tau_scale_{name} : second (constant)')` - brilliant! IMHO, prefixes are better than suffixes. As in any unix system, /var/log/system.log looks better than system.log/log/var/ . Also in dot notation...
What isn't grate about your __perfect__ code is that there is `m` and there is `m_{suffix}` here ```python m=gating_var(name='m_{suffix}' ``` and it is easy to mess what is there. In...
> I hope you don't take this as defensive/returning the blame @mstimberg, you don't need to say this! It is nice and hopefully useful discussion between colleagues, good Brianstorm :smile:...
It seems you are proposing "flat" placeholder replacement. There is something confusing in your example (but it may be just me 0_0): in the line ```python m=gating_var(name='m_{suffix}', ``` you are...