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

Modification of the gravitationalDrop method of MatrixWorkspace #12574

Closed
AntonPiccardoSelg opened this issue May 11, 2015 · 2 comments
Closed
Assignees
Labels
Framework Issues and pull requests related to components in the Framework SANS Issues and pull requests related to SANS
Milestone

Comments

@AntonPiccardoSelg
Copy link
Contributor

'''Original email from Richard:'''

Dear all

We are not applying enough gravitational drop in the SANS data reduction, as I had assumed that the beam was horizontal at the sample. In fact it is actually horizontal half way along the beam defining collimation L1, before the sample. (Note here, that as in the Q resolution calculations, L1 is the incident collimation length, which varies 4m to 12m on SANS2d, L1 is not the source to sample distance ~19m on SANS2d).

We are currently using drop = gconst_(wav^2)(L2)^2, but need instead gconst_(wav^2)_(L1_0.5+L2)^2

Usually for the rear detector the sample-detector distance L2 is set the same as L1, so since drop ~ wav^2.L^2 we could be off by as much as

{(L2+(L1)/2)/(L2) }^2 ~ 9/4 = 2.25

I have fit the beam centre at 11 and 5.5 angstrom for run 28222 (iron oxide) at L2=12m, despite some noisy curves, the difference in beam height is 5.1mm, even with “gravity on”, which is exactly what the correct formula predicts should be the case, as per table at bottom of attached spreadsheet.

I would like to correct the cpp routine at the end of this email by putting in a + LEXTRA to the calculation as shown in double MatrixWorkspace::gravitationalDrop, where LEXTRA defaults to zero and has a value passed from the user file and gui.

LEXTRA is likely L1*0.5 but may be less than this depending on where scraper baffles are inside the collimation.

Can this be done, urgently, please,

Thank you,

Richard

PS alas this does not solve any of our “background” at 12m issue, as the current beam centre is dominated by the long wavelengths, however it will improve the shape of the I(Q).


Keywords: SANS

@AntonPiccardoSelg
Copy link
Contributor Author

This issue was originally trac ticket 11736

@AntonPiccardoSelg AntonPiccardoSelg added Framework Issues and pull requests related to components in the Framework SANS Issues and pull requests related to SANS labels Jun 3, 2015
@AntonPiccardoSelg AntonPiccardoSelg self-assigned this Jun 3, 2015
@AntonPiccardoSelg AntonPiccardoSelg added this to the Release 3.5 milestone Jun 3, 2015
@AntonPiccardoSelg
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Framework Issues and pull requests related to components in the Framework SANS Issues and pull requests related to SANS
Projects
None yet
Development

No branches or pull requests

1 participant