What to do when converting LoadMuonNexus to use the new File Nexus Interface

[Karl Palmen]

An investigation #4037 suggests that when we would change LoadMuonLog to use the new Nexus File interface, it would be good instead to get the LoadNexusLogs to do the work of LoadMuonLog and withdraw the latter algorithm.

[Nick Draper]

Moved to iteration 33 at iteration 32 code freeze

[Russell Taylor]

Noticed that the following commit did not make it into this ticket:

commit ff60c8d4dcb223564888dc895b968abbb4e46cae
Author: Karl Palmen <karl.palmen@stfc.ac.uk>
Date:   Fri Dec 16 10:33:57 2011 +0000

    Changes made towards making LoadNexusLogs.cpp load Muon Nexus Data
    
    This may be useful for re #4329. Saved in branch muon_nexus_in_nexus.

This commit currently exists only on the branch mentioned above, and not in master. It's the only unmerged commit on that branch.

[Karl Palmen]

The work committed to this branch is not complete.

[Nick Draper]

Moved at end of release 2.1

[Nick Draper]

http://www.mantidproject.org/Release_Notes_2_2_Full_List

[Nick Draper]

Moved to release 2.4

[Nick Draper]

Moved to the Backlog after the code freeze for R2.6

[Russell Taylor]

The branch mentioned above is the oldest one still sitting on github. I propose to delete it - the small changes are to files that will have moved on a long way since then (and I'm not sure touching LoadTOFRawNexus was the right thing to do anyway). Let me know if you object.

Is this ticket even still relevant?

[Karl Palmen]

I expect this ticket is obselete, but I want Anders to comment on it.

[Anders Markvardsen]

Yes please close this ticket and delete this branch. Thanks

[Karl Palmen]

You may test by verifying the banch muon_nexus_in_nexus does not exist.

[Martyn Gigg]

Confirmed that the commit mentioned is not in master and that the branch is gone.

[Stuart Campbell]

This ticket has been transferred to github issue ​5176