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

Muon: run_number should appear as log value #9008

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

Muon: run_number should appear as log value #9008

mantid-builder opened this issue Oct 21, 2013 · 1 comment
Labels
Low Priority Things that you don't ever want to be done. Muon Issues and pull requests related to muons
Milestone
Release 3.1

Comments

@mantid-builder
Copy link
Collaborator

Original Reporter: Arturs Bekasovs

This ticket is blocks : TRAC7367

Stephen Cottrell noted that in Muon Analysis results table run_number is added automatically, without user being aware of it prior to the table creation. This is not transparent.

Additionally, user is unable to create a table with run_number and fitting results only, because he should select at least one log value for interface to allow that.

Making it so that run_number appears as another log value in the upper table would solve all these difficulties.
@mantid-builder
Copy link
Collaborator Author

This issue was originally trac ticket 8163

@mantid-builder mantid-builder added Low Priority Things that you don't ever want to be done. Muon Issues and pull requests related to muons labels Jun 3, 2015
@mantid-builder mantid-builder added this to the Release 3.1 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
Low Priority Things that you don't ever want to be done. Muon Issues and pull requests related to muons
Projects
None yet
Milestone
Release 3.1
Development

No branches or pull requests
1 participant
@mantid-builder