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

Interpolation Rebin #2072

Closed
NickDraper opened this issue Apr 30, 2010 · 1 comment
Closed

Interpolation Rebin #2072

NickDraper opened this issue Apr 30, 2010 · 1 comment
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release.
Milestone

Comments

@NickDraper
Copy link
Contributor

I think this boils down to a special interpolating rebin algorithm.

Follow up and ask him for the formulae he mentions and see if we need further info than that.

From Richard Heenan:

I am looking again at normalization using M1 rather than M2 at long sample-detector distances.

There is an issue here in that the time bins for M1 are a little too coarse, converting to wavelength bins of e.g. 0.5481549 in equal steps of 0.41113 angstrom. If the data reduction is asked for in smaller steps than this, or without matching boundaries, then some odd things may happen.

Would it be possible to interpolate M1 and M2 (say using a local cubic interpolation – I can give you the formulae) rather than use the normal rebin?

Also we will need a separate option to use M1 rather than M2 for the transmission calculation please, though this is not so urgent just yet…

@NickDraper
Copy link
Contributor Author

This issue was originally trac ticket 1225

@NickDraper NickDraper added the High Priority An issue or pull request that if not addressed is severe enough to postponse a release. label Jun 3, 2015
@NickDraper NickDraper added this to the Iteration 23 milestone Jun 3, 2015
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.
Projects
None yet
Development

No branches or pull requests

1 participant