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

Detector spherical dilation (parallax) #12089

Closed
NickDraper opened this issue Mar 4, 2015 · 5 comments
Closed

Detector spherical dilation (parallax) #12089

NickDraper opened this issue Mar 4, 2015 · 5 comments
Labels
Awaiting User Response Waiting on input or testing from a third party ISIS Team: LSS Issue and pull requests managed by the LSS subteam at ISIS Low Priority Things that you don't ever want to be done. Reported By User Issues that were found or highlighted by a user/scientist SANS Issues and pull requests related to SANS Stale This label is automatically applied to issues that are automatically closed by the stale bot

Comments

@NickDraper
Copy link
Contributor

sans_feature
This issue was originally TRAC 11250

(for larger solid area of pixels at wider angles)

Now know where the detectors are within 2 mm (ISIS). Hence this now makes this relevant. SNS not expecting this to have much effect yet but would like to follow discussions

Priority 2 (pretty high)
Contacts:

  • William Heller

  • Richard Heenan

  • Andrew Jackson (ESS)

    Keywords: SSC, 2015, All, sansCorr

@NickDraper
Copy link
Contributor Author

@NickDraper (2015-03-10T15:49:02):
Batch modify all SSC tickets to critical priority (this will also show up as an update for all those already as critical)

@NickDraper NickDraper added High Priority An issue or pull request that if not addressed is severe enough to postponse a release. SANS Issues and pull requests related to SANS SSC labels Jun 3, 2015
@NickDraper NickDraper added this to the Release 3.5 milestone Jun 3, 2015
@NickDraper NickDraper modified the milestones: Release 3.5, Release 3.6 Sep 14, 2015
@NickDraper NickDraper modified the milestones: Release 3.6, Release 3.7 Jan 22, 2016
@NickDraper NickDraper modified the milestones: Release 3.8, Release 3.9 Oct 3, 2016
@NickDraper NickDraper modified the milestones: Release 3.9, Temporary Holding Oct 14, 2016
@NickDraper NickDraper removed this from the Temporary Holding milestone Oct 3, 2017
@gemmaguest gemmaguest added the ISIS Team: LSS Issue and pull requests managed by the LSS subteam at ISIS label Aug 29, 2019
@gemmaguest gemmaguest removed the High Priority An issue or pull request that if not addressed is severe enough to postponse a release. label Oct 2, 2019
@smk78 smk78 added the Low Priority Things that you don't ever want to be done. label Jul 16, 2020
@smk78
Copy link
Contributor

smk78 commented Jul 16, 2020

The SANS Group need to remind themselves what this is about.

@smk78 smk78 closed this as completed Jul 16, 2020
@smk78 smk78 reopened this Jul 16, 2020
@gemmaguest gemmaguest added the Reported By User Issues that were found or highlighted by a user/scientist label Jul 29, 2020
@gemmaguest gemmaguest added the Awaiting User Response Waiting on input or testing from a third party label Jul 29, 2020
@stale
Copy link

stale bot commented Feb 22, 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 22, 2021
@smk78 smk78 added Never Stale and removed Stale This label is automatically applied to issues that are automatically closed by the stale bot labels Feb 22, 2021
@stale
Copy link

stale bot commented Aug 30, 2021

This issue has been automatically marked as stale because it has not had activity in 6 months. It will be closed in 7 days if no further activity occurs.
Allowing issues to close as stale helps us filter out issues which can wait for future development time. All issues closed by stale bot act like normal issues; they can be searched for, commented on or reopened at any point.
If you'd like a closed stale issue to be considered, feel free to either re-open the issue directly or contact a developer.
To extend the lifetime of an issue please comment below, it helps us see that this is still affecting you and you want it fixed in the near-future. Extending the lifetime of an issue may cause the development team to prioritise it over other issues, which may be closed as stale instead.

@stale stale bot added the Stale This label is automatically applied to issues that are automatically closed by the stale bot label Aug 30, 2021
@stale
Copy link

stale bot commented Sep 6, 2021

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

@stale stale bot closed this as completed Sep 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting User Response Waiting on input or testing from a third party ISIS Team: LSS Issue and pull requests managed by the LSS subteam at ISIS Low Priority Things that you don't ever want to be done. Reported By User Issues that were found or highlighted by a user/scientist SANS Issues and pull requests related to SANS Stale This label is automatically applied to issues that are automatically closed by the stale bot
Projects
Status: Stale
Development

No branches or pull requests

7 participants