You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
This issue was originally TRAC 9444
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
it works and from the data log I see it containing ~2*10^6^ good frames collected during 40000 sec, Workspace without monitors contains ~67M events.
If I try
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.
The text was updated successfully, but these errors were encountered: