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

IndirectQuickRun algorithm #14616

Closed
3 tasks
ElliotAOram opened this issue Nov 27, 2015 · 7 comments
Closed
3 tasks

IndirectQuickRun algorithm #14616

ElliotAOram opened this issue Nov 27, 2015 · 7 comments
Assignees
Labels
Indirect/Inelastic Issues and pull requests related to indirect or inelastic

Comments

@ElliotAOram
Copy link
Contributor

The MSG have asked for an algorithm that does the following:

  • Loads in .raw or .nxs files
    • if files are .raw reduce them using data reduction
  • Runs the files through the Elwin algorithm
  • Optional run through Iqt

The purpose of this is to get an overview of data quickly and in an automated way.

Iqt option removed as it's input can not be produced automatically

@ElliotAOram ElliotAOram added the Indirect/Inelastic Issues and pull requests related to indirect or inelastic label Nov 27, 2015
@ElliotAOram ElliotAOram self-assigned this Nov 27, 2015
@ElliotAOram ElliotAOram added this to the Release 3.6 milestone Nov 27, 2015
@SpencerHowells
Copy link

Iqt is not a 'black-box', it needs thought about the input. If _red workspaces are created, just run Iqt.

ElliotAOram pushed a commit that referenced this issue Nov 30, 2015
ElliotAOram pushed a commit that referenced this issue Nov 30, 2015
ElliotAOram pushed a commit that referenced this issue Nov 30, 2015
ElliotAOram pushed a commit that referenced this issue Nov 30, 2015
@SpencerHowells
Copy link

Not at all happy with Iqt option! Iqt comes with a health warning - need to be careful with number of points, energy range and energy bin otherwise the result can be rubbish!! Itr is not a black-box and should NOT be automatic.

@ElliotAOram
Copy link
Contributor Author

@SpencerHowells Probably best to exclude I(Q,t) from the algorithm completely in this case then.

@NickDraper NickDraper modified the milestone: Release 3.6 Jan 22, 2016
@ElliotAOram
Copy link
Contributor Author

This will also resolve #12270

@ElliotAOram
Copy link
Contributor Author

I've commited the latest version of the algorithm (hopefully it should only require a test and documentation)

@SpencerHowells
Copy link

The algo name is too vague. Can you change it to IndirectEnergyWindowScan.

@louisemccann
Copy link
Contributor

The EnergyWindowScan depends on a slightly modified version of MSDFit. This modified version outputs in a slightly different way, so plotting will need to be refactored.

louisemccann added a commit that referenced this issue Oct 25, 2016
louisemccann added a commit that referenced this issue Oct 25, 2016
louisemccann added a commit that referenced this issue Oct 25, 2016
louisemccann added a commit that referenced this issue Oct 26, 2016
louisemccann added a commit that referenced this issue Oct 26, 2016
louisemccann added a commit that referenced this issue Oct 26, 2016
louisemccann added a commit that referenced this issue Oct 26, 2016
louisemccann added a commit that referenced this issue Oct 26, 2016
louisemccann added a commit that referenced this issue Oct 27, 2016
louisemccann added a commit that referenced this issue Oct 28, 2016
louisemccann added a commit that referenced this issue Nov 2, 2016
# Conflicts:
#	docs/source/release/v3.9.0/indirect_inelastic.rst
louisemccann added a commit that referenced this issue Nov 2, 2016
louisemccann added a commit that referenced this issue Nov 8, 2016
louisemccann added a commit that referenced this issue Nov 18, 2016
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
Projects
None yet
Development

No branches or pull requests

4 participants