Ticket #4734 (closed: fixed)

Opened 9 years ago

Last modified 5 years ago

Handle 'weight' for each MDEvent

Reported by: Janik Zikovsky Owned by: Andrei Savici
Priority: major Milestone: Release 3.4
Component: Framework Keywords:
Cc: saviciat@… Blocked By:
Blocking: Tester: Harry Jeffery

Description (last modified by Andrei Savici) (diff)

The properly normalized signal for a box or a bin in MDHisto is:

Sum( event signal * event 'weight' ) / sum ( weights )

Where the weight of each 'event' is proportional to its solid angle * its width in energy transfer. For MDLeanEvent, weight would be 1.0 always. For MDEvent, it should either be cached or calculated on the fly (from the run number and detector ID).

  • Each MDEvent carries run index and detector id which is enough to find the weight, but do we want to cache it ?
  • Also , BinMD and the other integration methods would need to calculate the sum of the weight as they sum the signal.
  • See also #4733 where BinMD needs to track it

Change History

comment:1 Changed 9 years ago by Janik Zikovsky

  • Description modified (diff)

comment:2 Changed 9 years ago by Janik Zikovsky

  • Description modified (diff)

comment:3 Changed 9 years ago by Janik Zikovsky

  • Status changed from new to accepted

comment:4 Changed 9 years ago by Janik Zikovsky

Refs #4734 carry a TotalWeight field in MDBoxes

Changeset: 8aed22bf9fb2e18ee3089de1d7bb8d00d7a0e9f4

comment:5 Changed 8 years ago by Janik Zikovsky

  • Milestone changed from Release 2.1 to Release 2.2

comment:6 Changed 8 years ago by Janik Zikovsky

  • Status changed from accepted to assigned
  • Owner changed from Janik Zikovsky to Andrei Savici

comment:7 Changed 8 years ago by Nick Draper

  • Milestone changed from Release 2.2 to Release 2.3

Moved at the end of release 2.2

comment:8 Changed 8 years ago by Nick Draper

  • Milestone changed from Release 2.3 to Release 2.4

Moved to milestone 2.4

comment:9 Changed 8 years ago by Nick Draper

  • Milestone changed from Release 2.4 to Release 2.5

Moved at the code freeze for release 2.4

comment:10 Changed 7 years ago by Andrei Savici

  • Milestone changed from Release 2.5 to Release 2.7

comment:11 Changed 7 years ago by Nick Draper

  • Status changed from assigned to new

comment:12 Changed 7 years ago by Nick Draper

  • Milestone changed from Release 2.7 to Backlog

comment:13 Changed 7 years ago by Nick Draper

  • Component changed from Mantid to Framework

comment:14 Changed 7 years ago by Nick Draper

  • Status changed from new to assigned

Bulk move to assigned at the introduction of the triage step

comment:15 Changed 6 years ago by Andrei Savici

  • Status changed from assigned to verify
  • Resolution set to duplicate
  • Description modified (diff)

This is going to be part of #9105

comment:16 Changed 6 years ago by Harry Jeffery

  • Status changed from verify to verifying
  • Tester set to Harry Jeffery

comment:17 Changed 6 years ago by Harry Jeffery

  • Status changed from verifying to closed

comment:18 Changed 6 years ago by Nick Draper

  • Milestone changed from Backlog to Release 3.4

moved to r 3.4 as tickets are closed

comment:19 Changed 5 years ago by Nick Draper

  • Resolution changed from duplicate to fixed

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

comment:20 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue 5581

Note: See TracTickets for help on using tickets.