Ticket #11493 (closed: fixed)

Opened 6 years ago

Last modified 5 years ago

LoadRaw with separate monitors produces incorrect period log numbers

Reported by: Martyn Gigg Owned by: Martyn Gigg
Priority: major Milestone: Release 3.4
Component: Framework Keywords:
Cc: Blocked By:
Blocking: Tester: Dan Nixon

Description

  • Load OFFSPEC00033772.raw using LoadRaw and specify the LoadMonitors='Separate'
  • Right click and check the sample logs of one of the monitor workspaces.
  • It will have a log 'period X' where X is the period number. They are currently off by one.

The log on the main data workspace is okay.

Change History

comment:1 Changed 6 years ago by Martyn Gigg

  • Status changed from new to inprogress

Fix period numbering in monitor workspace logs for LoadRaw3

Refs #11493

Changeset: a4c654dbde03a4aeed9b76ca4434a46051429423

comment:2 Changed 6 years ago by Martyn Gigg

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

This is being verified as ​pull request #538.

comment:3 Changed 6 years ago by Dan Nixon

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

comment:4 Changed 6 years ago by Dan Nixon

  • Status changed from verifying to closed

Merge pull request #538 from mantidproject/11493_fix_period_numbers_loadraw_separate_monitors

Fix period numbering in monitor workspace logs for LoadRaw3

Full changeset: ​f9b16c5cb893e4d701f9fe0680c552b7d08376e0

comment:5 Changed 6 years ago by Dan Nixon

Strangely enough the log on the last monitor period was correct for me, the numbering was 2, 3, 4, 4.

comment:6 Changed 5 years ago by Nick Draper

Somehow these slipped through without a resolution. Set to Fixed.

comment:7 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​12331

Note: See TracTickets for help on using tickets.