Sam Yates
Sam Yates
Re `fmt` though, let's move that discussion though to a different issue (such as #514). I can see that `fmt` is good, but I'm less convinced that we need it.
We might not even have a standard C++ printed representation for these objects, and if we do, their purpose could be different to that of the Python `__str__`. It is...
You might note the question mark in those minutes — it was not agreed to!
And the reasons are exactly those mentioned here, and raised in the meeting: we don't have consistent representations C++ side, and different conversions are used for different purposes. Let's please...
For Python there is also the (IMO very reasonable) option of using the Python `print()` as exposed by pybind11.
I'm claiming that text representations on the C++ side is, essentially, a mess, and shouldn't form a basis for the Python representations without some sort of reform at the least....
To elaborate on the C++ side, there is a mix of representations: some are used just for debugging; some are used to provide a summary of an object state; some...
So, based on this issue and a convo with Brent, have made #1451. With that covering the C++ side, I propose that we repurpose this issue to focus on the...
It does indeed make sense! The only reason why we don't have one currently, is that we haven't implemented it. There is a complication in that while the calculation is...
If we have a branch which looks like (excuse the ASCII) `======------`, with greater attenuation in the thin tail, NEURON will divide the branch up equally into its `nseg` segments,...