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

Allow unit conversions without an instrument #12082

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

Allow unit conversions without an instrument #12082

NickDraper opened this issue Mar 4, 2015 · 2 comments
Assignees
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Indirect/Inelastic Issues and pull requests related to indirect or inelastic
Milestone

Comments

@NickDraper
Copy link
Contributor

This issue was originally TRAC 11243

Integration of 'Detector.dat' type parameter table. (Timmy)

  • Could this be used for a coherent approach to applying calibration values.
  • Make it easy to change IDF variables

The underlying wish for this is to be able to inject L1, L2, 2theta and efixed values in to override Instrument values, either when there are none or hey are considered incorrect.


Keywords: SSC, 2015, SNS, indirectShort

@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. Indirect/Inelastic Issues and pull requests related to indirect or inelastic 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
@stuartcampbell
Copy link
Collaborator

A prototype has been done and merged (see http://docs.mantidproject.org/nightly/algorithms/ConvertUnitsUsingDetectorTable-v1.html)

A new issue should be raised for problems arising from it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Indirect/Inelastic Issues and pull requests related to indirect or inelastic
Projects
None yet
Development

No branches or pull requests

2 participants