Alan Garny

+1

That code is not commented out anymore in the Analyser class (see PR #631 and [this](https://github.com/cellml/libcellml/pull/631/files#diff-1e3c5ca0a6097079f5d14c7f7cb98bcbR1446-R1470) in particular). The reason that piece of code was originally commented out is that...

I am in favour of clearing old issues before doing a particular task. Think of a compiler, you don't need to clear previous issues before recompiling a model.

Hi @ganimede. Your MathML code contains some entity references (`∂`) and `QDomDocument,` which is used to read your MathML code, doesn't recognise it as such. You can see that by...

> I'm wondering if there is a way to split up the constants and variables so that there are, say for constants, two arrays passed into the computation RHS routines?...

I think we will need to discuss it among the libCellML team. The original plan was to make things as simple as possible when it comes to code generation, but...

Nothing is complicated _per se_. I just want to make sure that I understand everything. What would help is if you were to provide, for a given CellML file, the...

> Is there another requirement for computed_constants being separated? Having them separate will, I think, not help for my case. I guess they are cleaner in terms of intent in...

Thanks @chrispbradley, I am currently working on issue #1243 (which, although simple on the surface, requires quite a few changes here and there) when I have a bit of time...

Hmm... for me (and the analyser, as it currently stands) the VOI is not a constant. So, if `t` in `X(t) = A.sin(omega.t)` is the VOI then `X(t)` won't be...