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

rename some variables in Fury algorithm #11584

Closed
jmborr opened this issue Dec 9, 2014 · 1 comment
Closed

rename some variables in Fury algorithm #11584

jmborr opened this issue Dec 9, 2014 · 1 comment
Assignees
Labels
Indirect/Inelastic Issues and pull requests related to indirect or inelastic Low Priority Things that you don't ever want to be done.
Milestone

Comments

@jmborr
Copy link
Member

jmborr commented Dec 9, 2014

renaming of some variables so that they better fit their intended meaning.
Also some extra documentation here and there.

Testing:

  • Download ([https://www.dropbox.com/s/tijx4b4dbqky9xd/BASIS_33207_sqw.nxs?dl=0 sample file]) and [https://www.dropbox.com/s/pekunlgyd6ji2p7/BASIS_33213_sqw.nxs?dl=0 resolution file]
  • Open the Fury tab in the Indirect->"Data Analysis" interface and load both sample and resolution. By default, one should see:
Elow = -0.15
Ewidth = 0.0004
Ehigh = 0.15
SampleBinning = 1
  • Click in "Plot Result" and then in "Run".
@jmborr
Copy link
Member Author

jmborr commented Jun 3, 2015

This issue was originally trac ticket 10742

@jmborr jmborr added Low Priority Things that you don't ever want to be done. Indirect/Inelastic Issues and pull requests related to indirect or inelastic labels Jun 3, 2015
@jmborr jmborr self-assigned this Jun 3, 2015
@jmborr jmborr added this to the Release 3.3 milestone Jun 3, 2015
@jmborr jmborr closed this as completed Jun 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Indirect/Inelastic Issues and pull requests related to indirect or inelastic Low Priority Things that you don't ever want to be done.
Projects
None yet
Development

No branches or pull requests

1 participant