clinssen
clinssen
Suggestion from @heplesser: to ward against confusion between variable names and unit literals, NESTML should allow unit literals to appear only directly after numeric literals, for example, ``V' = 2...
Including the relevant report from @tomtetzlaff here about the ignore_and_fire neuron model. In my original version, I had defined the variable ``` phase_steps integer = steps( max(0.,phase) / firing_rate )...
- Should we generate a dummy, temporary variable for a convolution with a delta kernel? - Should spiking input port names be allowed inside ODEs? - It's ambiguous where the...
Perhaps we could eliminate the use of ``.upper()`` to uppercase variable names in the generated code (and also move to C++ enum class for ``StateVecElems`` to ensure proper scoping of...
@WillemWybo : thanks for reporting this. I will look into it, could you help in define the semantics of the division operator? Should we be Python-like and have ``/`` always...
We could also introduce the Python ``//`` operator for integer (actually, "floor") division. This means that ``a/b`` would always be rendered in C++ as something like ``((float)a)/((float)b)``. But note that...
We would suggest to make ``/`` always be Python3-like floating point division, and to make ``//`` always be the C-like "true" integer division, where the result is always of integer...
Isn't this an issue with NEST Simulator, namely that nest-config is not returning the right path?
See https://github.com/nest/nest-simulator/pull/2543. Todo: replace https://github.com/nest/nestml/blob/d37cf6720a308acfd2a5b02b9b2bdc2102cd62eb/pynestml/codegeneration/resources_nest/point_neuron/setup/CMakeLists.txt.jinja2#L110 with a check that compiler ID matches. Should there be a check on compiler versions as well? (Equality would not be adequate as a slightly-newer...