Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a measuring tool for the instrument view. #5840

Closed
mantid-roman opened this issue Mar 19, 2012 · 3 comments
Closed

Create a measuring tool for the instrument view. #5840

mantid-roman opened this issue Mar 19, 2012 · 3 comments
Labels
Stale This label is automatically applied to issues that are automatically closed by the stale bot

Comments

@mantid-roman
Copy link
Contributor

This issue was originally TRAC 4994

The idea is that you click on one peak, its location is stored, then click on another and it will give you the difference in 2 theta, in phi between the two but most importantly it will calculate the angle between the two q-directions defined by these two points (the reason for this is that it can then be directly checked against the results of the print u.recAngle command). This is very useful when the crystal is not aligned. If it is aligned, this angle is either 2 theta (which we can read by doing a difference)/2 or phi, depending if your peaks are along a horizontal or vertical direction but if you look at non-orthogonal reflections or misaligned sample, it is no longer the case.
Pascal.

@mantid-roman
Copy link
Contributor Author

@NickDraper (2012-04-30T14:13:06):
Moved at end of release 2.1


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


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


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


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


@NickDraper (2013-07-26T13:54:59):
Moved to backlog at the code freeze for R2.6


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

@stale
Copy link

stale bot commented Feb 23, 2021

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 stale bot added the Stale This label is automatically applied to issues that are automatically closed by the stale bot label Feb 23, 2021
@stale
Copy link

stale bot commented Mar 2, 2021

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.

@stale stale bot closed this as completed Mar 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Stale This label is automatically applied to issues that are automatically closed by the stale bot
Projects
None yet
Development

No branches or pull requests

2 participants