List view

• Release 2.5

  No due date

  •2/3 issues closed
  66% complete1 open2 closed

• Improve clarity of error messages

  We shall improve the robustness in terms of clarity of runtime error messages, for example in the case of improper user input.

  No due date

  •3/7 issues closed
  42% complete4 open3 closed

• Improve numerical accuracy

  Efforts towards improvement of the accuracy.

  No due date

  •1/4 issues closed
  25% complete3 open1 closed

• Efficiency and improved internal organization

  This is a quality of code milestone related to improvements to memory/cpu consumption figures along with reorganization of code to better support future extensions.

  No due date

  •22/37 issues closed
  59% complete15 open22 closed

• Fix bugs

  Some fixes that haven't got addressed yet but should be dealt with with some urgency.

  No due date

  •27/40 issues closed
  67% complete13 open27 closed

• Improve (hybrid) dynamics in terms of usability

  Support more generalised systems and use a more flexible input/output.

  No due date

  •7/16 issues closed
  43% complete9 open7 closed

• Improve user experience

  We need to polish the examples and tutorials, complete the interfaces that are not fully developed and improve user experience wherever possible.

  No due date

  •34/46 issues closed
  73% complete12 open34 closed