Ticket #3235 (closed: fixed)

Opened 9 years ago

Last modified 5 years ago

EventNexusReader trouble with min and max signal values

Reported by: Michael Reuter Owned by: Owen Arnold
Priority: major Milestone: Iteration 29
Component: VATES Keywords:
Cc: Blocked By:
Blocking: Tester: Janik Zikovsky

Description

Once the clipping is off on the EventNexusReader, it looks like the min and max signal values are still being applied to the data. It looks like another accidental clipping is occurring.

Change History

comment:1 Changed 9 years ago by Owen Arnold

  • Status changed from new to accepted

Looking into it.

comment:2 Changed 9 years ago by Owen Arnold

The ImplicitFunction (defined by the plane when the Apply Clip flag is on) used to clip the dataset in a non-axis aligned fashion. When Apply Clip is off, the ImplicitFunction is definitely not called, so behaving as expected.

The max and min signal thresholds are a different matter from the ImplicitFunctions. These are applied after rebinning and are used to ditch visualisation cells that fall outside of the specified threshold. The 'Apply Clip' flag provides no control over this in-visualisation aspect.

comment:3 Changed 9 years ago by Owen Arnold

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

comment:4 Changed 9 years ago by Janik Zikovsky

  • Status changed from verify to verifying
  • Tester set to Janik Zikovsky

comment:5 Changed 9 years ago by Janik Zikovsky

  • Status changed from verifying to closed

They look (in the GUI) to be part of the "Apply Clipping" group, hence the confusion. A separator line or something like that would help reduce that confusion.

comment:6 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​4082

Note: See TracTickets for help on using tickets.