Don C.

The documentation for `Choices` is located on https://github.com/JacquesCarette/Drasil/wiki/The-Code-Generator I did document `codeSpec`, but it is not completed. This is ticket is partially overlap with what @peter-michalski did in #2961. The...

In the Drasil framework, we have options to generate modularized software. The modularized software contains a controller module, an input module, a calculation module and an output module. In all...

I just wonder does ```let ... in ...``` ok to handle the nested syntax? For nested syntax, I mean we can write ```let ... in ...``` inside of ```let ......

@smiths The **3.3 Output an ODE** is the section I made significant changes. Some specifications were inspired by [MIS for the ODE Solver module for the SWHS example](https://github.com/smiths/swhs/blob/master/docs/Design/MIS/PCM_MIS.pdf). Suggestions on...

This ticket seems discussed the same issue with #2975. I will make comments on #2975.

This ticket is partially complete. There are two ways to build the `ODEInfo`. - set the ODEInfo explicitly. This is sometimes called writing equations manually. Basically, we rewrite the ODE...

@balacij 'fully automated', I mean Drasil would automatically generate a system of ODE. Drasil can generate a single high-order ODE for the solver without explicitly writing it down, but it...

@smiths I can create a ticket if that is the preferable approach. Should we close this ticket and create a new one for automatically handling the system of higher-order ODE?...

I created #3385 and closed this one.

In short, the `theta` is only for solving the higher-order ODE. It is a hack to make the ODE solver works. It does not belong to the SRS. More like...