For your convenience, we provide sets of common bitmasks for almost all of the PCA event modes**. You should check carefully that you are using the correct bitmask for your data configuration; often, the tools will be perfectly happy to operate with a bitmask which is not what you intended. If you want a different combination of detectors or anodes, you will have to make your own using sefilter following its recipe.

If the bitmask you need has an asterisk next to it, then the data will have to be filtered with fselect before extraction as explained in the selection recipe.

Find your data mode (as shown in the AppId window of XDF or in the keyword DATAMODE of the fits event list) in the first column; x indicates the binning (A,B,C,M, or N), ll is the lower channel boundary, and rr the readout time. The next three columns tell you what you can select from that configuration, and the last column has the link to the correct table for chosing a bitmask:

Also, many of these bitmasks will not look like what you would get using sefilter yourself. We have removed the default bitmask which filters out the M[1]{1} token; since GoodXenon data have no time stamps, filtering on this token is unnecessary and will take longer in fselect. Where possible, we have also simplified the expressions produced by sefilter in order to make the selection process as efficient as possible. (Sefilter's algorithm is designed to be correct for every possible case, and so it may not be the most efficient.)

The event mode E_500us_64x_ll_rr is not currently included due to an oddity in the original processing of this event mode. If you have AO1 data of this type, wait for the reprocessed data and do not attempt to use this mode from the originally processed version.