LoadEventNexus with filtering does not work on (some?) event Nexus runs

[Alex Buts]

Lets try to load event nexus data from MER18972 run (see in archive or I can put it on ftp on request.)

If I issue

w1=LoadEventNexus('MER18972') 

it works and from the data log I see it containing ~2*10⁶ good frames collected during 40000 sec, Workspace without monitors contains ~67M events.

If I try

w1=LoadEventNexus('MER18972.nxs',FilterByTimeStart=0,FilterByTimeStop=40000) 

or any other time interval, the resulting workspace contains no events.

Looks like a bug.

Freddy said that nothing is wrong with the data inside of the workspace except the frame current is mainly 0 due to problems with DAE.

If this is the reason for the problem, LoadEventNexus should issue clear warning about it. A measures have to be taken to be able recovering the data.

[Federico M Pouzols]

I experience the same issue (tried with the same file):

• with the first command (no time filter) the events load fine, and in the logs I can see:

Read 67122520 events. Shortest TOF: 0 microsec; longest TOF: 20000 microsec.

• with the second command line (with time filter) the resulting workspace has no events, and I get:

Read 0 events. Shortest TOF: 4.29497e+08 microsec; longest TOF: 0 microsec

For both commands I get these warnings:

Xseblock entry 'ILM_N2' gave an error when loading a time series:'Invalid value entry for time series'. Skipping entry

Found entries in the proton_charge sample log with invalid pulse time!

But only for the second command I get these repeated messages:

TimeSeriesProperty is not sorted.  Sorting is operated on it. 
TimeSeriesProperty is not sorted.  Sorting is operated on it. 
TimeSeriesProperty is not sorted.  Sorting is operated on it. 
TimeSeriesProperty is not sorted.  Sorting is operated on it. 
TimeSeriesProperty is not sorted.  Sorting is operated on it. 

[Stuart Campbell]

This ticket has been transferred to github issue ​10287