Clone Workspace Bug

[OwenArnold]

This issue was originally TRAC 5663

• Load SXD23767 from the system test data directory
• Clone SXD23767 using CloneWorkspace algorithm
• run LoadInstrument on the cloned SXD23767 workspace and use the attached IDF. Notice that bank 5 and bank 2 in the IDF are no different between the original and the attached one.
• Click Show instrument on both workspaces and compare the patterns with the Spherical Z view set. NOTICE THAT THE PATTERNS IN BANK 5 AND BANK 2 LOOK DIFFERENT BETWEEN THE TWO WORKSPACES!

Now repeat the steps above, but reload the original file instead of cloning it, do everything else the same, and notice that bank 2 and bank 5 look the same! So something is going wrong with the cloning step.

[OwenArnold]

@NickDraper (2012-08-10T12:43:10):
Moved at the end of release 2.2

---

@NickDraper (2012-10-28T11:38:23):
Moved to milestone 2.4

---

@NickDraper (2013-01-28T09:22:42):
Moved at the code freeze for release 2.4

---

@NickDraper (2013-04-29T09:49:27):
Moved to r2.6 at the end of r2.5

---

@NickDraper (2013-07-26T14:01:42):
Moved to the Backlog after R2.6

---

@NickDraper (2014-02-14T11:04:53):
Bulk move to assigned at the introduction of the triage step

[OwenArnold]

http://trac.mantidproject.org/mantid/raw-attachment/ticket/5663/SXD_Definition4.xml
(uploaded by @OwenArnold on 2012-07-31T11:19:02)

---

http://trac.mantidproject.org/mantid/raw-attachment/ticket/5663/cloned.png

(uploaded by @OwenArnold on 2012-07-31T11:19:20)

---

http://trac.mantidproject.org/mantid/raw-attachment/ticket/5663/original.png

(uploaded by @OwenArnold on 2012-07-31T11:19:27)

---

[OwenArnold]

For samuel

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you feel this is incorrect please comment to keep it alive, with a reason why.

To prevent closure, e.g. for long-term planning issues, add the "Never Stale" label.

[stale]

This issue has been closed automatically. If this still affects you please re-open this issue with a comment so we can look into resolving it.