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

[ICAT] run range issues #9162

Closed
mantid-builder opened this issue Oct 31, 2013 · 1 comment
Closed

[ICAT] run range issues #9162

mantid-builder opened this issue Oct 31, 2013 · 1 comment
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release.
Milestone
Release 3.0

Comments

@mantid-builder
Copy link
Collaborator

Original Reporter: Jay Rainey

If you only fill in one side of the run-range an error is thrown: bad lexical cast: source type value could not be interpreted as target. Moreover, the size of the run range is 5-5 (e.g. 00000-00000), which is too small.

The following needs fixed:

  1. No error if user inputs only one side (assume from start (000000) to INPUT, or INPUT to end (perhaps +10k?)

  2. Remove limit on run-range size.

    Keywords: ICAT
@mantid-builder
Copy link
Collaborator Author

This issue was originally trac ticket 8317

@mantid-builder mantid-builder added High Priority An issue or pull request that if not addressed is severe enough to postponse a release. GUI labels Jun 3, 2015
@mantid-builder mantid-builder added this to the Release 3.0 milestone Jun 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release.
Projects
None yet
Milestone
Release 3.0
Development

No branches or pull requests
1 participant
@mantid-builder