EMBL/ESRF specific pages for MOSFLM
last modified
05-02-2008 13:32
News
- 2007-10-03: New MOSFLM version 7.0.1 (August 20th) installed
-
2006-05-15: New MOSFLM version 6.2.6 (May 4th) is installed as moslm626 and ipmosflm626.
-
300805: New version 6.2.5 of MOSFLM installed as mosflm625 and ipmosflm625. Please give it a try, if no negative reports have been received till beginning of next week the default version will be switched to this version.
-
170904: MOSFLM GUI bug reported, if you use this GUI please have a look in the "Known problems" section below.
-
020604: MOSFLM upgraded to version 6.2.4. The previous version 6.2.3 can still be run with the commands mosflm623 and ipmosflm623.
-
121203: MOSFLM updated to version 6.2.3. The previous version 6.2.2 can still be run with the commands mosflm622 and ipmosflm622.
-
051203: Final MOSFLM version 6.2.3 installed for Linux and SGI as mosflm623 (or ipmosflm623). This version supports the new mar225 detectors on BM14 and on ID23 - see the release notes for other things that have changed. Please try it and send any problems to the pxsoft mailing list.
Current version: 7.0.1
Template files for ESRF beamlines
| ID14-1 | ID14-2 | ID14-3 | ID14-4 | ID23-1 | ID23-2 | ID29 |
Known problems
-
Harry Powell reported this MOSFLM GUI problem:
"If you index an image using the Mosflm GUI, and accept the updated direct beam position, and then integrate images (using the GUI), it will use the beam position in the header rather than the value you just obtained. For good, well behaved crystals on a properly set up beamline this is not a problem, but for marginal images it can make the difference between no recorded intensity (!) and I/sig(I) >3 at ~2.75 A (or better).
The way round this at the moment is to type in the updated beam position in the GUI (typing it in manually sets an internal flag); an updated version of Mosflm will be available soon (probably after extensive testing at the next dna-dev meeting)..." -
Don't use "POSTREF NOMULTI"! The default is "POSTREF MULTI" and should always be used because "POSTREF NOMULTI" will break MOSFLM (see this on-site-only page for more details). If you would like to turn off the mosaicity refinement during the integration of each image you should use the commands "POSTREF USEBEAM OFF".
-
Never copy and paste space groups with the mouse! When indexing, you have at one moment to enter a solution number and a space group. If you use the mouse to copy the space group in the solution list above and paste it in the input field MOSFLM will either freeze or crash with a memory error. This will not happen immediately but much later when for example integrating the data. So, in order to be on the safe side, always type in the space group.
-
On LINUX systems: if MOSFLM is run in a NFS mounted directory it runs very slow. The reason for this is a problem with disk running on a SUN file server mounted on a Linux system. For most programs this is working fine, however for some programs, e.g. MOSFLM and SOLVE, data is written out in small pieces, and the NFS problem causes the process writing the data to slow down significally. At the ESRF we have written a wrapper for MOSFLM which automatically makes the SPOTOD file to be written to a temporary directory (/tmp/username/mosflm_tmp).