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.

Sign up for GitHub

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

Jump to bottom

Remove old Fury code from IndirectDataAnalysis.py and correct system test #11589

Closed
DanNixon opened this issue Dec 10, 2014 · 1 comment
Closed

Remove old Fury code from IndirectDataAnalysis.py and correct system test #11589

DanNixon opened this issue Dec 10, 2014 · 1 comment
Assignees
@DanNixon
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Indirect/Inelastic Issues and pull requests related to indirect or inelastic
Milestone
Release 3.3

Comments

@DanNixon
Copy link
Member

Left in after this routine was moved to an algorithm.

Also modify the system test to check the new algorithm (Fury) rather than the old code.
@DanNixon
Copy link
Member Author

DanNixon commented Jun 3, 2015

This issue was originally trac ticket 10747

@DanNixon DanNixon added High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Indirect/Inelastic Issues and pull requests related to indirect or inelastic labels Jun 3, 2015
@DanNixon DanNixon self-assigned this Jun 3, 2015
@DanNixon DanNixon added this to the Release 3.3 milestone Jun 3, 2015
@DanNixon DanNixon 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
Assignees

@DanNixon DanNixon

Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Indirect/Inelastic Issues and pull requests related to indirect or inelastic
Projects
None yet
Milestone
Release 3.3
Development

No branches or pull requests
1 participant
@DanNixon