05.12.2012 Views

WinGX v1.64

WinGX v1.64

WinGX v1.64

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

9.3 PLATON - ANALYSE Menu <strong>WinGX</strong> <strong>v1.64</strong><br />

2. Problems are indicated when:<br />

• Convergence is unstable<br />

• A large number of reflections left out during the iteration process (This may be well<br />

indicative for problems with the data, and should be checked for).<br />

3. A report on the use of SQUEEZE should always state for each (significant) independent<br />

void:<br />

• Where the void is (i.e. x,y,z)<br />

• Its volume<br />

• The number of electrons recovered.<br />

12 PLATON in the <strong>WinGX</strong> implementation<br />

The version of PLATON in <strong>WinGX</strong> is virtually identical to the UNIX workstation version,<br />

except that System S is not available (it is too UNIX specific). The major differences concern<br />

the input and output files. To maintain the normal <strong>WinGX</strong> file naming protocols, the ASCII<br />

listing file is renamed as PLATON.LST while the input files are generally created<br />

automatically. In normal operation, a temporary file called name.SPF is created by reading, in<br />

the following order, the SHELXL.LST (to try and obtain errors on the coordinates), the<br />

name.RES file or the name.INS file. If there is some problem with any/either of these files,<br />

the program may abort. The first thing to check is whether the SHELXL.LST file is from a<br />

refinement which has terminated normally - if not delete this file. The output name.HKP files<br />

are also usually renamed depending on the operation carried out The program is ALWAYS<br />

run in locked mode because of this renaming procedures. The hypertext help functions<br />

exactly as in the UNIX version. .<br />

Chapter. 9.3 PLATON 43

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!