Review MaxEnt Testing Situation

[Peter Parker]

Currently we are providing the MaxEnt algorithm to users via the script repo. This has its benefits, but unfortunately it means that the unit tests we have for it are only ever run manually.

We need a way to have these tests run automatically, since we have already had our first instance where a change elsewhere has had a detrimental knock-on effect for MaxEnt.

A couple of options are open to us:

• Provide the ability to run script repository tests, though this would require some thought about where data would be stored, etc.

• Bring MaxEnt in to the main repository, perhaps when we're sure the algorithm is not going to change much and we won't need to keep on adding binary .pyd files.

[Peter Parker]

A further problem caused by providing the algorithm via the script repo is that when we make a change that is not backwards compatible with earlier versions of Mantid, we break the algorithm for anybody using old versions. They may even have "auto-update" checked, in which case even if they don't update themselves the algorithm could still break.

[Nick Draper]

Moved to the backlog at the code freeze of R3.3

[Anders Markvardsen]

Just happen to notice this one. Rachel started maxent help request investigation yesterday from James

[Stuart Campbell]

This ticket has been transferred to github issue ​10569