LoadEventNexus: swallow event_index warning for banks with no events

[Janik Zikovsky]

if event_index is 1-length, just ignore that it is not matching proton_charge. That means the bank is empty

[Janik Zikovsky]

Refs #4050 remove a warning. This fixes it.

Changeset: 791624b24b5e828cbddd34ad633a5d1e6c36da7b

[Janik Zikovsky]

Note to testers:

From: mantid-help-bounces@… mantid-help-bounces@… On Behalf Of Moreira Dos Santos, Antonio F. Sent: Thursday, November 03, 2011 9:45 AM To: Yao, Marie Xingxing; Lynch, Vickie E.; mantid-help@… Subject: [Mantid-help] loading warring message

Hello,

Often, when I load runs into Mantid, I get the following messages, is this something I should worry about?

See, for instance, loading run 7671 from SNAP using LoadEventNexus

Bank bank9_events has a mismatch between the number of event_index entries and the number of pulse times. Bank bank3_events has a mismatch between the number of event_index entries and the number of pulse times. Bank bank1_events has a mismatch between the number of event_index entries and the number of pulse times. Bank bank11_events has a mismatch between the number of event_index entries and the number of pulse times. Bank bank10_events has a mismatch between the number of event_index entries and the number of pulse times. Bank bank16_events has a mismatch between the number of event_index entries and the number of pulse times. Bank bank18_events has a mismatch between the number of event_index entries and the number of pulse times. Bank bank17_events has a mismatch between the number of event_index entries and the number of pulse times.

[Janik Zikovsky]

Refs #4050 remove a warning. This fixes it.

Changeset: 791624b24b5e828cbddd34ad633a5d1e6c36da7b

[Vickie Lynch]

No warnings when I loaded SNAP_7671

[Stuart Campbell]

This ticket has been transferred to github issue ​4897