Ticket #7313 (closed: worksforme)

Opened 7 years ago

Last modified 5 years ago

MUON: PlotAsymmetryByLogValue inconsistent spectrum numbering

Reported by: Anders Markvardsen Owned by: Arturs Bekasovs
Priority: minor Milestone: Release 3.0
Component: MantidPlot Keywords:
Cc: james.lord@… Blocked By:
Blocking: Tester: Jay Rainey

Description (last modified by Anders Markvardsen) (diff)

James writes:

We were trying to track down a faulty detector that was upsetting our data using PlotAsymmetryByLogValue. If I enter a range of histograms to use as Forward or Backward (such as "1-16" or "1,3,5,7" it uses Spectra IDs (1-64). But if I enter a single number it instead interprets that as a Workspace Index in the range 0-63.

To test this you could look at HiFi runs 53672 to ~53692 where detector 23 (on the Spectrum numbering scale 1-64) was misbehaving (low counts) in 53672, 53675 and 53678. It's clearly number 23 as seen from plotting one Bin out of the raw data, or 2D Colour Plot.

Forward="1-32" Backward="33-64" or blank (default) -> small spikes seen.

Odd numbers only (long list typed in) -> larger spike.

Even numbers only -> clean data.

Forward="1-22,24-32" and Backward="33-64" -> clean data.

Forward="23" Backward="24" -> nothing wrong with the data...?

Forward="22" Backward="23" -> negative spikes, meaning the low counts are in the Forward bank

Forward="21" Backward="22" -> positive spikes, meaning the low counts are in the Backward bank.

(This is with the very latest Mantid 2.5.3, Windows 7)

Change History

comment:1 Changed 7 years ago by Nick Draper

  • Milestone changed from Release 2.6 to Backlog

Moved to backlog at the code freeze for R2.6

comment:2 Changed 7 years ago by Anders Markvardsen

  • Owner changed from Anders Markvardsen to Arturs Bekasovs
  • Priority changed from major to minor
  • Description modified (diff)

comment:3 Changed 7 years ago by Arturs Bekasovs

  • Status changed from new to verify
  • Resolution set to worksforme

comment:4 Changed 7 years ago by Arturs Bekasovs

All works as described in the ticket up to this line:

Forward="23" Backward="24" -> nothing wrong with the data...?

This is not true any more - when using these spectra I get spikes for 53672, 53675 and 53678. This is true if I swap forward and backward as well.

I get positive pikes for this one:

Forward="22" Backward="23" -> negative spikes, meaning the low counts are in the Forward bank

I don't get characteristic spikes for this one:

Forward="21" Backward="22" -> positive spikes, meaning the low counts are in the Backward bank.

This leads to a conclusion that the problem described in the ticket has been solved somehow since the ticket was opened.

comment:5 Changed 7 years ago by Arturs Bekasovs

  • Milestone changed from Backlog to Release 3.0

comment:6 Changed 7 years ago by Martyn Gigg

  • Status changed from verify to verifying
  • Tester set to Martyn Gigg

comment:7 Changed 7 years ago by Martyn Gigg

  • Status changed from verifying to verify
  • Tester Martyn Gigg deleted

comment:8 Changed 7 years ago by Jay Rainey

  • Status changed from verify to verifying
  • Tester set to Jay Rainey

comment:9 Changed 7 years ago by Jay Rainey

  • Status changed from verifying to closed

It appears this ticket has been solved in another ticket, as Arturs describes above.

comment:10 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue 8159

Note: See TracTickets for help on using tickets.