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

How Errors are Calculated #10532

Closed
1 task done
OwenArnold opened this issue Jun 19, 2014 · 1 comment
Closed
1 task done

How Errors are Calculated #10532

OwenArnold opened this issue Jun 19, 2014 · 1 comment
Assignees
Labels
Documentation Issues and pull requests related to documentation High Priority An issue or pull request that if not addressed is severe enough to postponse a release.
Milestone

Comments

@OwenArnold
Copy link
Contributor

This ticket is blocked by :

An important question raised more than once at the ILL was about how errors are calculated and carried through, the plus algorithm documentation http://www.mantidproject.org/Plus has a broken link for this and in the new documentation, this concept is completely missing.

This is an important point for people to trust Mantid, to know what it does about the errors.


Keywords: ILL

@OwenArnold OwenArnold added High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Documentation Issues and pull requests related to documentation labels Jun 3, 2015
@OwenArnold
Copy link
Contributor Author

This issue was originally trac ticket 9690

@OwenArnold OwenArnold added this to the Release 3.3 milestone Jun 3, 2015
abuts added a commit that referenced this issue Nov 26, 2015
walking through DirectEnergyConversion and using PropertyManager everywhere

Replaced all in diagnostics but need to deal with wb integrals next.
abuts added a commit that referenced this issue Nov 26, 2015
abuts added a commit that referenced this issue Nov 26, 2015
abuts added a commit that referenced this issue Nov 26, 2015
system tests are still failing
abuts added a commit that referenced this issue Nov 26, 2015
as it become too big to be convenient.
abuts added a commit that referenced this issue Nov 26, 2015
abuts added a commit that referenced this issue Nov 26, 2015
abuts added a commit that referenced this issue Nov 26, 2015
and modified ReductionWrapper according to Marcus suggestions (minor)
abuts added a commit that referenced this issue Nov 26, 2015
and fixing long standing error in dgreduce (thanks good nobody used internal reduction procedure)
abuts added a commit that referenced this issue Nov 26, 2015
abuts added a commit that referenced this issue Nov 26, 2015
Modified property managed to allow it MonovanIntegrationRange accepting absolute energy range (used by MAPS system test)
abuts added a commit that referenced this issue Nov 26, 2015
abuts added a commit that referenced this issue Nov 26, 2015
martyngigg added a commit that referenced this issue Nov 26, 2015
The parameter count has changed.
Refs #10532
abuts added a commit that referenced this issue Nov 26, 2015
Merge remote-tracking branch 'remotes/origin/feature/10532_separatePropertyManager' into feature/10681_RedWrapper

Conflicts:
	Code/Mantid/scripts/Inelastic/DirectReductionProperties.py
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation Issues and pull requests related to documentation High Priority An issue or pull request that if not addressed is severe enough to postponse a release.
Projects
None yet
Development

No branches or pull requests

2 participants