Ticket #8377 (closed: fixed)

Opened 7 years ago

Last modified 5 years ago

Include run start/end in MantidPlot workspace details

Reported by: Martyn Gigg Owned by: Federico M Pouzols
Priority: major Milestone: Release 3.3
Component: GUI Keywords:
Cc: Blocked By:
Blocking: Tester: Dan Nixon

Description

Requested by a user after the release presentation. They saw the date next to the instrument and thought that it related to the run itself.

If available we should include the run start/end times in the details about the workspace in MantidPlot

Change History

comment:1 Changed 7 years ago by Nick Draper

  • Status changed from new to assigned

bulk move to assigned at the into of the triage step

comment:2 Changed 6 years ago by Federico M Pouzols

  • Owner set to Federico M Pouzols
  • Milestone changed from Backlog to Release 3.3

comment:3 Changed 6 years ago by Federico Montesino Pouzols

  • Status changed from assigned to inprogress

added run start/end info to ws details string, re #8377

Changeset: 62b14b9efa708b9ae171b95c139e51fda53cc915

comment:4 Changed 6 years ago by Federico Montesino Pouzols

update test on expected workspace info string, re #8377

Changeset: 3bff77bc09f11951289b5762044cf146e33d1071

comment:5 Changed 6 years ago by Federico M Pouzols

  • Status changed from inprogress to verify
  • Resolution set to fixed

Two new lines have been added in the workspace details string: 

 "Run start: ..."
 "Run end: ..."

They are shown immediately below the "Instrument:..." line. They could also go in a single line, but to me it looks easier to read like this. It prints 'not available' if the info is not available. I think this is more informative than not showing anything. On the other hand the amount of information rows displayed for every workspace is growing.

To test:

Load your favorite workspaces and check that the new information is shown. Tests should pass, including APITest_MatrixWorkspaceTest which has been modified. If you find a workspace without run start/end dates you should see "not available", the unit test is checking this.

comment:6 Changed 6 years ago by Dan Nixon

  • Status changed from verify to verifying
  • Tester set to Dan Nixon

comment:7 Changed 6 years ago by Dan Nixon

For reference I also tested this with some Sassena data which does not have a run start and end time.

comment:8 Changed 6 years ago by Dan Nixon

  • Status changed from verifying to closed

Merge remote-tracking branch 'origin/feature/8377_include_run_start_end_in_workspace_details'

Full changeset: ​53a4393b84646bcddc112bf11b01083c683eaccd

comment:9 Changed 6 years ago by Dan Nixon

In the long term it would be much nicer to be able to configure what information is shown here.

comment:10 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​9222

Note: See TracTickets for help on using tickets.