Issues with the Workspace/Algorithm history when loading from a nexus processed file

[Russell Taylor]

Aziz sent a processed nexus file which has highlighted a few problems.

• It takes ages to load - and it's getting stuck on the reading in of the history, which contains ~180 algorithms. Profiling and examination of the code shows that the WorkspaceHistory & AlgorithmHistory use vectors for their internal storage, which are then subjected to multiple inserts and push_backs. I'm surprised that this accounts for all the slowness, but it's certainly not right.

• Trying to create a python script from the history doesn't work - it only gives 2 entries (one being the LoadNexus). This could be because of the mechanism that was used to order the algorithms in the script, which is a counter in Algorithm (which has obviously been reset once you're in a different Mantid session).

[Russell Taylor]

Nexus file from Aziz

[Russell Taylor]

The slowness of loading is now covered under ticket #1074. Work on this ticket should concentrate on the fact that a history script can't be generated.

[Sofia Antony]

(In [4201]) re #1032 -fix for issues with algorithm history when loading from nexus processed file

[Sofia Antony]

(In [4202]) re #1032 -fix for build failure,

[Stuart Campbell]

This ticket has been transferred to github issue ​1880