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

[mantid-builder]

Original Reporter: 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).

[mantid-builder]

This issue was originally trac ticket 1032

[mantid-builder]

http://trac.mantidproject.org/mantid/raw-attachment/ticket/1032/van_s2_new_corr-0.nxs
(uploaded by Russell Taylor on 2009-11-24T11:08:00)

---