Gd-Lysozyme

In this tutorial, we assume that we are handed an SFX dataset containing thermolysin diffraction, but are not told anything else. We will have to go through all the data runs, figure out which one is to be used for dark subtraction, and account for untrusted pixels and detector metrology. At this point, we will be prepared to integrate and merge the data. Finally, we will perform simple molecular replacement and ask whether there is any Zn signal in the anomalous difference Fourier.

Discovery of data collection parameters

Log in to pslogin.slac.stanford.edu, and then to psana. Carry through flags so that X-windows will work

ssh -YAC $USER@pslogin.slac.stanford.edu
ssh -YAC psana

Go in to the working directory and source the package manager:

cd ~/myrelease
sit_setup

Create a subdirectory for the 2014 tutorial files if not already done:

mkdir -p cxi84914

List out the Gd-Lysozyme XTC files (this could take time since there are many images):

ls /reg/d/psdm/cxi/cxi84914/xtc/e239
ls /reg/d/psdm/cxi/cxi84914/xtc/e240

Notice that there are numerous runs in the directory. Now we will create composite averages for each run. Grab this configuration file: mkdark.cfg and put it in your cxi84914 directory. For one run only from each experiment directory:

cxi.lsf -c ~/myrelease/cxi84914/mkdark.cfg \
-o /reg/d/psdm/cxi/cxi84914/scratch/$USER/initial_dark/e239/ \
-i /reg/d/psdm/cxi/cxi84914/xtc/e239 -q psanacsq -s -p 8 -x 239 -r 16 -t 0

cxi.lsf -c ~/myrelease/cxi84914/mkdark.cfg \
-o /reg/d/psdm/cxi/cxi84914/scratch/$USER/initial_dark/e240/ \
-i /reg/d/psdm/cxi/cxi84914/xtc/e240 -q psanacsq -s -p 8 -x 240 -r 16 -t 0

Take note:

• -c configuration file
• -o output directory (will be created)
• -i input files (directory containing the XTC streams)
• -q which batch queue to use
• -s funnel all streams for the run into one node (takes longer, but necessary for averaging)
• -p number of cores to use on the node
• -x which experiment number
• -r which run number
• -t which processing trial (auto increments from 0 if not given)

For all the runs in the Gd-Lysozyme data set 239:

kinit
aklog
for m in 27 28 29 30 31; \
 do echo $m; cxi.lsf -c ~/myrelease/cxi84914/mkdark.cfg \
 -o /reg/d/psdm/cxi/cxi84914/scratch/$USER/initial_dark/e239/ \
 -i /reg/d/psdm/cxi/cxi84914/xtc/e239 -q psanacsq -s -p 8 -x 239 -r ${m} -t 0; done

For all the runs in the Gd-Lysozyme data set 240:

kinit
aklog
for m in 1 2 3 4 5 6 7 8 9 10 12 13 14 16 17 18 19 21 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40; \
 do echo $m; cxi.lsf -c ~/myrelease/cxi84914/mkdark.cfg \
 -o /reg/d/psdm/cxi/cxi84914/scratch/$USER/initial_dark/e240/ \
 -i /reg/d/psdm/cxi/cxi84914/xtc/e240 -q psanacsq -s -p 8 -x 240 -r ${m} -t 0; done

bjobs lists all your batch jobs; use this form for more information including other-user load:

bjobs -w -u all -q psanacsq
bkill [number] # stops unwanted job

Some runs take up to 2 hrs wall time to average. Find the averages, view the max-composites, and list out header information for each experiment separately and create a table of the results:

