Goniometer calibration on TOPAZ

[VickieLynch]

This issue was originally TRAC 10199

The TOPAZ goniometer calibration is currently using an ISAW algorithm for finding and refining the goniometer offsets (in chi, phi, omega). This algorithm works very well and reliable.
We found that well calibrated goniometer zero positions are critical to high quality structure refinements due to stitching a substantial number of settings together in a quantitative manner.

However, trying the same calibration to find and refine goniometer offsets in Mantid does not give us a number unless the offset is very large. The Mantid algorithm does not have sufficient sensitivity.

This should be straight forward: A well working algorithm exists in ISAW and it is only necessary to copy the algorithm into the Mantid framework to produce the same results.

We need to use this calibration every time we change sample environment and swop goniometers. We will do this more frequently from the next cycle on when we have an ambient and a cryogenic goniometer.

For the corrections the runs TOPAZ_10116 - TOPAZ_10127 were used.
The settings were verified with TOPAZ_ 10220 to 10231.

Xiaoping has the done the data reduction, calculated the offsets and has the details. For further details please contact Xiaoping.

[VickieLynch]

@VickieLynch (2014-11-11T15:27:36):
Refs http://trac.mantidproject.org/mantid/ticket/10199 use same cost function as ISAW

0cd3ae9

---

@VickieLynch (2014-11-11T16:04:29):
Revert "Refs http://trac.mantidproject.org/mantid/ticket/10199 use same cost function as ISAW"

This reverts commit 0cd3ae9.

22c434b

---

@VickieLynch (2014-11-11T19:02:26):
Revert "Revert "Refs http://trac.mantidproject.org/mantid/ticket/10199 use same cost function as ISAW""

This reverts commit 22c434b.

36fc1f8

[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.