2,684
edits
Xdsconv: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
mNo edit summary |
mNo edit summary |
||
| Line 14: | Line 14: | ||
END | END | ||
EOF | EOF | ||
This latter step is not necessary for CNS and SHELX output formats, which are written directly by XDSCONV. For these output formats, one might use MERGE=FALSE to keep | This latter step is not necessary for CNS and SHELX output formats, which are written directly by XDSCONV. For these output formats, one might use MERGE=FALSE to keep obsrevations separate. | ||
To have control over the column labels, one might want to modify the simple example above as: | |||
f2mtz HKLOUT temp.mtz<F2MTZ.INP | |||
cad HKLIN1 temp.mtz HKLOUT junk_xdsconv.mtz<<EOF | |||
LABIN FILE 1 E1=FP E2=SIGFP E3=DANO E4=SIGDANO E5=ISYM | |||
LABOUT FILE 1 E1=FP E2=SIGFP E3=DANO_sulf E4=SIGDANO_sulf E5=ISYM_sulf | |||
END | |||
EOF | |||
ISYM column is important if you want to run SHARP afterwards. | |||
In the case of a MTZ file that should be used for molecular replacement and refinement, the CAD step could be used to transfer the R_free flag from a different dataset to this new dataset. Alternatively, change of labels and transfer of columns can be done in the ccp4i GUI. | |||
---- | ---- | ||