Event Workspace

What is it for?

Event Workspaces are specialised for time-of-flight neutron scattering. Event Workspaces are designed for sparse data storage of neutron events. Individual detector observations, including information about when that observation was made are stored as discrete items inside the workspace. The ability to keep more detailed information gives a number of advantages over converting directly to a compressed form, such as allowing more powerful filtering operations to be used.

Summary for Users

The Event Workspace is a type of Matrix Workspace, where the information about each individual neutron detection event is maintained. For you as a user, this means that:

  • There are many options for filtering an Event Workspace, such as FilterByLogValue

  • You can histogram (via rebin) an Event Workspace over and over and no information is ever lost (as long as you choose the PreserveEvents option).

  • You can convert an Event Workspace to a histogram Workspace 2D by using the Rebin algorithm.

  • You cannot modify the histogram Y values (for example, with the Divide algorithm) and keep the event data. If you use an algorithm that modifies the Y values, the output workspace will be a Workspace 2D using the current binning parameters.

  • Some algorithms are Event Workspace-aware, meaning that the output of it can be another Event Workspace. For example, the Plus algorithm will append the event lists if given two input Event Workspaces.


If you set the same name on the output as the input of your algorithm, then you will overwrite the Event Workspace and lose that event-based information.

Working with Event Workspaces in Python

The python options for an Event Workspace are limited - it is designed to be able to be read (but not written to) like a MatrixWorkspace. You can look at the Event Workspace API reference for a full list of properties and operations, but here are some of the key ones.

Accessing Workspaces

The methods for getting a variable to an Event Workspace is the same as shown in the Workspace help page.

If you want to check if a variable points to something that is an Event Workspace you can use this:

from mantid.simpleapi import *
from mantid.api import IEventWorkspace

eventWS = CreateSampleWorkspace(WorkspaceType="Event")

if isinstance(eventWS, IEventWorkspace):
    print(eventWS.name() + " is an " + eventWS.id())


eventWS is an EventWorkspace

Event Workspace Properties

In addition to the Properties of the MatrixWorkspace, the Event Workspace also has the following:

from mantid.simpleapi import *
eventWS = CreateSampleWorkspace(WorkspaceType="Event")

print("Number of events: {}".format(eventWS.getNumberEvents()))
print("Maximum time of flight: {}".format(eventWS.getTofMax()))

Event lists

Event Workspaces store their data in event lists, one per spectrum. You can access them using:

from mantid.simpleapi import *
eventWS = CreateSampleWorkspace(WorkspaceType="Event")

# get the number of event lists
evListCount = eventWS.getNumberHistograms()

# Get the first event list
evList = eventWS.getSpectrum(0)

# Get some basic information
print("Number of events in event List 0: {}".format(evList.getNumberEvents()))
print("Minimum time of flight in event List 0: {}".format(evList.getTofMax()))
print("Maximum time of flight in event List 0: {}".format(evList.getTofMax()))
print("Memory used: {}".format(evList.getMemorySize()))
print("Type of Events: {}".format(evList.getEventType()))

# Get a vector of the pulse times of the events
pulseTimes = evList.getPulseTimes()

# Get a vector of the TOFs of the events
tofs = evList.getTofs()

# Get a vector of the weights of the events
weights = evList.getWeights()

# Get a vector of the errors squared of the weights of the events
weightErrors = evList.getWeightErrors()

# Integrate the events between  a range of X values
print("Events between 1000 and 5000: {}".format(evList.integrate(1000,5000,False)))

#Check if the list is sorted in TOF
print("Is sorted by TOF: {}".format(evList.isSortedByTof()))
Changing EventLists

Please note these should only be done as part of a Python Algorithm, otherwise these actions will not be recorded in the workspace history.

from mantid.simpleapi import *
import math
eventWS = CreateSampleWorkspace(WorkspaceType="Event")
# Get the first event list
evList = eventWS.getSpectrum(0)

# Add an offset to the pulsetime (wall-clock time) of each event in the list.
print("First pulse time before addPulsetime: {}".format(evList.getPulseTimes()[0]))
seconds = 200.0
print("First pulse time after addPulsetime: {}".format(evList.getPulseTimes()[0]))

# Add an offset to the TOF of each event in the list.
print("First tof before addTof: {}".format(evList.getTofs()[0]))
microseconds = 2.7
print("First tof after addTof: {}".format(evList.getTofs()[0]))

# Convert the tof units by scaling by a multiplier.
print("First tof before scaleTof: {}".format(evList.getTofs()[0]))
factor = 1.5
print("First tof after scaleTof: {}".format(evList.getTofs()[0]))

# Multiply the weights in this event list by a scalar with an error.
print("First event weight before multiply: {0} +/- {1}".format(evList.getWeights()[0], math.sqrt(evList.getWeightErrors()[0])))
factor = 10.0
error = 5.0
print("First event weight after multiply: {0} +/- {1}".format(evList.getWeights()[0], math.sqrt(evList.getWeightErrors()[0])))

# Divide the weights in this event list by a scalar with an error.
print("First event weight before divide: {0} +/- {1}".format(evList.getWeights()[0], math.sqrt(evList.getWeightErrors()[0])))
factor = 1.5
error = 0.0
print("First event weight after divide: {0} +/- {1}".format(evList.getWeights()[0], math.sqrt(evList.getWeightErrors()[0])))

# Mask out events that have a tof between tofMin and tofMax (inclusively)
print("Number of events before masking: {}".format(evList.getNumberEvents()))
print("Number of events after masking: {}".format(evList.getNumberEvents()))

For Developers/Writing Algorithms

See the Event Workspace section in development documentation

Category: Concepts