Ticket #3078 (closed: fixed)
The can and sample workspaces aren't filling the same Q range
Reported by: | Steve Williams | Owned by: | Steve Williams |
---|---|---|---|
Priority: | critical | Milestone: | Iteration 30 |
Component: | Mantid | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: | Anders Markvardsen |
Description
As Richard says below after a reduction the can and sample workspaces that are produced should have the same range in Q:
I am going mad again. I am changing the minimum radius in the gui to compare results.
Depending on the order I do things in I can get less bins at the minimum Q in the can that in the sample or (sample-minus-can) result, as per attached plot. (Was 1.28.11783 of Weds 18 May) “Show data†on the workspaces confirms there are 2 less points at the start of the can_tmp workspace
Is Mantid “caching†the can results from a previous round and not noticing I have changed the radius ???? – if so then what background is it actually subtracting off the first few points ?
Richard
Change History
comment:4 Changed 9 years ago by Nick Draper
- Milestone changed from Iteration 29 to Iteration 30
Accepted and assigned tickets moved at iteration 29 code freeze
comment:5 Changed 9 years ago by Steve Williams
Perhaps this is not a problem since ticket #3105. We could check again what Richard Heenan thinks.
comment:6 Changed 9 years ago by Steve Williams
There are still problems! Richard has replyed with another test case. Place these runs into the SANS GUI
Tr db Sam 7187 7185 7182 Can 7179 7183 7182
In that case the workspaces:
7178rear_1D_1.75_14.0
7178rear_1D_1.75_14.0_sam_tmp
7178rear_1D_1.75_14.0_can_tmp
must all have common bins.
comment:9 Changed 9 years ago by Steve Williams
- Status changed from accepted to verify
- Resolution set to fixed
In [13574]:
comment:10 Changed 9 years ago by Anders Markvardsen
- Status changed from verify to verifying
- Tester set to Anders Markvardsen
comment:12 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 3925
A set of test runs for this is 7174 7098 7097 7176 7096 7097 I'm looking for an effect in the geometry as suggested here:
Just tried going back to 2-12 in the user file L/WAV and TRANS/FIT (rather than 1.75 to 14 as before)
The TRANS/FIT box seems not to pick up what is in the user file, my gui “remembered†a 14 ang max from previous session?
And it still give different Q range for the “canâ€
PREVIOUS COMMENTS could be a red herring as 14/12 = 1.166, is also very close to 47/41 = 1.146 the different beam stop radii !
Have now SWAPPED the sample and can, the weaker scattering run 7176-add has the missing Q bins at small Q, so perhaps, As Steve suggested this morning, perhaps it is an “empty bin†causing truncation somewhere ??? or something odd in the geometry ??
Richard