Generate XDS.INP: Difference between revisions

JanGeb (talk | contribs)
The script: Added support for Pilatus 4M CdTe @ ID30B/ESRF (rev. 1.24)
m Usage: mention xds-zcbf plugin
 
(3 intermediate revisions by the same user not shown)
Line 5: Line 5:
Usage is just (don't forget the quotation marks!):
Usage is just (don't forget the quotation marks!):
  generate_XDS.INP "/home/myname/frms/mydata_1_???.img"
  generate_XDS.INP "/home/myname/frms/mydata_1_???.img"
XDS [https://xds.mr.mpg.de/html_doc/xds_parameters.html#NAME_TEMPLATE_OF_DATA_FRAMES= supports] bzip2-ed frames. Thus, when specifying the frame name parameter of the script, you should leave out any .bz2 extension.
For .h5 files you need to load the *master.h5 , and you don't need the quotation marks:
generate_XDS.INP /home/myname/frms/mydata_1_master.h5
XDS [https://xds.mr.mpg.de/html_doc/xds_parameters.html#NAME_TEMPLATE_OF_DATA_FRAMES= supports] compression with gzip or bzip2. When specifying the frame name parameter of the script, you should leave out any .gz or .bz2 extension. Note that the processing of *.cbf.gz files can be made faster by [[Installation|loading]] the xds-zcbf.so [[LIB|plugin]].


For improved interaction with [[XDSGUI]], it is advantageous to provide an ''absolute'' filename for the data files - one that starts with a slash ("/").
For good interaction with [[XDSGUI]], it is advantageous to provide an ''absolute'' filename for the data files - one that starts with a slash ("/").


== The script ==
== The script ==
Line 15: Line 17:
<div class="mw-collapsible-content">
<div class="mw-collapsible-content">


<pre>#!/bin/bash
<pre>
 
#!/bin/bash
# purpose: generate XDS.INP
# purpose: generate XDS.INP
#
#