Changes

Line 1,260: Line 1,260:  
</pre>
 
</pre>
 
If you do use cut-and-paste from the webpage, be aware of the following problem report: On the Mac, after loading frames, by clicking “generate XDS.INP”, the program gives some strange symbol “” in XDS.INP. And the more you click “save” button, the more “” appear. This looks like e.g. <br>SPACE_GROUP_NUMBER=0  ! 0 if unknown <br>UNIT_CELL_CONSTANTS= 70 80 90 90 90 90  <br> ''The problem is due to the “Rich text” format in TextEdit when saving "generate_XDS.INP". It is solved by re-downloading the script, and changing format to Plain - everything should work then.''
 
If you do use cut-and-paste from the webpage, be aware of the following problem report: On the Mac, after loading frames, by clicking “generate XDS.INP”, the program gives some strange symbol “” in XDS.INP. And the more you click “save” button, the more “” appear. This looks like e.g. <br>SPACE_GROUP_NUMBER=0  ! 0 if unknown <br>UNIT_CELL_CONSTANTS= 70 80 90 90 90 90  <br> ''The problem is due to the “Rich text” format in TextEdit when saving "generate_XDS.INP". It is solved by re-downloading the script, and changing format to Plain - everything should work then.''
 +
 +
Attention beamline staff: it would be great if you could make a one-line change to the script after downloading, in order to point to the correct path to Dectris' Neggia library, or the Durin plugin, respectively. Just open the script with an editor and adjust neggia_path or durin_path ! This relieves users from having to change the LIB= line for every data set.
    
== Calling generate_XDS.INP from a Python script ==
 
== Calling generate_XDS.INP from a Python script ==
2,538

edits