Spectrum Standard v10.4.

4
Known Bugs
About This Document
This document provides the following information about Spectrum v10.4.4:

1. General
2. Known Issues Associated with the Windows 7/8 Operating Systems
3. Known Issues in Spectrum Quant

1. General
· Incorrect display of certain fonts (Bug 5643)
Numbers and italicized text may not be displayed correctly in reports when certain fonts are
used. When designing a new report template, check that the appearance of your report is
correct when it is saved or printed before using the template.
· Delays when previewing or saving lengthy reports in Spectrum and Report Designer
(Bugs 5579, 5899)
If a report template contains many data tables and/or the results for many samples are being
reported in a single document, there may be a lengthy delay in producing the final report or in
previewing the report in Report Designer.
· Layout of text may be misleading when Word Wrap is set to No (Bug 5752)
In Report Designer, if two lines of text are placed in a text box in a template and the Word
Wrap property is set to No, the final report will only display the first line of text, even though
Report Designer shows both lines on the canvas. Setting Word Wrap to Yes solves this
problem.
· Peak Table and Peak Area/Height results may not be reported correctly (Bug 5486)
In some report templates, the results for Peak Table and Peak Area/Height may not be
reported separately because they both use the same results tab in Spectrum. The solution is to
put the two report items in separate sections in the Report Designer template, and then repeat
each section for the appropriate sets of results.
· Default settings not restored in all cases for NIRA II (Bug 2340)
Check that the number of scans reads 32 and the scan mode is Interleaved when you restore
default settings for the NIRA II accessory.
· Duplicate spectral libraries can appear when upgrading Spectrum software (Bug
1455)
The duplicated entries can be removed by resetting the workspace layout.
· If there are Windows updates pending during the installation, then an error is
triggered (Bug 2547)
It may be possible to fix this problem by retarting the PC and running the setup.exe in repair
mode, but in general the best approach is to uninstall Spectrum and then re-install it once all
Windows updates are completed.
· Creating PDF reports using Far East language packs can cause an “out of memory”
error (Bug 1111)
Please close Spectrum (select Save for reload to retain your settings) and restart the software.
· Uninstalling AssureID (v 4.2.0) corrupts the installation of Spectrum 10 (Bug 1448)
The repair process can be initiated by running the Spectrum 10 application which results in
the Spectrum Touch installer running in repair mode. On completion of the installation
Spectrum 10 and Touch applications will function normally.
· If the user changes the accessory to a shuttle or a NIRA, the interleaved scan option
is not available (Bug 1093)
Please restart Spectrum and the interleaved scan option becomes available.
· If a user is creating touch macros to analyse existing spectral data only, the sample
scan step is still required (Bug 1008)
When a Touch sample step is included, the macro will run correctly.
· If the user runs a macro and an AVI calibration is required, the prompt dialog is
hidden behind the Touch screen (Bug 1381)
Please ensure an appropriate AVI calibration is in place before using it in a Touch macro.
· Setup Pathlength does not work correctly with nanometer units (Bug 4443)
This problem is being investigated. Please use cm-1 units only with the pathlength feature.
· Export spectra does not allow a point separator when the default separator is a
comma (Bug 3034)
Modify the system Regional and Language Options from the Windows Control Panel to
change the decimal separator to a point to allow a point separator to be used.
· Applying gridlines to a spectrum after zooming in can cause the software to lock up
(Bug 1455)
If a spectrum displayed is zoomed in to maximum extent and then gridlines are applied, the
application can lock up. However, if the full spectrum is displayed (fully zoomed out) then
gridlines can be applied.
· Send-To-Word/Send-To-Excel will only work on Office 2007 and later versions
(Bug 1757)
Send-to-Word/Send-To-Excel requires Microsoft® Office 2007 or later to be installed.
· Send-To-Word/Send-To-Excel will not work unless Office 2007 has been initialized
(Bug 1395)
After installing Office on the computer, Word/Excel should be opened and used at least once.
This initializes Office and, from that point on, the Send-To-Word/Send-To-Excel function in
Spectrum should work correctly. If an error still occurs with Office 2007, then it could be
that the primary interop assemblies (PIA) for Office were not installed when Office was
installed. These can be installed either through the Office install CD or, alternatively, on the
root of the Spectrum install CD is a self-extracting EXE called PrimaryInteropAssembly for
Office 2007. First run the EXE, agree to the Microsoft license and select a directory to
extract the files into (for example c:\temp\office2007). Navigate to this folder and then run
the O2007PIA.MSI installer program. This will install the primary interop assemblies
allowing Spectrum to send spectra and tables to Word/Excel 2007.
· Clicking the “help” question mark in the Graph Properties dialog does not display
the Help (Bug 1640)
With the Graph Properties dialog displayed, clicking the question mark in the title bar
produces the query cursor. However, clicking that query cursor on an interface item does not
bring up a help display. It is recommended that the F1 button is used to display help when
required.
· Changing the auto name is not used for the first scan (Bug 1751)
When changes are made to the auto name, the changes are not used for the first scan that is
performed. The second and subsequent scans do use the new auto name. To avoid this delete
the existing sample(s) from the sample table and new ones that are added will then use the
new auto name.
· Selecting a sample in the sample table and then clicking run does not run the
selected sample but the next un-run sample (Bug 1980)
The selection state of a sample in the table does not match the expectation to run the selected
sample when the start button is hit and instead the first un-run sample is run. To run a
specific sample from the sample table move it to the top of the un-run samples.
· Change of UATR top plate not recognized by software unless UATR is removed and
replaced (Bug 1753)
Changing the UATR top-plate whilst the UATR is still plugged in will not be recognized by the
application and will not update the beam-path diagram. To avoid this unplug the UATR to
change the top-plate; on insertion the new top-plate is correctly recognized in the beam path.
· Vertical Cursor causes unexpected results when the cursor is turned off via the
context menu whilst over the cursor itself (Bug 1970)
If a user selects the vertical cursor and then turns it off via the right-click context menu on
the cursor line itself, the cursor goes but the actual mouse cursor remains in double-arrow
form and certain functions cannot be carried out. The workaround is to turn the vertical
cursor back on using either the context menu or the toolbar icon and then turn the cursor off,
either using the toolbar icon or by using the context menu on the graph background but not
on the cursor line itself.
· Configuring shift F1 as a process keyboard shortcut brings up the help, not the
process (Bug 1972)
A toolbar can be customized by going into the toolbar customize menu from the View menu
or by using the special drop-down button at the end of a toolbar and choosing Customize. If
the keyboard button is then clicked, a key combination can be defined as a shortcut for a
menu item. If <shift F1> is chosen then this will bring up the help when invoked instead of
the chosen menu item.
· Application crashes if the user clicks the color button with no spectra loaded in the
graph window (Bug 1763)
If no spectra are loaded in the graph window and the context menu on the graph window is
used to bring up the ‘Properties' dialog and then under the 'Advanced' tab the Color button is
pressed, the application crashes. This button works fine if spectra have been loaded into the
graph window.
· Maximum number of continuously scanned samples in a sample view is limited to
350 (Bug 1618)
Scanning a large number of samples, for example, over 350 in an individual sample view,
causes the application to slow down. Creating more than one sample view to scan data into
will improve this issue.
· Instrument settings changed without subsequent scanning are not remembered if
the software is shutdown (Bug 2408)
If you do not collect data after having changed some instrument settings and then exit the
software the instrument settings that are shown the next time you login will be the ones from
the last scan you performed with the same instrument/accessory combination. This means
that if you want to configure a workspace with certain instrument settings, you must perform
a scan (for example, a background) with those settings before exiting the software for them to
be remembered.
· View menu items relating to graph are non-functioning for a results tab graph
(Bug 2557)
The View menu items only work on the multiple or single Samples View graphs but not for
the Compare and Search graphs. To manipulate these graphs, use the context menu on the
graph to select graph options or the graph's property pages.
· Removing a user's workspace from Spectrum (Bug 2663)
If a user is deleted from the security database, the workspace files (that is, default settings,
GUI layout, equations, process chains, etc.) associated with that user are not deleted from the
hard disk. If it is required to remove these files, then login to Windows with an admin
account and start Windows Explorer and make sure that, under Tools->Folder
Options->View in XP or Organize->Folder and Search Options->View in Windows 7 or
View->Options-> Change folder and search options->View in Windows 8, the "Show hidden
files and folders" option is selected. On the root of the Windows drive navigate to
Documents and Settings\All Users\Application Data\PerkinElmer\Spectrum\Users for XP
and ProgramData\PerkinElmer\Spectrum\Users for Windows 7/8. There will be a folder with
the user's name which can be deleted to remove their workspace.
Note that if the login type is switched from, say, PerkinElmer login to Windows login then
new workspaces are created for the Windows login users. If the login type is switched back
again the original workspaces are still intact unless they have been manually removed.
· Macro – search in process chain allows duplication of library directories causing
duplicate runs (Bug 2681)
When a Setup Macro is performed and the search process is added to the macro then the list
of available libraries (from the Setup Libraries and Search library list) is copied into the
search process setup and the libraries to be searched can be selected. If a library from the
Setup Libraries and Search library list is subsequently deleted it still remains available in the
macro’s search process setup since it is using the library list that was available when the
process was added. However, if in the Setup Libraries and Search tab a library with the same
name as the deleted library is added and the macro is edited then any libraries that are in the
Search process setup that have been deleted are re-added to the Setup Libraries and Search
library list and any new libraries are added to the Search process setup's library list. Hence
there will now be 2 libraries with the same name in both lists.
It is recommended that if you setup a Search process in a macro that you do not delete any
libraries in the Setup Libraries and Search library list without first deleting the macro or
removing the Search process from it and then re-adding it with the new library list.
· When NIRA is in interleaved mode, preview does not display any spectra (Bug 2682)
If preview for scanning is selected then the software should enter monitor mode first,
allowing changes to sample positioning to be performed before scanning is initiated.
 However, for a NIRA in interleaved mode the software enters monitor energy mode and no
spectra are displayed in the preview window but a scan can be initiated as normal. If the
NIRA is not in interleaved mode, then the software works correctly.
· Instrument, Ready Checks and Instrument Verification buttons loaded twice after
Spectrum 10 upgrade (Bug 3714)
If a previous version of Spectrum 10 has been uninstalled and a new version installed, then
when the software is restarted and connected to an IR instrument duplicate menu items
appear on the Measurement menu and duplicate setup icons appear in the right-hand
shortcuts pane. These duplicate items can be removed by performing a ‘Reset Layout’
command from the Setup menu. Note that if you have more than one user defined this should
first be done on the Administrator user before any other users.
· Raman - Wavelength Calibration can fail if, prior to the calibration, an optimum
exposure calculation has been halted (Bug 3897)
If a timed scan has requested the optimum exposure time to be calculated before the scan and
this calculation is halted and another scan is not performed before a wavelength calibration is
started, then the wavelength calibration may fail. The error can be avoided by performing a
short 1 second exposure scan prior to the wavelength calibration.
· Raman - After a Raman focus the ‘Laser + shutter’ icon in the Measurement
toolbar shows the shutter open when it has been closed (Bug 3848)
Performing a scan will reset this icon to the correct state.
· Raman - Cannot reconnect to the Raman instrument within the same session of the
software (Bug 3788)
If you disconnect from the Raman instrument and then try to reconnect again within the same
software session the reconnection fails. Please close the software and then re-open to connect
again to the Raman instrument.

2. Known Issues Associated with the Windows 7/8 Operating Systems

· Instrument Install Wizard does not run after software installation if a reboot has
not been performed (Bug 2720)
After the software has been installed and the Add Instrument wizard is invoked, sometimes
no wizard will appear. If this happens, then a reboot of the PC forces the permissions to be
set on the appropriate folders and the wizard then appears correctly.
· Quant Import tool cannot be launched in Windows 8 unless Spectrum is already
running (Bug 1383)
The Quant Import tool will not launch if it is selected from the Windows 8 start menu. To
work around this, launch Spectrum first and then launch the Quant Import tool.
· Spectrum is displayed behind the Spectrum Touch screen when using Touch as a
member of the Users group (Bug 1415)
When using Spectrum 10 as a member of the Users group, launching Spectrum Touch results
in Spectrum being launched and the Spectrum Touch icon appearing on the task bar. Clicking
this icon launches Spectrum Touch but Spectrum remains displayed behind it on the screen.
The macro still runs correctly.
· Spectra may not be displayed correctly in the results screens of Spectrum Touch
(Bug 2438)
In some instances, a spectrum will not be displayed in a the results screen of Spectrum Touch
when using Windows 8. The problem can usually be corrected by resizing the Touch dialog.
3. Known Issues in Spectrum Quant
· Some minor discrepancies between Spectrum Quant and legacy Quant + methods
using the PLS1 algorithm (Bugs 3277, 3287, 3301 and 3285).
In certain cases with PLS1 models, Spectrum Quant will use a different number of latent
variables for property predictions and for spectral outlier assessment. This may lead to slight
differences in the reported residual ratio, peak-to-peak error, RMS error and M-distance
compared to an otherwise equivalent Quant+ method.
· Incorrect importing of standards in imported Quant+ methods (Bugs 3380 and
3254)
Check that all the standards in legacy Quant+ methods are correctly imported into Spectrum
Quant. In some instances, previously excluded standards may now be included in the model,
or there may be some missing property values. Samples previously used in Independent
Validation may now be included in the calibration.
· No “Set Model Factors” option in PLS1 (Bugs 3258 and 2834)
In methods using the PLS1 algorithm, it is not possible to overwrite the automatic selection
and manually specify the exact number of factors (latent variables) to be used in the model in
all instances. Only the maximum number of factors can be selected.
· Missing property values are not supported (Bugs 2683 and 3264)
The calibration and independent validation calculations do not currently support missing
values in property data in standards. Ensure that there are no missing values in your data.
· Custom fields are not recognized in Independent Validation (Bug 3361)
Adding standards that contain custom columns to Independent Validation will not prompt the
Custom Columns dialog to appear. You will need to manually add the correct columns and
enter the relevant data. Calibration samples with custom columns are recognized by the
software.
· Residual spectra are sometimes plotted with the incorrect ordinate units (Bug 3512)
The units can be converted by clicking the Absorbance button in the toolbar or under the
View menu.
· Methods saved without spectra cannot be calibrated or validated when the name of
the standards folder is changed (Bugs 3590-4)
Saving a method without spectra allows it to be used for prediction without the calibration or
validation data being available, and also reduces the size of the method file. If you want to
rerun the calibration or independent validation on a method saved without spectra, ensure
that the calibration and validation spectra are present in the same location as they were when
the method was first calibrated.
· Toolbars do not update when a QuantC algorithm method is changed to a PCR+ or
PLS1 method (Bug 3604)
Clicking an option on the Method Explorer will refresh the screen and update the toolbars
with the correct options.
· When Creating a Beers law Peak Height method, valid Start and End values must
be generated.
Before switching to peak height calculations, please set the Start and End values to values
within the standards spectral range. To correct this simply switch the calculation type to
“max peak height” enter a valid start and end value, then switch it back to “peak height”.
· The validation report can sometimes fail to update.
The validation report can sometimes fail to update. To force it to update simply minimize it,
and maximize it again.
· The validation can be run when standards have no property values.
The result obtained from validation standards with no property information is erroneous.
· The default normalization value in the predict table is Zero.
When adding samples to the predict table and normalization is turned on the default
normalization values are set as zeros. This default is incorrect and should be changed by the
user.