Run dependent parameters:
First up are functions that will return e.g. the region-of-interest boundaries for each run. During the experiment, this should be kept up-to-date so if the setup changes, the littleData file will get an entry with new boundaries for a just finished range of runs. This way, the littleDataRun script will always use the correct region of interest for each run.
Azimuthal Integration
Another option is to reduce the data by azimuthally averaging the signal. Here, we need to know the center for the integration as well as the detector distance and beam energy. The latter two are mostly important for the q-values of the bins that will also be stored in the littleDatasmallData. As conditions will change during an experiment, it is convenient to have a function that return the correct integration setup for each (range of) run(s). In addition to a 1-d result as a q-vector, you can also define a number of phi-slices that should be used for integration, resulting in a 2-d average in q-phi space.
The averaging will automatically apply a corrections for the x-ray polarization and geometric acceptance. What is currently not corrected for are signal differences due to different path length of the photons when crossing the detector . Also, the calculations assume that the detector is mounted perpendicular to the beam direction.
run dependent integration parameters
def getAzIntParams(run):
ret_dict |
def getAzIntParams(run):
""" Parameters for azimuthal integration
See azimuthalBinning.py for more info
"""
if isinstance(run,str):
run=int(run)
ret_dict = {}
if run>0:
az_dict = {'eBeam': |
8015
retcspad_8769794601676089294865383526655729
retcspad_dis_to_sam 110.
return ret_dict
UserData: azimuthal integration
Code Block |
---|
|
haveCspad = checkDet(ds.env(), 'cspad')
if haveCspad:
cspad = DetObject('cspad' ,ds.env(), int(run), name='cspad')
for iROI,ROI in enumerate(ROIs):
cspad.addROI('ROI_%d'%iROI, ROI)
cspad.azav_eBeam=azIntParams['eBeam']
if azIntParams.has_key('cspad_center'):
cspad.azav_center=azIntParams['cspad_center']
cspad.azav_dis_to_sam=azIntParams['cspad_dis_to_sam']
try:
cspad.addAzAv(phiBins=7)
except:
pass
dets.append(cspad)
|
[-549.943775, 261.418876] # um
az_dict['dis_to_sam'] = 80. # mm
az_dict['tx'] = 0 # deg
az_dict['ty'] = 0 # deg
az_dict['phiBins'] = 11 # number of phi bins
ret_dict['epix10k2M'] = az_dict
return ret_dict
|
Code Block |
---|
|
SDAna In: anaps.FitCircle() |
This will by draw the image and let you either select points by clicking or define a threshold above which points are selected and fitted to a single circle. The azimuthal integration code needs a center point which the circle fitting will return.
Below is an example of the entire prompt:
- First the image you created first will pop up. You can then either select points by hand or use a threshold (highest x% of pixels).
- The chosen pixel location will be shown and you are adjust your threshold until you are satisfied.
- In the last step, the fit is performed and overlaid on the image. The beam center and radius of the circle are printed. You will have to know about your sample to use the radius to extract the detector - sample distance. The latter will not affect she shape of the azimuthally integrated data (a wrong center will!), but the q-bin values will be wrong.
Code Block |
---|
|
SDana In [2]: anaps.FitCircle()
plot AvImg_cspad using the 5/99.5 percentiles as plot min/max: (0.199616, 263.383)
Select Circle Points by Mouse?:
n
Select Circle Points with threshold (y/n):
y
min percentile % of selected points:
99.2
thresP 248.786973755
Happy with this threshold (y/n):
y
x,y: 99652.2541599 87977.9162216 R 18603.6250138
|
FitCircle has an optional argument (useMask=False/True) that defaults to False. If set to True, the mask stored in the calib directory will be applied.
Run the Azimuthal integration
This function will set up the azimuthal integration. It will also correct for the LCLS Xray polarization and the geometric acceptance. The center and distance to sample are needed. Then this code can be applied to any average image by:
Code Block |
---|
|
SDana In [2]: anaps.AzInt |
Use of SmallDataAna_psana
For the use of the interactive features of SmallDataAna_psana, we recommend to start it in an ipython session as interactive grabbing of user input is currently not implemented via the notebook.
Creating an average image
In order to decide on the proper ROI, fit a team center or make a mask, the first step is always to create an image that you would like to use as base. This is achieved using the following function
SDAna In: anaps.AvImage()
This will by default create an average image of 100 events of an area detector.
The full command with all its options and a examples is here:
AvImage
Code Block |
---|
|
LDana In [1]: anaps.AvImage?
Type: instancemethod
String form: <bound method |
LittleDataAnaAvImage<LittleDataAnaLittleDataAnaSmallDataAna_psana object at |
0x7fd37fe03590>>0x7f7731f13f10>>
File: /reg/ |
dpsdmxpptut15resresults/littleData/xppmodules/scripts/ |
LittleDataAnaSmallDataAna_psana.py
Definition: anaps. |
AvImage'', numEvts=100, thresADU=0.0, thresRms=0.0,useLdat=False, nSkip=0, minIpm=-1.0, common_mode=True)
Docstring: <no docstring>
LDana In [2]: anaps.AvImage()
detectors in event:
cs140_rob
opal_1
Select detector to select ROI of?:
cs140_rob
try get detector info to make average image for: cs140_rob
try to make psana Detector with: cs140_rob
requested 100 used 100
LDana In [3]: anaps.plotAvImage()
plot AvImg_cs140_rob using the 5/99.5 percentiles as plot min/max: (1603.9, 1950.21)
If you would like to take a quick look at your average image before proceeding, use as seen above:
Code Block |
---|
SDAna In: anaps.plotAvImage()
|
It returns the data arrays. The q-bins are stored as well in anaps.<detname>.azav_q
which will result in a figure like this popping up: