What's new in CrystalClear™ 1.4.0 SP1
There are several bug fixes and enhancements in CrystalClear 1.4.0 SP1.
New Features
The new features that are available in CrystalClear 1.4.0 SP1 are:
- Implemented mechanism to write MessageManager-written messages to a sample_status.log file located in the sample directory while a sample is open.
- User-specifiable sequence starting number of both the first scan in a
schedule as well as subsequent scans in the schedule based on a
predetermined inter-scan
increment. Two new parameters have been added to the application
configuration file to support this mechanism:
- ScheduleFirstScanStartNum
- InterScanStartNumIncrement
Bug fixes/Enhancements
The bug fixes/enhancements that are available in CrystalClear 1.4.0 SP1 are:
- Enhancements
- Implemented mechanism to report actual errors when reading a configuration file using the Read() method in the configuration file interpreter class.
- Implemented latest version of System-Y structure modeling program (dated October 9, 2007)
- Bug fixes: CrystalClear
- Fixed problem in FS_PROCESS with user-specified resolution limit value specified in FS_PROCESS Integration dialog not being passed and used in the scale and average command step.
- Fixed problems in small molecule mode flowbar encountered when last command executed is the Write CIF command and one re-enters the sample after closing CrystalClear. The fix will reset the saved button back to the Setup dialog. The same problem also caused a crash when completing a menu-spawned spacegroup check and the last command prior to running the spacegroup check is the Write CIF command.
- Fixed crash occurring for RAPID instruments after the second Mount Crystal command message is dismissed when opening a new screen, collect, and process task sample with FS_PROCESS as the processing suite. Also fixed the related problem where a two-button space was being displayed at the top of the flowbar upon dismissing the second Mount Crystal command message for RAPID instruments when opening a new screen, collect, and process task sample with d*Trek as the processing suite.
- Fixed problem in d*TREK dtmultistrategy where an S1 labeled scan (second scan as stored in the header) was attempted to be evaluated and failed if the chi and phi rotation angles are not defined for the instrument.
- Removed Strategy flowbar button in FS_PROCESS prcessing as it currently is no longer supported.
- Fixed problem with resource.dat not being updated in timely fashion with the scanner: value when running Collect-style tasks in FS_PROCESS. Without this fix, FS_PROCESS processing could not proceed.
- Fixed image step defaults for scans of schedules labeled Two: 0, 30, Two: 0, 90, and Four: 0, 90, 180, 270 for all instrument types.
- Fixed crash resulting from starting a collection when the JXG server is connected and the pre- and post-collection JXG script combo boxes contain "(None)" as the value.
- Fixed problem with Strategy where erroneous -crysgonio options were placed on dtmultistrategy command line for non-existent or virtual goniometer axes.
- Fixed problem with resource.dat being updated with d*Trek orientation angles for missetting angles when switching between d*Trek to FSP processing suites.
- Fixed apparent resetting values of certain parameters (such as scan wavelength) when a Hobbit database schema mismatch is detected and the version is updated.
- Fixed misspellings of certain fields in the resource.dat.
- Prevent acceptance of project and sample names containing any commas (,) or periods (.) in the respective Open Sample dialog combo boxes.
- Added 2 second delay after sending direct beam shot command to help ensure the DirectBeam.log file is ready to be loaded into the logfile viewer.
- Fixed image viewer crashes associated with circle mask utility. If too large a circle is drawn, CrystalClear is liable to crash due to overridden memory.
- Added parsing of FS_ABSCOR absorption correction information for inclusion in an output CIF file.
- Fixed problem with specific CrystalClear small molecule and SCXmini mode site defaults being reverted to macromolecular mode defaults when changes in database schema are detected.
- Updated defaults for small molecule and SCXmini modes of operation.
- Bug fixes: Instrument servers
- Fixed bug in applying overload correction factor when overload auto-switch is enabled. [AFC/CCD]
- Add 7-bit shift option for compressed images. [AFC/CCD]
- Add raw image replay capability. [AFC/CCD]
- Add option to compress all images no matter whether overload correction is On or Off. [AFC/CCD]
- Fixed bug in overload correction which erroneously set pixel values > 1,048,575 to saturated; gated out call in ChangeWorkingDirectory command causing freeze-up in Linux. [AFC/CCD]
- Fixed initialization of variable correponding to "-replay" command line option
- Update d*TREK library to support version 9.9. [AFC/CCD]
- Correct image decompression/compression for variable saturated value. [AFC/CCD]
- Add TimeStamp to client connection established and failed notifications. [R-AXIS]
- Enhance error reporting in DirectBeam to help troubleshoot intermittent problem. [R-AXIS]
- Fixed bug in backlash correction calculation affecting the IV++_Distance and IV++_Chi instruments.[R-AXIS]
- Add configuration file options PhiDatumOffsetPosition and UsePhiDatumOffsetPosition which are used to unwind the Phi axis to its original zero position when it calculates that it should datum during a move operation. [R-AXIS]
- Add "-recover" command line option which reads the last known Phi position from InstrumentServer.UID, or if that file is not found prompts the user to enter a position manually. Before datuming the Phi axis is datumed in place then moved to the offset position. [R-AXIS]
- Bug fixes/enhancements: d*TREK®
- Implemented new mechanism to pad strategy scan results to attempt to include entire strategy-determined range while still aligning the start angle on a whole number boundary, ensuring the number of images is consistent, and checking to make sure no collisions will occur. The image width is now input to dtmultistrategy to perform these calculations via the option -rotimagewidth. The log file reporting was enhanced to report the adjusted ranges.