ls /reg/d/psdm/cxi/cxi84914/scratch/$USER/initial_dark/e239/r*/000/out/*.pickle
cctbx.image_viewer `find /reg/d/psdm/cxi/cxi84914/scratch/$USER/initial_dark/e239/r*/000 -name "max*.pickle"`
for m in `find /reg/d/psdm/cxi/cxi84914/scratch/$USER/initial_dark/e239/r*/000 -name "max*.pickle"`; 
 do echo $m; cxi.print_pickle $m; echo; done

Let's make a table of the results for experiment 239:

Run	Distance	Wavelength	Diffraction	Comments
27	81.0	1.456964	weak powder
28	81.0	1.456955	strong powder
29	81.0	1.4569557	strong powder
30	81.0	1.4569529	dark
31	81.0	1.456949	strong powder

The next Gd-Lysozyme experiment:

ls /reg/d/psdm/cxi/cxi84914/scratch/$USER/initial_dark/e240/r*/000/out/*.pickle
cctbx.image_viewer `find /reg/d/psdm/cxi/cxi84914/scratch/$USER/initial_dark/e240/r*/000 -name "max*.pickle"`
for m in `find /reg/d/psdm/cxi/cxi84914/scratch/$USER/initial_dark/e240/r*/000 -name "max*.pickle"`; 
 do echo $m; cxi.print_pickle $m; echo; done

Let's make a table of the results for experiment 240:

Run	Distance	Wavelength	Diffraction	Comments
1	156.0	1.145418	dark
2	101.0	1.454165	strong powder
3	81.0	1.454175	strong powder
4	81.0	1.454175	strong powder
5	81.0	1.454175	strong powder
6	81.0	1.454176	strong powder
7	81.0	1.454176	strong powder
8	97.735	1.453730	dark
9	171.0	1.4569401	weak powder
10	81.0	1.456952	strong powder
12	81.0	1.45695	weak powder
13	81.0	1.45815	dark
14	81.0	1.456952	strong powder
16	81.0	1.45697	strong powder
17	81.0	1.457426	weak powder
18	81.0	1.467101	very weak powder
19	81.0	1.456950	strong powder
21	81.0	1.456949	strong powder
24	81.0	1.456950	very weak powder
25	81.0	1.456958	strong powder
26	81.0	1.4569358	strong powder
27	81.0	1.4569524	strong powder
28	81.0	1.456964	very weak powder
29	81.0	1.4570738	strong powder	shadow
30	81.0	1.4569528	strong powder	shadow
31	81.0	1.4569488	dark
32	81.0	1.456953	strong powder
33	81.0	1.4569476	strong powder
34	81.0	1.4569505	strong powder
35	81.0	1.456966	strong powder
36	81.0	1.456948	strong powder
37	81.0	1.4573264	strong powder
38	81.0	1.4569576	strong powder
39	81.0	1.4569520	strong powder
40	81.0	1.4569505	strong powder

Some conclusions:

• Run 30 was the dark run for experiment 239. We'll use the average and standard deviation for further processing. Tutorial students can take result from the instructor's directory:

/reg/d/psdm/cxi/cxi84914/scratch/tmmclark/initial_dark/e239/r0030/000/out/avg-r0030.pickle
/reg/d/psdm/cxi/cxi84914/scratch/tmmclark/initial_dark/e239/r0030/000/out/stddev-r0030.pickle

• Runs 1, 8, 13 and 31 were dark runs for experiment 240. We will discard runs 1 and 8 since the detector distances are unique and would require separate detector calibration. Either run 13 or 31 will work so we'll use the average and standard deviation of run 31 for further processing of experiment 240. Tutorial students can take result from the instructor's directory:

/reg/d/psdm/cxi/cxi84914/scratch/tmmclark/initial_dark/e240/r0031/000/out/avg-r0031.pickle
/reg/d/psdm/cxi/cxi84914/scratch/tmmclark/initial_dark/e240/r0031/000/out/stddev-r0031.pickle

• We are interested in getting the Gd anomalous signal from lysozyme, runs were collected at the far remote for f” at approximately 8500 eV or 1.457 Angstroms. See the X-ray Anomalous Scattering.

• We'll accept runs 27-29 and 31 ("calibration27") for experiment 239, and in experiment 240 runs 3-7, 10, 11, 14-19, 23-30 and 32-40 ("calibration3"). We will discard run 9 due to the unique detector distance for this single run and there is no dark at a corresponding detector distance.

Prepare to mask out the untrusted pixels

We'll now calculate dark-subtracted averages for experiment 239.

for m in 27 28 29 31; \
 do echo $m; cxi.lsf -c ~/myrelease/cxi84914/mkavg_e239.cfg \
 -o /reg/d/psdm/cxi/cxi84914/scratch/$USER/averages/e239/ \
 -i /reg/d/psdm/cxi/cxi84914/xtc/e239 -q psanacsq -s -p 8 -x 239 -r ${m} -t 0; done

This repeats exactly the same averaging calculations as before, except the dark average from run 30 is subtracted. The dark image to be subtracted (along with its std deviation) is defined in the configuration file mkavg_e239.cfg.

Now we'll figure out which pixels are untrusted, and thus should not be integrated. Three criteria will be used:

• Hot pixels--on the average-dark the pixel values exceed 1350 (should be fine tuned by inspecting the dark & using trial and error)
• Hot pixels--on the standard deviation-dark the stddev exceeds 5 and therefore unreliable (also should be fine tuned by trial and error)
• Cold pixels or shadows--on a maximum-composite data image, inspect values and set a minimum threshold value (we choose 20 here)

cxi.make_mask -v --maxproj_min 20 --avg_max 1350 --stddev_max 5 --output mask_base.pickle \
 /reg/d/psdm/cxi/cxi84914/scratch/$USER/initial_dark/e157/r0031/000/out/avg-r0031.pickle \
 /reg/d/psdm/cxi/cxi84914/scratch/$USER/initial_dark/e157/r0031/000/out/stddev-r0031.pickle \
 /reg/d/psdm/cxi/cxi84914/scratch/$USER/averages/e157/r0020/000/out/max-r0020.pickle

Inspect the mask:

cctbx.image_viewer mask_base.pickle show_untrusted=true

Simple thresholding wasn't sufficient for capturing some shadow areas and also an apparent untrusted region in one of the ASICs. Calculate some additional masks using the polygon feature; tied to our current metrology. Reading off polygon vertices from the cctbx.image_viewer, be sure to read coordinates as fast,slow (reverse order).

cxi.make_mask -v --poly_mask=1258,83,1148,9,1258,9 --output=mask_inactive.pickle -a 3000 -s 100 -m 0 \
/reg/d/psdm/cxi/cxi84914/scratch/$USER/initial_dark/e157/r0031/000/out/avg-r0031.pickle \
/reg/d/psdm/cxi/cxi84914/scratch/$USER/initial_dark/e157/r0031/000/out/stddev-r0031.pickle \
/reg/d/psdm/cxi/cxi84914/scratch/$USER/averages/e157/r0020/000/out/max-r0020.pickle

Shadow on runs 17-20:

cxi.make_mask -v --poly_mask=915,1696,712,1719,506,1750,915,1750 --output=mask_shadow17.pickle -a 3000 -s 100 -m 0 \
/reg/d/psdm/cxi/cxi84914/scratch/$USER/initial_dark/e157/r0031/000/out/avg-r0031.pickle \
/reg/d/psdm/cxi/cxi84914/scratch/$USER/initial_dark/e157/r0031/000/out/stddev-r0031.pickle \
/reg/d/psdm/cxi/cxi84914/scratch/$USER/averages/e157/r0020/000/out/max-r0020.pickle

Shadow on runs 21-27:

cxi.make_mask -v  --output=mask_shadow21.pickle -a 3000 -s 100 -m 0 \
 --poly_mask=1741,1536,1540,1518,1331,1506,1120,1505,918,1515,712,1550,496,1576,286,1629,86,1685,86,1754,1741,1754 \
/reg/d/psdm/cxi/cxi84914/scratch/$USER/initial_dark/e157/r0031/000/out/avg-r0031.pickle \
/reg/d/psdm/cxi/cxi84914/scratch/$USER/initial_dark/e157/r0031/000/out/stddev-r0031.pickle \
/reg/d/psdm/cxi/cxi84914/scratch/$USER/averages/e157/r0021/000/out/max-r0021.pickle

Combine three masks together for runs 17-20:

cxi.or_mask mask_base.pickle mask_inactive.pickle mask_shadow17.pickle \
 /reg/d/psdm/cxi/cxi84914/scratch/$USER/averages/e157/mask_calibrate17.pickle

Combine three masks together for runs 21-27:

cxi.or_mask mask_base.pickle mask_inactive.pickle mask_shadow21.pickle \
 /reg/d/psdm/cxi/cxi84914/scratch/$USER/averages/e157/mask_calibrate21.pickle

Now We need to repeat the procedure above to calculate dark-subtracted averages for experiment 240.

for m in 3 4 5 6 7 10 12 14 16 17 18 19 21 23 24 25 26 27 28 29 20 32 33 34 35 36 37 38 39 40; \
 do echo $m; cxi.lsf -c ~/myrelease/cxi84914/mkavg_e240.cfg \
 -o /reg/d/psdm/cxi/cxi84914/scratch/$USER/averages/e240/ \
 -i /reg/d/psdm/cxi/cxi84914/xtc/e239 -q psanacsq -s -p 8 -x 240 -r ${m} -t 0; done

This repeats exactly the same averaging calculations as before, except the dark average from run 31 is subtracted. The dark image to be subtracted (along with its std deviation) is defined in the configuration file mkavg_e240.cfg.

Correct the detector metrology

Accurate data integration requires highly precise knowledge of pixel positions in laboratory space (metrology). Gaining this knowledge is especially difficult due to the segmented nature of the CSPAD detector, which is tiled into 64 application-specific integrated circuits (ASICs). The 64 ASICs are arranged in quadrants that are approximately 4-fold rotationally symmetric, with 8 sensors per quadrant and 2 ASICs per sensor. The sensors are field-serviceable, and may therefore change from Run to Run.

We thus need to determine positions and rotations for all 64 tiles, ideally down to an accuracy on order of 10 microns. As a general overview, cctbx takes the following steps:

• Tile placement in physical space is measured by the beamline operators optically using electron microscopy. This is done at the per-sensor level (2 ASICs per sensor). This is already hard-coded; nothing for the user to do.

• Relative positions of the quadrants are determined coarsely by considering powder rings.

• Sensor positions are refined based on Bragg spot diffraction, allowing for whole-pixel translations in x and y.

• ASIC positions are refined to subpixel accuracy based on Bragg diffraction, allow for sub-pixel translations and rotations.

Quadrant positions

The electron microscopy step above determines only the sensor positions relative to the frames of reference of each quadrant; but not the absolute position of each quadrant in space. At the CXI instrument, the forward detector DS1 has rail-mounted quadrants to allow re-sizing of the central hole. The quadrant placement should be assessed for both the forward and back (DS2) detectors.

For thermolysin we examine one of the strong images (maximum composite). Students may use the instructor's files ($USER=nksauter). We first determine that our image has a timestamp that identifies it within cctbx as being from run 5 (2011):

cxi.print_pickle /reg/d/psdm/cxi/cxi84914/scratch/$USER/averages/e157/r0021/000/out/max-r0021.pickle 
 > Detector format version: CXI 5.1
cxi.detector_format_versions
cxi.detector_format_versions "CXI 5.1"
cxi.view /reg/d/psdm/cxi/cxi84914/scratch/$USER/averages/e157/r0021/000/out/max-r0021.pickle \
 distl.detector_format_version="CXI 5.1" viewer.calibrate_unitcell.d_min=10 \
 viewer.calibrate_unitcell.unitcell=94,94,130.8,90,90,120 viewer.calibrate_unitcell.spacegroup=P6122

The "Settings" GUI panel shows detector distance as well as the hard-coded quadrant positions corresponding to "CXI 5.1", namely -3,-1,-1,-5,-13,2,-7,-4. Tile translations have been zeroed out in the code. The settings can be changed in the panel, or alternately given as a separate command line parameter (distl.quad_translations=-3,-1,-1,-5,-13,2,-7,-4). The object is to align the powder pattern with the predicted rings (red circles) based on the unit cell parameters. It can be seen that the alignment is not quite perfect.

Since we have well-formed powder rings, we can run the automatic quadrant positioning tool:

cspad.quadrants /reg/d/psdm/cxi/cxi84914/scratch/$USER/averages/e157/r0021/000/out/max-r0021.pickle \
 distl.detector_format_version="CXI 5.1"
> The NEW QUAD translations are: [-4, -4, -1, -7, -13, 1, -7, -6]

Try a few different max-composites from runs 21-24:

The NEW QUAD translations are: [-4, -5, -2, -7, -12, 0, -7, -5]

The NEW QUAD translations are: [-3, -4, -1, -7, -12, 0, -7, -5]

The NEW QUAD translations are: [-3, -3, -4, -6, -12, 0, -7, -5]

The NEW QUAD translations are: [-3, -3, -1, -7, -11, 0, -6, -3]

These can be pasted on to the command line for graphical review:

cxi.view /reg/d/psdm/cxi/cxi84914/scratch/$USER/averages/e157/r0021/000/out/max-r0021.pickle \
 distl.detector_format_version="CXI 5.1" viewer.calibrate_unitcell.d_min=10 \
 viewer.calibrate_unitcell.unitcell=94,94,130.8,90,90,120 viewer.calibrate_unitcell.spacegroup=P6122 \
 distl.quad_translations=-3,-4,-3,-7,-12,0,-7,-5

This looks slightly better. From the GUI it also appears that distance=176 fits better than distance=171; meaning that the detz_offset for the configuration file should be 576, not 571.

Unit-pixel tile positions

Now we will index the data to derive model lattices. [The configuration file L498-thermolysin-17.cfg names our phil parameter file L498-thermolysin-t000.phil (t000 means trial 0)]. We'll then compare model and observation, from which we can deduce better metrology.

for m in 17 18 19 20; \
 do echo $m; cxi.lsf -c ~/myrelease/cxi84914/L498-thermolysin-17.cfg \
 -o /reg/d/psdm/cxi/cxi84914/scratch/$USER/results/e157/ \
 -i /reg/d/psdm/cxi/cxi84914/xtc/e157 -q psanacsq -p 8 -x 157 -r ${m} -t 0; done

for m in 21 22 23 24 25 26 27; \
 do echo $m; cxi.lsf -c ~/myrelease/cxi84914/L498-thermolysin-21.cfg \
 -o /reg/d/psdm/cxi/cxi84914/scratch/$USER/results/e157/ \
 -i /reg/d/psdm/cxi/cxi84914/xtc/e157 -q psanacsq -p 8 -x 157 -r ${m} -t 0; done

bkill 0 # stop all jobs; wrong file path

A quick command to count how many integration files there are:

for m in `seq 17 27`; \
do echo $m `find /reg/d/psdm/cxi/cxi84914/scratch/$USER/results/e157/r00$m/000/integration -name "int*.pickle"|wc -l` ; done; \
find /reg/d/psdm/cxi/cxi84914/scratch/$USER/results/e157/*/000/integration -name "int*.pickle"|wc -l

Determine whole-pixel translations for all sensors on the CSPAD.

cspad.metrology data=/reg/d/psdm/cxi/cxi84914/scratch/$USER/results/e157/r*/000/integration bravais_setting_id=12 max_frames=1000 min_count=25 detector_format_version="CXI 5.1" cxi84914/L498-thermolysin-t000.phil | tee L498-17-t000.unit

List out the new unit translations:

cat L498-17-t000.unit |grep -A21 "Unit translations"

Results from three refinement cycles are listed; capture the last one and incorporate it into a new version of the integration phil file, L498-thermolysin-t001.phil. Also in this phil file, for the next integration round we'll increase our integration limits (3 places) to 1.8 Angstroms. After editing the configuration file to use this new phil file, submit the new round of integration jobs.

For the purpose of the tutorial, we'll drop runs 17-20 since they contribute only 1095 lattices compared with >18000 for runs 21-27. Fine-tuning of the metrology for runs 17-20 would have to be performed separately since the detector is at a different distance.

for m in 21 22 23 24 25 26 27; \
 do echo $m; cxi.lsf -c ~/myrelease/cxi84914/L498-thermolysin-21.cfg \
 -o /reg/d/psdm/cxi/cxi84914/scratch/$USER/results/e157/ \
 -i /reg/d/psdm/cxi/cxi84914/xtc/e157 -q psanacsq -p 8 -x 157 -r ${m} -t 1; done

Another round of metrology refinement, this time using trial 001 as the basis:

cspad.metrology data=/reg/d/psdm/cxi/cxi84914/scratch/$USER/results/e157/r002[1-7]/001/integration bravais_setting_id=12 max_frames=1000 min_count=25 detector_format_version="CXI 5.1" cxi84914/L498-thermolysin-t001.phil | tee L498-21-t001.unit

…proving we have not yet converged. Take this output and construct trial 002: L498-thermolysin-t002.phil; edit the *.cfg file. Submit another round of integration jobs:

for m in 21 22 23 24 25 26 27; \
 do echo $m; cxi.lsf -c ~/myrelease/cxi84914/L498-thermolysin-21.cfg \
 -o /reg/d/psdm/cxi/cxi84914/scratch/$USER/results/e157/ \
 -i /reg/d/psdm/cxi/cxi84914/xtc/e157 -q psanacsq -p 8 -x 157 -r ${m} -t 2; done

Evaluate metrology again:

cspad.metrology data=/reg/d/psdm/cxi/cxi84914/scratch/$USER/results/e157/r002[1-7]/002/integration bravais_setting_id=12 max_frames=1500 min_count=25 detector_format_version="CXI 5.1" cxi84914/L498-thermolysin-t002.phil | tee L498-21-t002.unit

Add sub-pixel corrections

There are negligible changes in the unit-translations (non-zero only at large radius), and the rmsd is now 0.96 pixels. We'll leave the unit-translations exactly where they are now, and add subpixel translations and rotations to the phil file. These are taken from the very end of the log file (L498-21-t002.unit). Incorporate these into L498-thermolysin-t003.phil.

Integrate the data

We're ready for the final integration trial, which will be t003. Again edit the configuration file L498-thermolysin-21.cfg so that it points to the latest phil file, L498-thermolysin-t003.phil. Submit integration jobs:

for m in 21 22 23 24 25 26 27; \
 do echo $m; cxi.lsf -c ~/myrelease/cxi84914/L498-thermolysin-21.cfg \
 -o /reg/d/psdm/cxi/cxi84914/scratch/$USER/results/e157/ \
 -i /reg/d/psdm/cxi/cxi84914/xtc/e157 -q psanacsq -p 8 -x 157 -r ${m} -t 3; done

…19980 lattices indexed and integrated. If the second lattice is desired (about 10% of images have two) set indexing.outlier_detection.switch=True in the phil file, and integrate again under a new trial number (-t 4).

Trial 005: Try first-lattice again, correcting an omission of the mask_pixel_value=-2 phil parameter in trial 003.

…19987 lattices indexed and integrated in trial 005.

Merge the data

on pslogin, download the reference structure 2tli from the pdb (must be done on pslogin, the only outward-facing host). 2tli.pdb will be used for per-image scaling; 2tli.mtz will be used for reporting correlation to isomorphous synchrotron data.

phenix.fetch_pdb --mtz 2tli

back to psana. Get the command file mergethermo.csh.

mkdir /reg/d/psdm/cxi/cxi84914/scratch/$USER/merge/e157
cd /reg/d/psdm/cxi/cxi84914/scratch/$USER/merge/e157
./mergethermo.csh

Log file

Better log file from trial 005--using untrusted pixel mask

Solve the structure

Some quick commands to evaluate the data. Here the result *.mtz files must be moved back to your $HOME directory and transferred to your laptop to run PHENIX:

cp /reg/d/psdm/cxi/cxi84914/scratch/$USER/merge/e157/thermoanom_2tli_s0_mark0.mtz $HOME
cp /reg/d/psdm/cxi/cxi84914/scratch/$USER/merge/e157/thermonoanom_2tli_s0_mark0.mtz $HOME

Always use the "s0" files; "s1" and "s2" are the semi-datasets used only to calculate CC1/2.

phenix.fetch_pdb --mtz 2tli
phenix.xtriage thermonoanom_2tli_s0_mark0.mtz scaling.input.xray_data.obs_labels=Iobs > triage_noanom.log

Wilson B factor:14.8

phenix.automr 2tli.pdb thermonoanom_2tli_s0_mark0.mtz seq_file=2tli.fa identity=100 copies=1 build=False

The MR-placed model is in ./AutoMR_run_1_/MR.1.pdb.

Obtain the set of R-free-flags used in the Nature Methods paper

wget http://cci.lbl.gov/publications/download/4ow3_original_iobs_flags.mtz

Refine the model

phenix.refine ./AutoMR_run_1_/MR.1.pdb refinement.output.prefix=001 \
 xray_data.file_name=thermonoanom_2tli_s0_mark0.mtz \
 xray_data.r_free_flags.file_name=4ow3_original_iobs_flags.mtz \
 xray_data.r_free_flags.label=R-free-flags \
 main.number_of_macro_cycles=6 optimize_xyz_weight=True \
 optimize_adp_weight=True nproc=20 refinement.input.xray_data.labels=IMEAN \
 ordered_solvent=true ordered_solvent.mode=every_macro_cycle

trial 003: RWORK = 23.1% RFREE = 26.5% out to 2.1 Angstrom

trial 005: RWORK = 22.0% RFREE = 26.3% out to 2.1 Angstrom (taking untrusted pixels into account)

Run an ersatz script (provided by Nat Echols) to measure the peak heights of the anomalous scatterers.

libtbx.python map_height_at_atoms.py \
 001_001.pdb thermoanom_2tli_s0_mark0.mtz \
 input.xray_data.labels=Iobs \
 xray_data.r_free_flags.file_name=4ow3_original_iobs_flags.mtz \
 xray_data.r_free_flags.label=R-free-flags

Promising results for the Zn and one Ca:

pdb="ZN    ZN A 317 " :   5.97 sigma
pdb="CA    CA A 318 " :   0.93 sigma
pdb="CA    CA A 319 " :   2.74 sigma
pdb="CA    CA A 320 " :   1.08 sigma
pdb="CA    CA A 321 " :   0.20 sigma

Better results from trial 005:

pdb="ZN    ZN A 317 " :   7.66 sigma
pdb="CA    CA A 318 " :   1.10 sigma
pdb="CA    CA A 319 " :   2.52 sigma
pdb="CA    CA A 320 " :   1.40 sigma
pdb="CA    CA A 321 " :   1.01 sigma