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

Better explain effect of smearing in concatenated data #354

Open
butlerpd opened this issue May 5, 2019 · 0 comments
Open

Better explain effect of smearing in concatenated data #354

butlerpd opened this issue May 5, 2019 · 0 comments

Comments

@butlerpd
Copy link
Member

butlerpd commented May 5, 2019

Following up on issue #353 where user was confused that when they applied the dQ from file they got spikes in their data which did not "look correct." The documentation was updated to indicate that resolution is worst next to beamstop so if you intercalate data from two setting you will mix points with bad resolution next to some with good. Also suggested this could be avoided by a simultaneous fit. While true this fails to emphasize to point out that SasView is demonstrating the fact that the intensity at a given Q should be different for different resolutions. This is important because most users do not understand this. More importantly, because they don't, they tend to scale data from different settings so that they "look" like they match in the overlap region - which is often wrong. Thus there is in fact value in noting that this fit actually provides valuable information: if the "spikiness" of the model is worse than the data, it is clear evidence the user incorrectly scaled their data which could be a nice sanity check.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant