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

Debye-Waller factor #38775

Open
wants to merge 14 commits into
base: main
Choose a base branch
from
Open

Debye-Waller factor #38775

wants to merge 14 commits into from

Conversation

KyleQianliMa
Copy link
Contributor

@KyleQianliMa KyleQianliMa commented Jan 31, 2025

Description of work

EWM 9033

DebyeWallerFactorCorrectionMD applies debye-waller factor correction to extract S(q, \omega) from scattering signal. It scales the signal by the inverse of debye-waller factor exp(^2 * <u^2>/3) assuming isotropic hamonic potnetial.

Summary of work

Further detail of work

To test:

Creating a fake MDevent works space and bin the intensity uniformly for 1000 counts between 1-4.
Observe the plotted data and see it was indeed scaled by an expotential function. Note the form should follow exp(x) not exp(-x) because we are scaling the intensity to remove debye-waller factor.

# Create a test MD workspace
ws = CreateMDWorkspace(Dimensions='1', Extents='1,4',
                     Names='|Q|', Units='A')
FakeMDEventData(ws, UniformParams=-6000)

# Run the algorithm
wsOut = DebyeWallerFactorCorrectionMD(ws, MeanSquaredDisplacement=0.15)

# Bin the result so that it can be printed
wsOut = BinMD(wsOut, AlignedDim0='|Q|,1,4,6')
ws = BinMD(ws, AlignedDim0='|Q|,1,4,6')

plt.plot([int(x) for x in ws.getSignalArray()])
plt.plot([int(x) for x in wsOut.getSignalArray()])
plt.show()

image


Reviewer

Please comment on the points listed below (full description).
Your comments will be used as part of the gatekeeper process, so please comment clearly on what you have checked during your review. If changes are made to the PR during the review process then your final comment will be the most important for gatekeepers. In this comment you should make it clear why any earlier review is still valid, or confirm that all requested changes have been addressed.

Code Review

  • Is the code of an acceptable quality?
  • Does the code conform to the coding standards?
  • Are the unit tests small and test the class in isolation?
  • If there is GUI work does it follow the GUI standards?
  • If there are changes in the release notes then do they describe the changes appropriately?
  • Do the release notes conform to the release notes guide?

Functional Tests

  • Do changes function as described? Add comments below that describe the tests performed?
  • Do the changes handle unexpected situations, e.g. bad input?
  • Has the relevant (user and developer) documentation been added/updated?

Does everything look good? Mark the review as Approve. A member of @mantidproject/gatekeepers will take care of it.

Gatekeeper

If you need to request changes to a PR then please add a comment and set the review status to "Request changes". This will stop the PR from showing up in the list for other gatekeepers.

@sf1919 sf1919 added this to the Release 6.13 milestone Feb 4, 2025
@sf1919
Copy link
Contributor

sf1919 commented Feb 4, 2025

This will also require a release note.

@KyleQianliMa
Copy link
Contributor Author

Will update once the PR is ready

@sf1919
Copy link
Contributor

sf1919 commented Feb 4, 2025

Apologies - I thought it was ready as it was not a draft PR.

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

Successfully merging this pull request may close these issues.

2 participants