RESULT Software Release Notes

If security is enabled for RESULT, the option to “Save audit to database” may not be honored. This has been resolved.

Entries collected during Standard Time then displayed during Daylight Saving Time showed an incorrect GMT offset compared to time displayed in report. This has been resolved in this hot fix.

Negative floating-point values written modbus were incorrectly rounded to specified significant digits.

On a new system you get an error message when you try to access the Update Instrument Information command in the Service menu of RESULT Operation. On other systems you are able to get into the Update Instrument Information dialog, but you get an error message when you try to create a backup of the instrument information. This is now fixed by this hot fix. It was caused by unintended interactions caused when translation support was added for the instrument driver.

The 8333 cm-1 intercept value is not tested with the correct limits. Fix this acceptance limits to lie between -0.0500 and +0.0500.

A new policy has been added to prevent the overwriting of RESULT Operation data files. This policy is separate from the policy to prevent overwriting of workflow files in RESULT Integration. This policy can be found in the Additional Policies section in Security Admin. This affects the Archive event.

RESULT will now detect when communication to the Security Service has been interrupted.

Instrument Validation timestamp displayed in a report is now displayed with the correct time zone offset.

Service Log entries are now limited in length to prevent an empty entry in Audit Manager. Multiple entries can be created instead of single long entries.

When the Logical Specification of a Check Event is applied, the items to be tested are blank. Fix all of this instances by reloading the measurement to be tested.

Raise the snout of the tablet detector before attempting to move the autosampler.

Fix in the IGS options setting for the validation path.

Ensure that the semaphore is not released before USB reply retry.

Fix this to honor the number of decimal digits expected in the method.

This is now added back when saving a spectrum. This feature was lost in the previous release.

Clean up how the confidence values are saved during a measurement.

Fixed how pressure values are computed and saved in Sequence, especially in the mini-header.

Since the introduction of RESULT 4, the RESULT software has only been in English. With this release RESULT is also available in Chinese, French, German, Spanish and Italian. This version also introduces RESULT software in Japanese.

The inlier distance and the X sample Q residual values available from the Unscrambler measurements are now available from RESULT.

The new default is to force running a workflow at least once from a while loop.

Allow a registry item to define a new default laser frequency that will be used for all data collects.

Any bitmap file used by RESULT software may now be secured.

This option is now always done.

Add the “Before each and reset the timer” to provide a background option that will restart the timer for the timed background options. This option may be selected in the Collect event and then if the Sample Specification is used with a different Collect event, you can reset the time to time zero for the second Collect event.

If the RESULT.mdb doesn’t already exist, then the error where the database didn’t get created was fixed.

This is now fixed.

This is now fixed for all multi-byte languages.

This is now fixed. It only occurred when the offset was at least 10 steps.

This is now fixed.

This is now fixed by taking care of a null exception.

Now set to return Fail if no spectrum is available.

Make sure that the security client is available before adding to the event viewer.

When sending a floating point RESULT to OPC, the number of decimal digits was ignored. Thus the full precision RESULT was sent out on OPC. The number of OPC decimal digits is now applied properly. This problem with also found and fixed in the Write to Modbus event.

The ReStartRESULTOperation program supports the ability to reboot the computer from a workflow on demand (using the –SHUTDOWN or –RUNAPPSHUTDOWN command line options). This feature gives a log of the times when the reboot command was issued.

The Request item is set to an OPC tag index that is greater than the number of request items that are supported. When that happens now, rather than setting the value into a Request item, set it to a Measurement item. This allows it to still be viewed from OPC.

The Collect Dual Tablet background worked properly in simulation mode, but it was broken on instrument. The issue has been fixed.

The background frequency on Collect event doesn’t work in Operation mode when “Save to audit trail” is not checked. Now the dependency on this setting has been removed, and the background will be archived properly in Operation mode to support different settings of background frequency.

These two events now are available to add to Collect Sequence when creating a workflow.

In addition to concentration RESULTs, diagnostics values are now available for Report to OPC and Write to Modbus events for TQ Analyst, Unscrambler and PLSplus/IQ.

Note: Any existing workflow created prior to RESULT 4.4 using Write to Modbus or Read from Modbus will have to be recreated.

The Wavelength Reproducibility test was added to the USP35 ValPro workflows for RESULT 3. This makes the historical USP35 workflows fully compatible with USP 1856 and EP 2.2.40. These updated workflows must be copied to the Program Files (x86) / RESULT / ValPro directory, overwriting the old USP35 files. These are the same ValPro 4 workflows released in RESULT 4.2.

When “Save to Audit Trail” policy was checked, only background archiving record was captured in Archive Log, but sample archiving record was missing.

Note: In all cases, RESULT.MDB must be installed in the RESULT Data/Config folder with user permissions set per the Installing Your Software manual.

Spectrum range got clipped if regions are not the same for both transmission and reflection.

The 5000 cm-1 linearity test RESULT does not apply to the tablet detector and was removed from the USP_EP workflow.  It was correct for the old USP35 tests for the tablet analyzer ValPro workflow.

Antaris hardware and RESULT software manuals were previously available on the RESULT 3 language pack DVD. In RESULT 4 the language files are not supported, and the DVD was eliminated. PDF manuals are now available on the RESULT 4 Program DVD in the RESULT Documents directory.

When a user’s access to RESULT Integration or RESULT Operation is denied in Security Admin settings, user can still launch RESULT.

The Unscrambler Measurement is not available in the list of templates for new specification in Measure event. A configuration file formatting issue was corrected to resolve the problem.

USP35 workflows and methods are replaced with USP_EP workflows and methods to comply with new USP 1856 and existing EP 2.2.40 standards. The legacy ValPro workflows and methods are still available and remain unchanged.

One of production utility failed to read temperature properly from Heater Block due to a problem in instrument driver.

Collect Dual Tablet event shows blanked regions when different spectral ranges are used for transmission and reflection. Quantitative RESULTs may be impacted.

Workaround: Archived data can be reprocessed to recover the full spectral range.

Two drivers are installed with RESULT software, one for old electronic module, and one for the new one. RESULT will automatically detect and use the correct driver when connected with instrument.

Fixed the slowing down issue related to memory usage in live display of spectrum plots.

Fixed the issue caused by missing components in installation.

“TQ Analyst DS Data Security” is bundled with ValPro for Antaris NIR. When Security Suite is not installed, TQ Analyst will not start and you will get errors.

Workaround: Uninstalling “TQ Analyst DS Data Security” will fix the problem.

If your bench’s electronics module needs an update to new module, you will need at least RESULT 4.2 and a firmware update.

A new service – Thermo Scientific Factory Automation Service is installed and runs in the background to support Modbus TCP communication. Two text documents with help information are installed under “C:\ProgramData\Thermo Scientific\FactoryAutomationService”: ModbusConfiguration.txt for workflow configuration, and PCConfig.txt for Modbus TCP configuration and default RESULT identifiers configuration.

This event allows information from workflow events to be read from Thermo Scientific Factory Automation Service.

This event allows information from workflow events to be written to Thermo Scientific Factory Automation Service.

RESULT is updated to work with Security Suite 2.3 and Audit Manager 1.3 with fixes of handling Unicode language properly.

RESULT OPC Server database is updated to support up to 20 Operator Request and Request Event tags. RESULT OPC Test Client is also updated to display 20 sets of tags for Operator Request and Request Event.

Fixed the issue related to “Check Signature” on workflows when secure folders are not enabled.

Fixed the crash when opening workflow in a read-only folder and fixed the failure with “Check Signature” on a workflow in a read-only folder.

RESULT is updated to work with Security Suite 2.2 that supports secure folders. Also RESULT 4.0 uses Audit Manager for audit trail logs. RESULT built-in Logs still work as before.

When secure folders are enabled, user won’t be able to copy in and out of any files from the secure folders using Windows file explorer. In Integration, under File menu a “Import…” submenu should be available, and in Operation, on Manage Workflows dialog, the Import button should be enabled. User can use this Import function to import any types of files into the secure folder location.

By default, this policy is checked. In order to enable secure folders in RESULT, you need to uncheck this policy in Security Administration. When this policy is unchecked, RESULT will automatically select secure folder locations for Workflows, Archive, Standards and Backgrounds and disable the editing of these fields in Options dialog. With secure folders enabled, users can only run RESULT software to save, archive and import files to secure folders, and any modification (add, copy, delete and rename) outside RESULT will be prohibited by Thermo Security File Service.

By default, this policy is unchecked, and the behavior is the same as in older version of RSEULT, i.e. the same user can sign the same file multiple times. When this policy is checked, if trying to sign the same file more than once, an error message will pop up.

By default, this policy is unchecked. When checked, RESULT Integration will only give users a view-only user interface without any menu items on the top. User can still create or open workflow and run the workflow but won’t be able to save workflow.

By default, this policy is unchecked. When checked and also the Archive setting of “Require digital signature” is checked, during workflow runtime, user won’t be able to cancel the “Sign File” dialog. If it fails on the first try, user will be prompted three times. If all three tries failed, a workflow error will be generated.

Be default, this policy is unchecked. When checked, running a workflow in Operation, user can only Pause and Resume a workflow, but won’t be able to Stop the workflow.

To support a special application, increase the number of RequestInputEvent items from 16 to 24 in RESULTOPCDB.mdb

Fixed Load Spectrum and Operator Request where the directory name was incorrect when processing a file name with a full path.

Reset WorkflowStatus and ReadToRun when no workflow is selected. Make sure that the workflow name is set after the path is set. Handle the case where there is a duplicate workflow name in two different paths. Initially get the path from the administrative settings.

The call to set gas cell Pathlength has been obsoleted. Use the new supported call.

Change the correlation to fail if the interferogram peak falls outside of the PeakRange. Add diagnostics (written to CoaddErrors.txt) to indicate when there are bad scans during a data collect. Many of the failures will be generated when the interferogram falls outside the peak range or when correlation fails.

Set a seven second delay on any beam path change.

The Unscrambler predict would fail if some obscure parameter was not present. Ignore these occurrences and continue predicting.

Add the path where the Unscrambler X Engine version 10.5.0 is found. This path cannot be found in the registry or any other location on my computer. It must be hand loaded.

Report file (.htm file) can be signed twice when the policy of “double signature” is allowed with security or when security is not installed. Double signatures are displayed properly on “Check Signature” dialog.

Correct an issue with TQ Analyst that caused a conflict with Thermo Client 1.8 (or earlier). TQ Analyst, version 9.8 added to the DVD.

History: This is fixed in RESULT 3 SP12 hot fix 2.

Update/correct values expected answer in text for PCR-R, Distance Match-D, RMS Noise, Peak-to-Peak Noise, Single Beam 1%, Single Beam 2%, Single Beam 5%, Peak Width High Location, Location Low Location, Location High Location, Data Range (in Composite Calculation Test D).

History: This is fixed in ValPro 3 SP12 hot fix 1.

Sign the user workflows “EP Wavelength Repeatability.wfl” and “MX_EP Wavelength Repeatability.wfl”.

History: This is done in ValPro 3 SP12 hot fix 1.

If you launch RESULT Operation from OPC when security is installed, the Login dialog comes up on the instrument computer. However in OPC you can launch a workflow before the login dialog is accepted. This violates the login feature. Fixed in this hot fix.

History: This is a longstanding problem that is fixed in RESULT 3 SP12 hot fix 1.

When a workflow is selected and launched from OPC in RESULT Operation, the signature status on the user interface is not updated. A signed workflow is not shown as signed.

History: This is a longstanding problem that is fixed in RESULT 3 SP12 hot fix 1.

When the ValPro Qualification button is pressed in RESULT Operation, the workflow name is updated to match the ValPro workflow being run. However the signature status on the user interface does not update for the ValPro workflow. The workflow may not be shown as Signed.

History: This is a longstanding problem that is fixed in RESULT 3 SP12 hot fix 1.

A servo reset is required when the beam path is changed on an Antaris IGS instrument. Then need a delay to make sure that the reset scan does not occur while any (beam path) mirror is moving.

History: This is good practice and is fixed in RESULT 3 SP12 hot fix 1.

The fix is to remove the saturated peak check for SimpleOMNIC correlation. In this correlation is should be nearly impossible to reject a scan.

History: This is corrected in RESULT 3 SP12 hot fix 1.

Add support of Unscrambler 10.5 models and handle the 64 bit model case. Also turned off the Unscrambler bias and slope correction for old models.

History: This is fixed in RESULT 3 SP12 hot fix 1.

Corrected the NTE_BAD_KEY_STATE error in software. If the KEYSET if found to be bad, then delete it and create a new one.

History: This is fixed in RESULT 3 SP12 hot fix 1.

Correct problem when delay of zero is encountered. Actually use this value to enter a programmable delay. If zero, check for a text file named SetDelay.txt where the delay could be entered.

History: This is corrected and enhanced in RESULT 3 SP12 hot fix 1.

When a background only data collect event is used, grab the delay from the sample specification. In the past there was no way to set a delay for a background only collect.

History: This is fixed in RESULT 3 SP12 hot fix 1.

The only part of RESULT software that was not Windows® 10® compliant was running tutorials from the version of TQ Analyst software (v. 9 SP5) that was included with the release. This has now been addressed with the addition of TQ Analyst 9 SP7 to the RESULT software.

Update to Thermo Client version 1.8.

See the TQ Analyst 9.7 release notes for a listing of issues that might be important for RESULT software.

Put the number of seconds to delay before closing the Operation software into the second argument of the executable call for the ReStartRESULTOperation program. If only one parameter is used, then wait one second – which has always been the default.

If the Request event is used to enter an OPC value and the OPC server is not available, then pass a zero (0) as the expected value. This is done instead of exposing the request dialog that is shown when OPC is not being read. This allows automated analysis with OPC.

Update how the OPC variable RepeatCount is updated by making it zero based. When the repeat count is zero, no RESULTs should appear. After the last repeat, the repeat count is incremented one more time which can be used to show the last set of values in the OPC variables.

In the past the measure RESULTs for measurements 1 through 5 were shown. Since many more measurements may now be filled, changed the to measure RESULTs for measurements 1 through 4 and for measurements 77 through 80.

A special point type is defined for the Read IO and Write IO events. It is called “Embedded Number String Memory” and it is used to pass specially formatted numbers. For example the string “100F” might be passed and that will be interpreted as the number 100. This is used to report temperature values from a special Opto22 device.

Allow an option to save the values being written to the Trend display in RESULT Operation into a text file. This will only be done if there is an entry in RESULTSettings.ini in the group with the value “SaveToText=1”. The values are saved to a file named “TrendData yyyy-MM-dd HH-mm-ss.txt”. A new file is created if nothing has been written to the current text file for 30 minutes.

1. Add a floating point version of the current OPC long values Mode, RunningState, NumberWorkflowErrors and RepeatCount. New R4 version names are fMode, fRunningState, fNumberWorkflowErrors and fRepeatCount. 2. Add a long (I4) version of the values that are currently sent by OPC to the Request event. The old names in OPC are of the form InputField.FieldData. The new I4 names are of the form InputField.DataI4.

The spectrum collect correction called (S/B)/X is usually used to correct a spectrum where the background was collected on a different beampath than the sample. This equation now assumes that “X” is a ratioed spectrum. In the new feature, if “X” is actually a single beam, then this correction changes automatically to S/X. This means that the “X” single beam is assumed to be a background single beam collected on the same beampath. If “X” is a ratioed spectrum, then the equation (S/B/X is still calculated.

The ability to open and view CNC files (with associated SRS file) that have been created in the Series capability in Omnic software has been added to RESULT Data View. In Omnic series the CNC file usually has an index number added to the root SRS file name. This is handled in this new option.

If the background frequency is set to “Once for each workflow run”, you still will be required to collect a background with each sample. This happens in RESULT Operation, but not in RESULT Integration.

Workaround: The workaround for this issue is to go into RESULT Options and check the “Save audit trail to database” checkbox.

History: Problem created with RESULT 3 SP11. This is fixed in RESULT 3 SP12.

Despite the fact that the ValPro test passes, the condition on the front screen of RESULT Operation remains “Required” and not “Satisfied”. This may cause a user to be unable to run any production workflows.

Workaround: The workaround for this issue is to go into RESULT Options and check the “Save audit trail to database” checkbox.

History: Problem created with RESULT 3 SP11. This is fixed in RESULT 3 SP12.

The Quick Collect menu item – when selected - causes a crash in RESULT software. Caused by an invalid access of memory and fixed for this version.

History: Problem created with RESULT 3 SP11. This is fixed in RESULT 3 SP12.

The RunExe event has always required that a full pathname be included with the name of the program being executed. In this corrected version, if no pathname is specified, then the pathname of the workflow is added to the executable name.

History: This is fixed in RESULT 3 SP12.

Rather than failing when an incomplete data buffer is received on the first scan, set the data collect to try again to collect the first scan.

History: This is fixed in RESULT 3 SP12.

When you try to coadd single beams, there is no noise improvement in the RESULT. The single beam was not actually being coadded; only the latest scan was reported. Now perform the coadd and report that as the RESULT.

History: This is fixed in RESULT 3 SP12.

The “No expiration” option for Background Frequency allows you to collect a background in one workflow and use it in another or collect a background with one collect specification and use it with a different specification. The “No expiration” option is selected when you want to collect the spectrum that will use the common background.

History: This is fixed in RESULT 3 SP12.

The RESULT Options “Save audit trail to database” and “Launch OPC at startup” are new with the SP11 build. Thus there is no historical security policy to allow these to be set. However the options are grayed when Security Administration is running and therefore these options may not be changed. In the fixed version, the presence or absence of the policy for these items is checked and the items become available if necessary.

Workaround: If you reinstall the RESULT application into Security Administration, new policies will become present for these options. This is correct behavior.

History: This issue was created in RESULT 3 SP11 and is fixed in RESULT 3 SP12.

The quant RESULTs for Method title and Method file name are empty for a Search method – and actually for any classification method. This is now fixed and the correct method title and method file name are reported.

History: This issue was created with the release of RESULT 3 SP11. It is fixed in RESULT 3 SP12.

If a Measure event is supposed to return a Pass or Fail for an answer and the RESULT is not actually valid for this test, then do not return an empty string. Instead return a “N/A”.

History: This was fixed in RESULT 3 SP12.

Instead of requiring the full pathname for the program in RunExe, if the fullpath is not included, then replace it with the directory from which the workflow is being run. This simplifies RunExe setup.

History: This was fixed in RESULT 3 SP12.

The Instrument Check menu item in the Maintenance menu of RESULT Operation and Integration for the IGS does not display the three spectra that are included in the check. Only the third spectrum is displayed at the end of the command. This is now fixed and all three spectra are available.

History: This problem was created in SP11 and was fixed in RESULT 3 SP12.

When you run ThermoIQ and attempt to access the ValPro file information, ThermoIQ does not respond and it runs forever. This required a fix in the ValPro installer.

History: Problem created with RESULT 3 SP11. This is fixed in ValPro 3 SP12.

RESULT software is supported on Windows® 8.1® and Windows® 10®.

See the TQ Analyst 9.5 release notes for a listing of new features that might be used in RESULT measurements and also for fixes to existing features. The TQ Analyst features are implemented in Spectrum.dll that is part of the RESULT release.

Additions were made to support the Antaris II DR model (Diffuse Reflectance). This model does not have a transmission detector in the sample compartment.

This scan rejection type is already implemented for RESULT IGS. With this option a scan will rarely, if ever, be rejected. A scan will be rejected if an incomplete scan – not enough data points – returns from the instrument, but otherwise it will add the scan. This is implemented for the transmission collect, the integrating sphere collect, the fiber optic collect and the multi-channel collect.

RESULT.mdb, which can be used to store values and answers in RESULT Operation, has a finite size and with some customers has filled up and caused problems. The only solution was to manually archive the old file and create a new file. In this new implementation when the data base reaches 80% of its maximum size, a signal is sent to archive the current data base and create a new one. This operation will wait and only occur the next time that the computer is rebooted. Still to be addressed is automatically searching and accessing all of the archived data bases as well as the current version of RESULT.mdb.

This ability will be available The instrument values are read when the composite component “InstrumentDiags” is first called for a spectrum.

Add the ability to save an audit trail to the RESULT data base in RESULT Operation.

Add the ability to automatically start the RESULT OPC server when RESULT Operation is started.

Add the ability to automatically start a RESULT workflow when RESULT Operation software is started. It does this by looking for a file called “LaunchWorkflowAtStartUp.txt” in the RESULT Data directory.

Add an ability that will never terminate the loop in the Repeat event. If the number of repetitions is set to -1, then the loop will never terminate.

Add an OPC value that will track the count of an unnested Repeat event.

In a recent version the behavior of the Report to File output was changed. After each answer was reported, the line was terminated with a CRLF. This caused a problem in some old workflows where a tab was expected. A registry item was added to revert to separating with a tab always. The registry key is “TabAlways” under RESULT. If set to one, then the tab replaces the end of line indication.

History: Problem created in RESULT 3 SP6. This is improved in RESULT 3 SP11.

You can choose to display the answers by index or by time on the Trend Tab. However if you selected the Time option, it caused a crash of the software. This was caused by an out-of-range index in an array and it was fixed in this version.

History: Problem occurred in earlier versions of RESULT. This is corrected in RESULT 3 SP11.

There was the small chance of a conflict between displaying the trend chart graph and filling the trend array in the application. When this happened the system locked. This hole was fixed and the conflict avoided. As part of this change, the Setup and Refresh buttons on the Trend tab are disabled when a workflow is running.

History: Problem occurred in earlier versions of RESULT. This is corrected in RESULT 3 SP11.

The time that is shown in the table on the Trend Tab in RESULT Operation displays the GMT time followed by the GMT-x:xx label. It should show the local time. This was fixed in this version.

History: Problem occurred in earlier versions of RESULT. This is corrected in RESULT 3 SP11.

Thirty OPC items were allowed and this values was ultimately raised to 101. This number was selected for a particular application, but it should cover virtually any situation.

History: This was changed in RESULT 3 SP11.

There was an error in the Write to Excel (and Read from Excel) events when more than 26 columns were required. The translation between column number and Excel column symbol (an alpha string) was fixed and now operates correctly.

History: Problem existed in earlier versions of RESULT. This was fixed in RESULT 3 SP11.

All of the operations with the Pressure controller were dependent on the presence of a Temperature controller. This was changed to make the two controllers function independently. Also add the ability to read temperature or pressure values even if the event to set up the controllers is not part of the workflow.

History: Problem existed in earlier versions of RESULT. This was fixed in RESULT 3 SP11.

The Unscrambler assigns different default directories for their methods – based on the version of the Unscrambler. Added directories that will support Unscramber version 10.3 for both OLUP and OLUC.

History: This was fixed in RESULT 3 SP11.

This feature had only been added for IGS, but makes sense to have it for NIR too. This was added.

History: This was added in RESULT 3 SP11 to work the same as for RESULT IGS software.

The size of the security token buffer needed to be expanded since a customer had a problem when their local security buffer exceeded 8000 byes. The problem prevented them from logging into the system in a secure environment.

History: The size of the buffer has always been 8000, but it is a best idea to increase to 65535. This is corrected in RESULT 3 SP10 Hot Fix 1.

Add the Archive event to the events allowed under Collect Sequence. This allows individual sequence spectra to be saved.

In Report to OPC, allow the standard error or uncertainty to be reported. Thus the value and its uncertainty (error) may be reported.

Make sure that if the temperature and pressure are attached to the spectrum that these values are always used to quantify a sample spectrum.

History: Problem occurred in earlier versions of RESULT. This is corrected in RESULT 3 SP10.

USP35_BA_ValPro_Target_External.wfl was incorrect on the ValPro distribution media with SP9.

History: Problem introduced in SP9 and corrected in RESULT 3 SP10 (ValPro 3 SP10).

Add support for models developed with the Unscrambler X from CAMO. This requires that either OLUPX (for predictive models) or OLUCX (or classifier models) be installed. These are also CAMO products. Add support for Hotelling Q residual RESULTs and for inlier distance RESULTs for Unscrambler models.

Retain the aperture value for an Antaris IGS data collect. This value will be reported in the spectrum info when the spectrum is viewed from TQ Analyst.

Add the ability to select 4x the number sample scans for a background data collect.

Change the RESULT Operation default to not require the user to log on. Of course this is overridden if Thermo Security is turned on.

The Write to Excel event gives a variety of errors when it is used. The RESULTs are not dependable. The Excel file that is created does not always have the correct information saved into it. This was fixed and Write to Excel now works properly, but there are additional clean-ups that were done. Write to Excel only writes to a workbook with extension “.xlsm”. Excel is always closed at the end of the experiment (workflow). The ability to handle date output (VT_DATE) was added. It is no longer possible to have an invalid data format output to Excel.

History: Problem occurred in earlier versions of RESULT. This is corrected in RESULT 3 SP9.

If the background and sample are collected in the same beampath with the transmission accessory, then an error was reported. There should be no problem with this scenario. This problem was introduced when a different problem was fixed in the previous version of RESULT.

History: This problem was created in RESULT 3 SP8. It is corrected by RESULT 3 SP9.

There is a difference between the attribute label, which indicates that the peak width is measured at 40% of the peak maximum, and the comment at the bottom of the report, which indicates at 10% of peak maximum. The correct value, 40%, is changed in the comment text. The answer for the test, the actual peak width, is correct.

History: This problem was introduced in the last release of RESULT. This is corrected in RESULT 3 SP9.

All of the wavelength accuracy tests in RESULT for NIR have been changed to report in wavelength and to use the wavelength uncertainties specified in the USP. This means modified workflows and TQ Analyst methods to support the changes.

Under ValPro options there is a new selection called “USP Version’. A customer may choose to use the legacy USP tests or the latest version from USP 35.

The ability to attach up to four custom workflows to the ValPro sampling tests has been added. This feature is available from ValPro options. This is an enhancement to the previous software where is was possible to add one custom workflow.

Antaris Target systems are now supported on Microsoft Windows 7 32 bit.

Note: Antaris Target systems are not supported in Microsoft Windows 7 64 bit.

In TQ Analyst it is possible to indicate that a component is computed, but not reported. When this is done, that RESULT is not included when the RESULTs are reported. This indication was ignored by RESULT and the Measure event. This feature is now honored, but only for newly created workflows. Workflows created by previous versions of RESULT will continue to use all components whether or not they should be reported.

In a distance match method, the maximum deviation – as well as the proportion of data points that fall outside the specified limits – may be reported. The maximum deviation is now be available for reporting from the Report event.

Two new Correction methods are available to be used in the Collect event. The more important one allows a beam path correction spectrum to be specified that will be divided into the ratioed spectrum. This correction spectrum may be loaded as a transmittance or %T spectrum. These options are described when you select the Correction option.

If the limits for the pass/fail test are set in TQ Analyst, it is possible to selectively decide which answers will return with a pass or fail indication. If a TQ Analyst quantitative (or measurement only) method is set with the same value for the high and low limit, then no pass/fail indication will be returned and reported.

A third correlation type is made available. The new type is the same as the OMNIC Simple correlation. The difference between the RESULT Simple correlation and the OMNIC Simple correlation is that in the OMNIC version scans are never rejected. This may be useful if bad data collects are identified from a diagnostic calculated on the final spectrum produced by the data collection.

The instrument status information (information about the current state of the spectrometer) is attached to the current spectrum after it’s collected.

If the Measure event uses a TQ Analyst quantitative or measurement only method, then the answers from the measurement are attached to the spectrum. They may be viewed from the Information display in OMNIC.

“Combine Multiple Methods” TQ Analyst methods are supported from RESULT. At this point these can be difficult to create in TQ Analyst, but once a method is presented, it may be predicted. Among other things this allows a variety of Composite component values to be computed from multiple TQ Analyst quantitative and measurement only methods.

“Combine Multiple Methods” TQ Analyst methods support the use of Grams PLSplus/IQ methods. This permits the RESULTs of these methods to be used in Composite component value computations – more than are available from RESULT.

The Eject step is moved to the beginning of data collect setup. This is where it is expected. Changes made to effectively let the temperature stabilize before data collection.

History: Problem occurred in earlier versions of RESULT.

The use of a %T or %R spectrum with the “Transfer correction using scalar spectrum” or “Transfer correction using division by a scalar spectrum” produced a RESULT that was off by a factor of 100. You had to use a transmittance or reflectance spectrum. This is not the common scale for a ratioed spectrum. This is now automatically corrected to give the correction that is expected (not off by a factor of 100).

History: Problem occurred in earlier versions of RESULT .

There is a difference between the attribute label, which indicates that the peak width is measured at 40% of the peak maximum, and the comment at the bottom of the report, which indicates at 10% of peak maximum. The correct value, 40%, is changed in the comment text. The answer for the test, the actual peak width, is correct.

History: Problem occurred in earlier versions of ValPro .

For an IGS, restart the data collect when the first two scans do not correlate. Do not assume that the first scan must be correct.

History: Feature added to RESULT 3 SP7

In the Sample Specification for an IGS collect add a choice to allow the Correlation to be set and allow a setting to handle Rumble (apparent vibration of the sample).

History: Feature added to RESULT 3 SP7

Generate meaningful messages when a data collection fails. This replaces the ‘Bad Scan’ message which might occur for several reasons.

History: Feature added to RESULT 3 SP7

Allow the ability to archive bad scans during data collection. This is not the default behavior, but may be turned on in a diagnostic mode.

History: Feature added to RESULT 3 SP7

When an error occurs during a loop event, display the iteration number, but also the time of that the problem occurred.

History: Feature added to RESULT 3 SP7

A memory leak occurred with each read of a method in the Measure event. After many iterations this will causes a crash.

History: Problem created in RESULT version 3 SP6.

The temperature and pressure are not applied before measuring a spectrum in the Sequence event. However if the spectrum is measured after the fact, the RESULT is correct and consistent with the temperature and pressure.

History: Problem occurred in earlier versions of RESULT .

RESULT software is supported on Windows® 7® 64-bit with two exclusions (see Note below). We recommend that you launch setup.exe from your installation CD to perform the following operations: Remove Application, Modify Installation and Repair Installation. If you initiate these actions from Programs and Features, you risk receiving multiple messages about installing/uninstalling each application or add-in option.

Note: Antaris Target systems are not supported with Microsoft Vista or Microsoft Windows 7 including both 32-bit and 64-bit; also, the Pirouette application is not Vista or Windows 7 compatible.

History: Feature added to RESULT 3 SP6

RESULT CD installer has a new front page dialog. On the dialog there are three installation options: RESULT Software or RESULT IGS Software, Release Notes and TQ Tutorial Module. Under the button for “TQ Tutorial Module”, there is a note of “Required TQ Tutorial Module Installation”.

History: Feature added to RESULT 3 SP6

TQ tutorials are updated with the new version of ToolBook from SumTotal. Due to some conflicts of versioning between new ToolBook and RESULT, the installation of this module cannot be incorporated into RESULT module installations, and it has to be manually installed from RESULT installer front page. The installation of this TQ Tutorial Module is required for proper functioning of TQ Analyst.

History: Feature added to RESULT 3 SP6

All the RESULT user guide PDF files are updated. The following are major areas of updates:

History: Feature added to Result 3 SP6

ValPro workflow for Integrating sphere qualification using external standards is updated to use dark corrected standards.

Note:

History: Feature added to Result 3 SP6

RESULT software now reports the Hotelling T2, Hotelling T2 Limit and ResXValSamp values for prediction models developed in Unscrambler 9.8.  To perform on-line predictions in RESULT with Unscrambler models, you must have OLUP installed on the computer.  These new RESULTs can be displayed using the Report event in the RESULT software.

History:  Feature added in RESULT 3 SP6.

Protected Unscrambler method (.upp) files are a packaged (protected) private file format defined to run with a specific instrument or data from that instrument. When using the protected Unscrambler method for simulation, the method will only give RESULTs when the simulated .spa was collected from the same instrument as the protected Unscrambler method was specified for.  When collecting from an instrument, the method will only give RESULTs when the collecting instrument is the instrument specified for the protected Unscrambler method.

History: Feature added to RESULT 3 SP5.

The two checkboxes of “Clear all but most recent XX” for RESULTs and workflow errors are combined and replaced with a dropdown box of “Clear options”. There are three items in the options dropdown list: Clear all, Retain most recent and Clear most recent. “Clear all” is selected as default. The options dropdown box and the associated edit box are only enabled for clearing workflow RESULTs and workflow errors, and are disabled when clear background is selected.

History: Feature added to RESULT 3 SP5.

Two checkboxes are added to the Write to Excel editor: one for “Hide Excel run time window” and one for “Save Excel file automatically”. When “Hide Excel run time window” is checked, the Excel window will not be visible during workflow run. When “Save Excel file automatically” is checked, the Excel file specified in Write to Excel will be saved automatically with any new data.

History: Feature added to RESULT 3 SP5.

Count of workflow errors will be available to be reported out in Report to Text File, Write to Excel, and RESULT OPC Server. Also this value will be available to Logic Specification so that it can be used in Check, Perform If, and Perform While.

History: Feature added to RESULT 3 SP5.

In older version of RESULT, Repeat only generated workflow RESULT when “Use sampling sequence” was selected. Now, Repeat will always generate RESULT that can be used by other events. The RESULT that the Repeat event is made available for other events is:

History: Feature added to Result 3 SP5.

In the last release the (zero) offset for the autosampler could no longer be set properly. This prevented the proper centering of a sample.

History: Problem occurred in RESULT version 3 SP4.

ValPro was not available to be run from the RESULT Operation “ValPro” button on a USB IGS system with either the DTGS or MCT detectors. The workaround was to select the workflow as a custom workflow to be run.

History: Problem occurred in RESULT version 3 SP4.

The timeout for waiting for the sample spinner to rotate to the verify position is not necessarily long enough when using a large sample cup.

History: Problem occurred in earlier versions of RESULT.

This is technically correct behavior, but the RESULT should not issue an error. The new behavior is to return a zero for the standard deviation of one value. This will allow the value to be used without special first time logic

History: Problem occurred in earlier versions of RESULT.

RESULT crashes when Logged Archived long named HTML reports are retrieved in Operation. The problem was caused by limited memory allotted for file name, and it has been fixed.

History: Problem occurred in RESULT version 3 SP4 Tracking number: V&V22145

When we run Instrument Alignment twice in a row, RESULT will crash to the point that we have to restart the bench and the computer to get communications back up.

History: Problem occurred in RESULT version 3 SP4 Tracking number: V&V21735

RESULT software is supported on Windows® 7® with two exclusions (see Note below). We recommend that you launch setup.exe from your installation CD to perform the following operations: Remove Application, Modify Installation and Repair Installation. If you initiate these actions from Programs and Features, you risk receiving multiple messages about installing/uninstalling each application or add-in option.

Note: Antaris Target systems are not supported with Microsoft Vista or Microsoft Windows 7; also, the Pirouette application is not Vista or Windows 7 compatible. None of the products are supported in a 64 bit operating system.

History: Feature added to RESULT 3 SP4.

This RESULT version supports the new USB based Antaris IGS instrument. A new feature related to this is:

History: Feature added to Result 3 SP4.

Historically, especially during loop running, once an error occurs in one loop, every following loop will generate a separate error report. If running for a long time, eventually the forever increasing list of error reports will blow up the software. Now, RESULT will keep using one error report for each workflow running, and keep appending new errors to the report, but not generating new reports.

History: Feature added to RESULT 3 SP4.

A new radio button option and checkbox are added to Clear event to allow clearing of workflow errors.

History: Feature added to RESULT 3 SP4.

A new Preview button is added to the editor for user to preview the Excel datasheet with dummy RESULTs.

History: Feature added to RESULT 3 SP4.

RESULT Data Viewer allows merging of two sequence files into a new sequence file

History: Feature added to RESULT 3 SP 4.

A scan rejection setting has been added to the Integrating Sphere, Dual Integrating Sphere, Fiber probe and multichannel fiber probes sampling device setups. This allows the conventional collect, Normal, setting and the Limited setting for not rejecting scans for samples that change during collection.

History: Feature added to RESULT 3 SP4.

When Correction is setup in Collect event such that a background is not required, the software should skip the collection and saving of the background all together.

History: Problem occurred in RESULT version 3.0. Tracking number: V&V21113.

The delay, and sometimes missing report, problem caused by checking “Print HTML report after report is displayed” in Report event has been fixed.

History: Problem occurred in RESULT version 3.0. Customer reported issue.

Target Link Utility is not compatible with RESULT 3 SP3 or later versions of RESULT. Kinetics Demo is available from the Start Menu under Thermo RESULT. You can use this application to test your communications link with the Antaris Target, change between USB and wireless communication and specify the IP address of the Antaris Target that you want to communicate with. Detailed instructions for using Kinetics Demo are located at the end of this document.

Note: Antaris Target systems are not supported with Microsoft Vista; also, the Pirouette application is not Vista compatible.

History: Feature added to RESULT 3 SP3 hot fix 1.

If you try to uninstall RESULT CD, it will not fully uninstall all parts of the software.

Note: Installation of RESULT 3 SP3 Hot fix 1 will resolve this issue.

History: Problem occurs in RESULT 3 SP 3 and is fixed in RESULT 3 SP 3 Hot fix 1. Tracking number: V&V17497.

If you perform an align command on an Antaris Target, it will turn on the auto correction feature of the firmware. This can lead to potential problems due to a bug in the firmware. See firmware release notes above for details.

History: Problem occurs in RESULT 3 SP 3 with Antaris Target Firmware v1.7.6 and is fixed in RESULT 3 SP 3 HotFix 1. Tracking number: V&V17498.

When checking the position of the autosampler a timing error could intermittently provide incorrect data on the position of the autosampler. The software would then request the autosampler to move to an incorrect position based on the bad data. After the move the position was rechecked so an error would always be reported to the user and no data could be collected at the incorrect position. The timing on the DELL 960 computers intermittently exposed this problem.

History: Problem occurs in RESULT 3 SP 3 and is fixed in RESULT 3 SP 3 HotFix 1. Tracking number: V&V17499.

The instrument check command only produces the 100% line spectrum and not the single beam and interferogram spectra.

Recommendation: Check the single beam and interferogram performance with Quick Collect. Upgrade to RESULT 3 SP 3 Hot Fix 1.

History Problem occurs in RESULT 3 SP 3 and is fixed in RESULT 3 SP 3 HotFix 1. Tracking number: V&V17610.

The software allows you to set a custom spectral range on Antaris Target collect specifications, but then restores the default use standard range setting when you leave the settings window.

Recommendation: Upgrade to RESULT 3 SP 3 Hot Fix 1.

History Problem occurs in RESULT 3 SP 3 and is fixed in RESULT 3 SP 3 HotFix 1. Tracking number: V&V17611.

When requesting the validation wheel or attenuator wheel to move the command will occasionally be rejected by the instrument RESULTing in an error. This error is reported to the user and no data is collected at incorrect wheel positions.

Improvements: Changes were made to significantly reduce the frequency of this issue.

Recommendation: If you see this error, repeat your measurement.

History Problem occurs in RESULT 3 SP 3 and the frequency is significantly reduced in RESULT 3 SP 3 HotFix 1. _ Tracking number: V&V17500._

Without this in the path, the user gets a message about missing file UnscEMSCTrans.dll. This is true on both Windows XP and Windows Vista.

Workaround: Change the bench model in the Options dialog of RESULT Integration and RESULT Operation.

History: Problem occurred in all versions of RESULT. Added to release notes in December 2009. Tracking number: V&V17612

Without this in the path, the user gets a message about missing file UnscEMSCTrans.dll. This is true on both Windows XP and Windows Vista.

Workaround: OLUP requires c:\program files\olup (Unscrambler online predictor). OLUC requires c:\program files\oluc (Unscrambler online classifier). If you have OLUP installed, add the path to OLUP to the system path. If you have OLUC installed, add the path to OLUC to the system path. If you have both installed, add both paths to the system path.

History: Problem occurred in all versions of RESULT. Added to release notes in August 2009. Tracking number: V&V16958

RESULT software is supported on Windows® Vista® with two exclusions (see Note below). We recommend that you launch setup.exe from your installation CD to perform the following operations: Remove Application, Modify Installation and Repair Installation. If you initiate these actions from Programs and Features, you risk receiving multiple messages about installing/uninstalling each application or add-in option.

Note: Antaris Target systems are not supported with Microsoft Vista; also, the Pirouette application is not Vista compatible.

History: Feature added to RESULT 3 SP3.

Maintenance menu was only available in the RESULT Operation application. We added a Maintenance menu to RESULT Integration with a limited set of commands including: Test Sample, Test Background, Test Measurement, Instrument Status, Align Instrument and Instrument Check.

History: Feature added to RESULT 3 SP3.

We added the following features to the Archive event in RESULT Integration software:

· Added tips on how to set up folder locations properly below the Folder text box.

· When Report Archiving Information is selected in the Archive event, a new column labeled OPC Tag Index appears in the table. Use the column to specify the listing order of archiving information for the_ OPC server._

· Added Use Double Signature check box to File Format group. Feature is enabled only when Require Digital Signature check box is selected. At runtime, if Use Double Signature is selected, users must sign archived files twice.

· Added Append Other Text RESULTs check box and Setup button to File Name group. Clicking Setup displays a dialog for selecting text RESULTs generated by other Result events. All selected text RESULTs are used to form the file name for archived data_._

History: Feature added to Result 3 SP3.

We added a Get Input From OPC Client check box to the Request specification. When this check box is selected, an OPC Tag Index column appears in the table. This column defines which OPC tag (RESULT.Workflow.RequestInputEvent.InputField) each request item should read the data from at runtime.

History: Feature added to RESULT 3 SP3.

We added an Encoding Type drop down list box to the Report to Text File event. The list box provides two options for encoding text files created by this event: Unicode and ANSI.

History: Feature added to RESULT 3 SP3.

Added the following items to the list of events that can be used with a Collect Sequence event: Read from IO, Write to IO, Read from Excel and Write to Excel.

History: Feature added to RESULT 3 SP3.

Before, information like Operator Name, Date, and Instrument Serial Number could only be added to a report through a Report Header section. Now, a Report Header Item can be added to Report To Text File and Write To Excel events. The RESULT is not associated with any RESULT events.

History: Feature added to RESULT 3 SP3.

Write To Excel events can be used to report data generated by other RESULT events to an Excel spreadsheet. Also allows some math and statistical functions for floating point and integer data.

History: Feature added to RESULT 3 SP3.

Read From Excel events can be used to read data from a specific cell in an Excel spreadsheet. The data is then available for use by other RESULT events.

History: Feature added to RESULT 3 SP3.

Simulation collect is now enabled in both Collect and Collect Sequence events with Blend Analyzer Sample and Background specifications.

History: Feature added to RESULT 3 SP3.

This feature appears in the RESULT Options dialog box in RESULT Operation software and in the policy list for RESULT Operation in Security Administration software. When the feature is selected, RESULT Operation allows the user to run only workflows that are signed.

History: Feature added to RESULT 3 SP3.

This feature appears in the RESULT Options dialog box in RESULT Operation software and in the policy list for RESULT Operation in Security Administration software. When the feature is selected, RESULT Operation allows an OPC Client to select and run workflows that are not managed by RESULT Operation.

History: Feature added to RESULT 3 SP3.

In previous versions of RESULT software, the settings for Configure Standards were not saved. RESULT now uses .cfg files to save these settings. For RESULT Integration, the file name is RESULTIntegratorStandardOptions.cfg. For RESULT Operation, the file name is RESULTOperatorStandardOptions.cfg. Both files are saved in the following path: RESULT Data\Config\.

History: Feature added to RESULT 3 SP 3.

We added a Custom option to the Background Frequence drop down list box in the Collect, Collect Multi-Channel and Collect Dual Tablet events. When this option is selected, an Interval (min) edit box appears below Background Frequency. Use Interval to specify in minutes how often to collect a new background.

History: Feature added to RESULT 3 SP 3.

We removed the Valpro Installed checkbox from the RESULT Options dialog for RESULT Integration and RESULT Operation. At startup, both applications automatically check a registry key and Valpro file folder to determine whether Valpro is installed.

History: Feature added to RESULT 3 SP3.

The checkbox can be used to indicate that the Unscrambler method requires the spectrum to be reversed from high frequency to low frequency.

History: Feature added to RESULT 3 SP 3.

All specifications in the current workflow now appear in the Details view of RESULT Integration. Active specifications are listed in red text; inactive specifications are in black text.

History: Feature added to RESULT 3 SP3.

We added a Pre-Processing Filter column to the table in a Spectrum Item specification. Use it to define the type of pre-processing prior to display. The drop down list is populated according to the TQ Analyst method defined in the corresponding Measure event.

History: Feature added to RESULT 3 SP3.

The Optimize Gain button is now enabled and implemented for Autosampler Tablet specifications and Autosampler SoftGel specifications.

History: Feature added to RESULT 3 SP3.

We added a Perform System Alignment Before ValPro Test check box to the Valpro Options dialog box in RESULT Operation. When this checkbox is selected, the system will automatically perform a system alignment before it runs a ValPro test. If the alignment fails, an error message appears and the ValPro test will not run.

History: Feature added to RESULT 3 SP3.

RESULT now allows users to open multiple instances of RESULT Integration but only one instance of RESULT Operation.

History: Feature added to RESULT 3 SP3.

RESULT now records the sample temperature in the spectrum header.

History: Feature added to RESULT 3 SP3.

The Report To Spectrum event now works the same way with spectrum (.SPA) and sequence (.CNC) data files. This allows you to stamp sequence data files with information from a Request event (e.g., batch number, material name, etc.) like you can spectral files. The stamped information appears above the existing header section of a .CNC file. The CNC file can be opened through notepad or Excel.

History: Feature added to RESULT 3 SP3.

We added the following tags to the RESULT OPC Server:

· RESULT.BenchStatus: Corresponds to the Instrument Status in RESULT Operation. If the Instrument Status is a green check mark_, the tag will be turned ON; if Instrument Status is a red X, the tag will be turned OFF._

· RESULT.HMILockoutStatus: This tag works with RESULT Operation only. When the tag is turned ON, all the menus and buttons in RESULT Operation will be disabled and only the __OPC client can select, start and stop a workflow.

· RESULT.Workflow.RunContinuously: When this tag is turned ON, RESULT automatically restarts_ the workflow after it finishes running._

Message box functions: These tags allow message boxes answerable by an OPC client.

· RESULT.Workflow.MessageBoxStatus

· RESULT.Workflow.MessageBoxCaption

· RESULT.Workflow.MessageBoxText

· RESULT.Workflow.MessageBoxOKYesButton

· RESULT.Workflow.MessageBoxNoButton

· RESULT.Workflow.MessageBoxCancelButton

Operator Request dialog runtime functions: These tags allow prompts for repeat and other operator requests answerable by an OPC client.

· RESULT.Worflow.OperatorRequest.NumberRequests

· RESULT.Worflow.OperatorRequest.AcceptButtonStatus

· RESULT.Worflow.OperatorRequest.ResetButtonStatus

· RESULT.Worflow.OperatorRequest.LoadFromOPC

· RESULT.Worflow.Opera__torRequest.Request01.Question

· RESULT.Worflow.OperatorRequest.Request01.Answer

· RESULT.Worflow.OperatorRequest.Request01.DataType

· RESULT.Worflow.OperatorRequest.Request01.Required

Calculate RESULTs from Report to OPC: Calculate RESULTs can now be added to Report to OPC event.

· RESULT.Worflow.CalculateEvent.NumberCalculateRESULTs

· RESULT.Worflow.CalculateEvent.ReportToOPCEventName

· RESULT.Worflow.CalculateEvent.Calculate01.AttributeName

· RESULT.Worflow.CalculateEvent.Calculate01.DataRESULT

· RESULT.Worflow.CalculateEvent.Calculate01.DataType

· RESULT.Worflow.CalculateEvent.Calcualte01.CalculateEventName

History: Feature added to Result 3 SP3.

We added two checkboxes to the Transmission Module sample specification: Eject Holder Before Collect and Eject Holder After Collect.

History: Feature added to RESULT 3 SP3.

We added a real-time Cell Temperature status to the workflow status window (it appears in the lower left corner of the Run Time Test window in RESULT Integration and in the main window of RESULT Operation). The status information appears each time a Collect event executes.

History: Feature added to RESULT 3 SP3.

The JCAMP-DX format supports a subset of the data collection parameters that are available for a Thermo spectrum file. It adds many of the remaining parameters into the COMMENTS field when you write a JCAMP-DX file. It also adds the ability to interpret these values when a JCAMP-DX file is read.

History:  Feature added to RESULT 3 SP3.

The information from a Report to Spectrum event will be written to a JCAMP-DX file in the COMMENTS section. In the JCAMP-DX spectrum each RESULT will be on a single line preceded by “!!” and then the name of the value followed by a “:”.

History:  Feature added to RESULT 3 SP3.

Spectral files collected in RESULT and saved with the date/time in the file name were labeled inconsistently depending on the clock setting in Windows. A new time stamp format has been implemented throughout RESULT. The format is:

yyyy-mm-dd hhmmss GMT+/-hhmm

History: Problem occurred in RESULT version 3.0. Added to release notes in August 2009. Tracking number: V&V16509

The date that showed up in the Measure Method Summary in Header table in the Report event was 1 month too old.

History: Problem occurred in all of versions of RESULT. Added to release notes in August 2009. Tracking number: V&V15020

RESULT did not properly add log entries to the Windows Event Viewer. RESULT now adds log entries to the Windows Event Viewer for user log on, log off and log on failed. This works in RESULT Integration and RESULT Operation.

History: Problem occurred in RESULT version 3.0. Added to release notes in August 2009. Tracking number: V&V13320

The text file generated by a Report To Text File event could not open cleanly in WordPad and the file contained some junk characters. The text file opened normally in Notepad. The problem was caused by an ambiguous encoding type when the file is created by RESULT. RESULT now allows you to select the encoding type (ANSI or UNICODE) in the Report to Text File event. The default setting is UNICODE.

History: Problem occurred in RESULT version 3.0. Added to release notes in August 2009. Tracking number: V&V16006

If a workflow contained a Read from IO event, the value reported out immediately after this event was correct. But, if the workflow then used the value in a Measure event and reported it again, the value become 0.

History: Problem occurred in RESULT 3.0. Added to release notes in August 2009. Tracking number: V&V16820

One specific workflow in question has 3 components that are measured twice, and then a Calculate event is used to do some statistics. In Calculate, “Store raw values with calculated values” is checked. Then, a Report is used to display the measured values and statistics of the Calculate. In the final generated HTML report, only the first component correctly gives the two measured values, the average and other statistics. The other components give incorrect measured values and statistics. WE corrected this in the Calculate event.

History: Problem occurred in RESULT 3.0. Added to release notes in August 2009. Tracking number: V&V15158

When saving a file to a folder in Archive, if the folder doesn’t exist, RESULT Integration will automatically create the folder and the file is saved correctly. But in RESULT Operation, it generates an error the first time you run it. Additionally, in RESULT Operation, if the file has not been created, it not only creates the file, it creates an additional file without the first character. The fix is in Archive event.

History: Problem occurred in RESULT 3.0. Added to release notes in August 2009. Tracking number: V&V16820

In RESULT Data View, when a user opens one sequence file and then saves them all as .SPA files, this works fine. But if they do this again with another sequence file, the operation fails (the spectra files from the 2nd sequence file do not save to the selected directory and it does not use the typed-in base name). Instead the spectra from the 2nd sequence are saved into the folder that contains the spectra files from the 1st sequence file and uses the same filenames and overwrites the spectra from the 1st sequence.

History: Problem occurred in RESULT 3.0. Added to release notes in August 2009. Tracking number: V&V16133

If you try to uninstall RESULT CD, it will not fully uninstall all parts of the software.

Recommendation: Perform an over install if you just want to reinstall RESULT 3 SP3. You must use the Microsoft Uninstall utility to fully remove the software from the PC.

History: Problem occurs in RESULT 3 SP 3 and is fixed in RESULT 3 SP 3 HotFix 1. Tracking number: V&V17497.

If you perform an align command on an Antaris Target, it will turn on the auto correction feature of the firmware. This can lead to potential problems due to a bug in the firmware. See firmware release notes above for details.

Recommendation: Do not use the align command on an Antaris Target. Turn off the “Automatically align before running ValPro” option in the ValPro options dialog (this is off by default). The Align command performs a manual calibration of the Target. This operation is only required every 6-9 months. Upgrade to RESULT 3 SP 3 Hotfix 1 so preventive maintenance alignments can be performed. If upgrade is not feasible, work with your field service engineer who can perform this maintenance procedure with field service utilities and RESULT 3 SP 3.

History: Problem occurs in RESULT 3 SP 3 with Antaris Target Firmware v1.7.6 and is fixed in RESULT 3 SP 3 HotFix 1. Tracking number: V&V17498.

When checking the position of the autosampler a timing error could intermittently provide incorrect data on the position of the autosampler. The software would then request the autosampler to move to an incorrect position based on the bad data. After the move the position was rechecked so an error would always be reported to the user and no data could be collected at the incorrect position. The timing on the DELL 960 computers intermittently exposed this problem.

Recommendation: If you see this error, repeat your measurement.

History: Problem occurs in RESULT 3 SP 3 and is fixed in RESULT 3 SP 3 HotFix 1. Tracking number: V&V17499.

When requesting the validation wheel or attenuator wheel to move the command will occasionally be rejected by the instrument RESULTing in an error. This error is reported to the user and no data is collected at incorrect wheel positions. The timing on the DELL 960 computers intermittently exposed this problem.

Recommendation: If you see this error, repeat your measurement.

History Problem occurs in RESULT 3 SP 3 and the frequency is significantly reduced in RESULT 3 SP 3 HotFix 1. Tracking number: V&V17500.

The instrument check command only produces the 100% line spectrum and not the single beam and interferogram spectra.

Recommendation: Check the single beam and interferogram performance with Quick Collect. Upgrade to RESULT 3 SP 3 Hot Fix 1.

History Problem occurs in RESULT 3 SP 3 and is fixed in RESULT 3 SP 3 HotFix 1. Tracking number: V&V17610

The software allows you to set a custom spectral range on Antaris Target collect specifications, but then restores the default use standard range setting when you leave the settings window.

Recommendation: Upgrade to RESULT 3 SP 3 Hot Fix 1.

History Problem occurs in RESULT 3 SP 3 and is fixed in RESULT 3 SP 3 HotFix 1. Tracking number: V&V17611

Without this in the path, the user gets a message about missing file UnscEMSCTrans.dll. This is true on both Windows XP and Windows Vista.

Workaround: OLUP requires c:\program files\olup (Unscrambler online predictor). OLUC requires c:\program files\oluc (Unscrambler online classifier). If you have OLUP installed, add the path to OLUP to the system path. If you have OLUC installed, add the path to OLUC to the system path. If you have both installed, add both paths to the system path.

History: Problem occurred in all versions of RESULT. Added to release notes in August 2009. Tracking number: V&V16958

A prompt for Gain will appear on Antaris MX or EX spectrometers on channels 1-4. The initial setting for gain in the prompt should be used if the fiber optic shunt is connected. A gain of 1 should be used if the SabIR Probe is connected. If other custom probes are connected, use the gain appropriate for the probe attached to the channel.

History: Feature added to RESULT version 3.0 Service Pack B.

The Process event is now available for use in a Collect Sequence event group.

History: Feature added to RESULT version 3.0 Service Pack B.

Add support for Retain All Spectra from Collect Sequence.

History: Feature added to RESULT version 3.0 Service Pack B.

The current state of the file signature is displayed when you open a workflow.

History: Feature added to RESULT version 3.0 Service Pack B.

For a classification Measure method, it is now possible to report the Class Name from the Report to Text event.

History: Feature added to RESULT version 3.0 Service Pack B.

Add the lower acceptance limit and the upper acceptance limit as values that may be reported about a TQ Analyst quantitative method.

History: Feature added to RESULT version 3.0 Service Pack B.

Add support for the MX Plus Automated Tablet Sample Handler.

History: Feature added to RESULT version 3.0 Service Pack B.

On some networks, a measure event may hang when the workflow is running if the measure event uses a classification method stored on a network drive.

Recommendation: Place the workflow and method on a local drive.

History: Problem occurred in RESULT version 3.0. Added to release notes in November 2007. Tracking number: V&V3066

Spectra created on a different instrument do not have the controls that are present on an Antaris instrument. Thus data spacing and spectral endpoints may not be compatible with data collected on an Antaris. This may cause an incompatibility between a PLSpls/IQ model and an Antaris spectrum. The solution is to adjust the Antaris spectrum to be compatible with the PLSplus/IQ model.

History: Problem occurred in all versions of RESULT. Added to release notes in February 2008.

The Antaris autosampler may return to a position off by a step or two depending on the distance and direction of approach to a target position. Hysteresis correction was activated for the movement.

History: Problem occurred in all versions of RESULT. Added to release notes in April 2008.

The time delay for waiting for the autosampler was not long enough. The delay was increased to insure that the autosampler will be able to reach the Home position.

History: Problem occurred in all versions of RESULT. Added to release notes in April 2008.

The channel and gain settings were coordinated for the Instrument Check command for an Antaris MX instrument.

History: Problem occurred in RESULT version 3.0. Added to release notes in April 2008.

The Unscrambler OMNIC UDI dll assumes that the spectral data are presented in descending spectral order. The RESULT Unscrambler option assumes that the spectral data are presented in ascending spectral order. Thus the two packages do not give the same RESULT. A registry key “CAMOReverseSpectrum” is provided so that when it is set it forces the RESULT Unscramber option to reverse the order of the spectral data.

History: Problem occurred in RESULT version 3.0. Added to release notes in April 2008.

The variance spectrum for one spectrum is set to an all zero spectrum.

History: Problem occurred in RESULT version 3.0. Added to release notes in April 2008.

The data type is not set properly for all types of data when reading a data value on an Opto22 device.

History: Problem occurred in Result version 3.0. Added to release notes in April 2008_._

RESULT cannot access Pirouette method files that were saved as read-only.

Recommendation: Turn off the Read-Only property of your method file(s) and then rerun the workflow.

History: Describes operation in RESULT version 1.0-3.0B. Added to release notes in October 2007. Tracking number: V&V02733.

The following events are now available for use in a Collect Sequence event group: Measure events, Check events, Calculate events, Store events, Clear events and Write To IO events. Previously, only Measure events could be added to a Collect Sequence group.

History: Feature added to RESULT version 3.0 Service Pack A.

When using the Sequence tab to display trends in collected data, you can easily configure the software to display the data full scale in both the spectral pane and each component pane. To configure a workflow to display component data with the Y-axis scaled to fill the pane, select the Run Sequence event. For each component you want the software to autoscale, set both the Min Y Value and Max Y Value in the Component Display group to 0.00.

To configure a workflow to display spectral data with the X-axis automatically scaled to fill the pane, set both the Starting and Ending Spectrum X Values to 0.00. To autoscale the Y-axis of the spectral display, set both the Minimum and Maximum Spectrum Y Values to 0.00.

History: Feature added to RESULT version 3.0 Service Pack A

An option is now available on the Run Sequence event to restrict the data displayed on the Sequence tab to the most recent measurements.

History: Feature added to RESULT version 3.0 Service Pack A

An option is now available on the Run Sequence event to control whether the X axes for the component panes are displayed in units of time or data points.

History: Feature added to RESULT version 3.0 Service Pack A

The Collect Sequence event now has an option to associate a logic specification with the event. The logic specification can be used to stop the events in the Collect Sequence group when the logical condition is met.

History: Feature added to RESULT version 3.0 Service Pack A

The Collect Sequence event now supports the same set of corrections as the Collect event. For more information, see Correct Sample Spectrum and Correction Specifications in your RESULT User’s Guide.

History: Feature added to RESULT version 3.0 Service Pack A

RESULT Data View now supports additional display options, such as data point, scatter and line display and lets you select the data point markers.

History: Feature added to RESULT version 3.0 Service Pack A

When using the Trend tab to display trends in measured data, you can easily configure the software to display the data full scale in each component pane. To configure a workflow to display component data with the Y-axis scaled to fill the pane, select the Trend tab and choose Display Setup. (If you can’t open the Display Setup dialog box, ask your RESULT Administrator to give you access by opening the Manage User’s dialog box, selecting your name and selecting Access Trend Tab Setup Option.) For each component you want the software to autoscale, set both the Y Min and Y Max values in the Log Settings group to 0.00.

History: Feature added to RESULT version 3.0 Service Pack A

If the operating system’s program files directory is not named C:\Program Files, the ValPro algorithms test will fail because the workflow is not able to find key input files that are installed in the RESULT\ValPro subdirectory of the system’s program files directory. This can occur on some international versions of Windows.

Recommendation: Create the following directory on the computer: C:\Program Files{subject}\ValPro. Copy the following files from the RESULT\ValPro directory under your Operating System program files directory to the directory you just created:

TQInputY.txt

TQInputZ.txt

IS Bkg.spa

TxTransVsFiber.spa

History: Problem occurred in RESULT version 3.0. Added to release notes in November 2006. Tracking number: V&V9545

The Dual Tablet event does not support the autosampler specifications for automating sample handling. This restricts some of the background handling options that are available when automating sample handling.

Recommendation: Use the Position Autosampler event to automate sample handling. If you wish to collect a background from the reference position at the start of your tray of samples, add a Position Autosampler event before your loop that moves to the background position and set your background handling to Once Per Workflow Run.

History: Problem occurred in RESULT version 3.0. Added to release notes in November 2006. Tracking number: V&V9451 and V&V9452

The size of the security token buffer needed to be expanded since a customer had a problem when their local security buffer exceeded 8000 byes. The problem prevented them from logging into the system in a secure environment.

History: The size of the buffer has always been 8000, but it is a best idea to increase to 65535. This is corrected in RESULT 3 SP10 Hot Fix 1, but a version for RESULT 3.0 was also done. This change does NOT exist in any version of RESULT software between RESULT 3.0 and RESULT 3 SP10 HF1. The only upgrade path that includes this change is to jump directly to the service pack 10 hot fix. If you attempt to load this version of software over the top of an existing version of software, then it will appear that you have to install the software two times. The first install will remove the previous version and the second install will actually load the new version of RESULT 3.0 Hot Fix 1.

Special installation instructions: If you attempt to load this version of software over the top of an existing version of software, then it will appear that you have to install the software two times. The first “install” will remove (delete) the previous version and the second install will actually load the new version of RESULT 3.0 Hot Fix 1.

RESULT now supports the Antaris II, Antaris MX, Antaris EX and Antaris Target Blend Analyzer along with the Antaris NIR, Antaris IGS and Antaris Multiplexer.

History: Feature added to RESULT version 3.0.

This event allows information from workflow events to be appended to a text file.

History: Feature added to RESULT version 3.0.

This event allows information from workflow events to be read from digital or analog I/O lines.

History: Feature added to RESULT version 3.0.

This event allows information from workflow events to be written to digital or analog I/O lines.

History: Feature added to RESULT version 3.0.

This event allows a spectrum to be loaded into a workflow from a computer disk so the spectrum can be used by other workflow events such as a Measure event.

History: Feature added to RESULT version 3.0.

This event allows simultaneous collection of transmission and reflection sample data using an Antaris II spectrometer with a tablet analyzer…​

History: Feature added to RESULT version 3.0.

This event allows simultaneous collection from multiple fiber optic channels using an Antaris MX or Antaris EX.

History: Feature added to RESULT version 3.0.

All collection events can now be linked to a correction specification. The correction specification can be used to define a sample correction. Typical sample corrections include dark background corrections, transfer corrections, and spectral processing with a background spectrum stored in a spectral file.

History: Feature added to RESULT version 3.0.

On an Antaris or Antaris II system, backgrounds can now be collected from the transmission or integrating sphere beam path in addition to the fiber optic beam path. Typically, a background from an alternative beam path would be used in conjunction with a transfer correction (see “Collection events now support sample corrections” above). The transfer correction allows background collection at a convenient location while maintaining spectral quality by removing artifacts from the final spectrum that are due solely to the alternative beam path used for the background collection.

History: Feature added to RESULT version 3.0.

The header information from a collection RESULT (spectrum) can now be added to other events or specifications such as a table item specification for a sample report. The spectral header information includes key header attributes such as the spectrum title, the date and time of collection and the resolution. The spectrum file name is also available if the spectrum has been archived before the spectral header information is used by another event in the workflow.

History: Feature added to RESULT version 3.0.

The composite measurement specification can be used to produce calculated RESULTs using RESULTs from other events. The composite measurement specification supports a large number of mathematical operators (e.g., + Add, - Subtract) and functions (e.g., AVG Average, MAX Maximum) to use for creating calculated RESULTs.

History: Feature added to RESULT version 3.0.

The calculate event supports the addition of first and second derivative measurements.

History: Feature added to RESULT version 3.0.

Both RESULT Integration and RESULT Operation provide support for running workflows continuously. The feature is available in the Run Time Test window of RESULT Integration and in the Manage Workflows dialog box in RESULT Operation.

History: Feature added to RESULT version 3.0.

The Table and Summary Item Specifications support a Preview Section button. This button shows a preview of the current layout for the selected section in the report without having to run the workflow. Similarly, the Report Item Specification includes a Preview Report button which shows the formatting for all the sections in the current report.

History: Feature added to RESULT version 3.0.

The Table Item specification now supports additional text formatting control features such as text alignment, style and color. The specification also supports adding heading, cell, line and table breaks to the table to control the layout of cells within the table. The specification also supports an option for displaying all data types in the same row or column. In prior versions of RESULT, different data types were always displayed in different rows or columns.

History: Feature added to RESULT version 3.0.

The Summary Item specification now supports all the new formatting features of the Table Item specification plus filtering on a pass/fail condition or sorting on a field in the report. The filtering option can be used to produce a summary table that only includes pass or fail RESULTs. The filtering options also allow you to display and/or highlight individual pass or fail RESULTs. The sorting options include an option for placing duplicates in separate tables. This option can be used with classification RESULTs to place the members of different classes in different tables. This provides you with statistical information about the individual classes.

History: Feature added to RESULT version 3.0.

A setting has been added to the Perform-While event that forces the loop to execute at least once regardless of the state of the conditional test. This setting is useful when the value of the conditional test is initialized inside the Perform-While loop.

History: Feature added to RESULT version 3.0.

Sampling sequence files now support user defined columns. Information from the additional columns can be used by other events and specifications such as a Report To Spectrum event or Table Item specification.

History: Feature added to RESULT version 3.0.

Previously the Store event only supported RESULTs from Measure events. The Store event now supports RESULTs from other events. The Store event also supports the selection of individual values (data types or attributes) from a workflow RESULT. For example, you can select a specific component concentration value produced by a measure event without having to select all the component values produced by that event. In previous versions of RESULT, the Store event selected all the available values for a workflow RESULT.

History: Feature added to RESULT version 3.0.

Previously, the logical test specification supported entered values for high and low limits. Now the logical test specification supports entered values and values produced by other events in the workflow.

History: Feature added to RESULT version 3.0.

The Add To Spectrum event can be used to add information to the history of a spectrum. The information is stored in the spectral file header.

History: Feature added to RESULT version 3.0

Measure Method information can be added to a heading section in a sample report. This information displays key attributes such as the file name and revision number of all TQ Analyst methods included in the workflow.

History: Feature added to RESULT version 3.0.

The Trend tab is an optional tab in RESULT Operation. It can be used to display live or historical trend charts of stored measurements. Any measurement stored to the database by a Store event in a workflow can be viewed on the Trend tab. The Trend tab also supports tabular display of the measured values.

History: Feature added to RESULT version 3.0.

RESULT Integration and Operation can be configured to provide status information to an Opto22 I/O controller. This status information can be used to link status to digital output lines. For example a digital line can be configured to turn on whenever a workflow is running. These packages can also be configured to allow the Opto22 I/O controller to control workflows. Control features include starting workflows, stopping workflows, and acknowledging a Start or Stop prompt from a StartStop event. For example a digital input line can be configured to start a workflow.

History: Feature added to RESULT version 3.0.

If Thermo Client Services are installed and Thermo Security Admin Server (our security administration software) is installed and properly configured, basic user policies can be administered using Thermo Admin Server. Thermo Admin Server can run on the same computer as RESULT software or on a different computer on the same domain.

History: Feature added to RESULT version 3.0.

If the operating system’s program files directory is not named C:\Program Files, the ValPro algorithms test will fail because the workflow is not able to find key input files that are installed in the RESULT\ValPro subdirectory of the system’s program files directory. This can occur on some international versions of Windows.

Recommendation: Create the following directory on the computer: C:\Program Files{subject}\ValPro. Copy the following files from the RESULT\ValPro directory under your Operating System program files directory to the directory you just created:

TQInputY.txt

TQInputZ.txt

IS Bkg.spa

TxTransVsFiber.spa

History: Problem occurred in RESULT version 3.0. Added to release notes in November 2006. Tracking number: V&V9545

The Dual Tablet event does not support the autosampler specifications for automating sample handling. This restricts some of the background handling options that are available when automating sample handling.

Recommendation: Use the Position Autosampler event to automate sample handling. If you wish to collect a background from the reference position at the start of your tray of samples, add a Position Autosampler event before your loop that moves to the background position and set your background handling to Once Per Workflow Run.

History: Problem occurred in RESULT version 3.0. Added to release notes in November 2006. Tracking number: V&V9451 and V&V9452

RESULT software honors the local security policy for blank passwords. If the local security policy is set to disable blank passwords, RESULT will not allow a user to logon with a blank password even if that is the current setting for the user’s password.

Recommendation: Use the Local Security Policy application in the Administrative Tools folder within the Windows Control Panel to set the Local Policies Security Options For Accounts: Limit local Use Of Blank Passwords To Console Login Only to Disabled if you want to allow blank passwords…​

History: Describes operation in RESULT version 1.0-3.0. Added to release notes in June 2006 Tracking number: V&V4356.

RESULT software honors the local security policy for all accounts. If the Local Security Policy Network Access: Sharing And Security Model For Local Accounts is set to Guest Only – Local Accounts Authenticate As Guests, RESULT will not allow a user to logon even if the logged on user has a valid account and enters a valid password.

Recommendation: Use the Local Security Policy application in the Administrative Tools folder within the Windows Control Panel to set the Local Policies Security Options For Network Access: Sharing And Security Model For Local Accounts to Classic – Local Users Authenticate As Themselves, if you want to use local user accounts. Alternatively, require all users to use network logins when running RESULT software.

History: Describes operation in RESULT version 1.0-3.0. Added to release notes in June 2006. Tracking number: V&V4356.

RESULT software provides the user with access to an F-Ratio RESULT from PLSPlus/IQ methods and not an F-Test value. RESULT calculates the F-Ratio from the two values from the PLSPlus/IQ method, including the F-Test value.

Recommendation: Develop your reports and limit checks around the F-Ratio value.

History: Describes operation in RESULT version 1.0-3.0. Added to release notes in June 2006. Tracking number: V&V6953.

If you have a collect event set to collect a background every 4 hours or so, collect standards will still collect a background on the first standard you run with each Collect Standards command. This occurs because a new internal workflow is generated to support the collect standards command and this workflow doesn’t have the same identifier for the Background Frequency as the associated workflow. Because of this, the software can’t properly find an existing background. The background frequency will be honored for all standards run with the same Collect Standards command.

Recommendation: In RESULT Integration set up the sampling sequence using Configure Standards to run your standards as a set or keep pressing the Go button to collect all the standards in the set. In RESULT Operation, set up a sampling sequence using Configure Standards to run your standards as a set. If you do one of these things, you will only collect an additional background on your first standard.

History: Describes operation in RESULT version 1.0-3.0. Added to release notes in June 2006. Tracking number: V&V6953.

The Report To Text event writes characters using the UNICODE character set and not the ANSI character set. If you create a text file using a program such as Notepad using ANSI characters, the Unicode characters appended to the file by RESULT will have spaces between characters and additional non-printing characters may appear.

Recommendation: If you need to edit the file before RESULT appends data to the file, use Notepad to edit the file and then save the file using the UNICODE file type. To save the file using the UNICODE file type, use the Save As command in Notepad. If RESULT creates the text file, you may edit the file in Notepad and it will automatically be saved with the UNICODE type.

History: Describes operation in RESULT version 3.0. Added to release notes in June 2006. Tracking number: V&V8806.

If you select to Preview data collection from the Operator Prompt dialog, then the sample cup spinner will start spinning before the prompt is shown and the integrating sphere flag will open before the prompt is shown. This is done so that the data collect can be previewed under actual data collection conditions.

Recommendation: If you do not select Preview data collection form the Operator Prompt dialog, then the operator prompt will appear before the sample cup starts spinning or before the integrating sphere opens.

History: Describes operation in RESULT versions 2.1-3.0. Added to release notes in February 2005.

The Optimize Gain button on the sample specifications for the Autosampler – Tablet Transmission Module and for the Autosampler – SoftGel Transmission Module is grayed. This is done for a technical reason in the software.

Recommendation: The gain and screen setting may be determined by using the Quick Collect command. The Optimize Gain button on this dialog is not grayed and is available. Run the command and copy the gain and screen setting to the sample specifications.

History: Describes operation in RESULT versions 1.2 – 3.0. Added to release notes in June 2004. Tracking number: V&V04445.

Consider a workflow where five samples are run in a loop. During sample 2 there is an air bubble that causes a workflow error that states “interferogram peak too large.” However in the report the RESULTs from sample 1 are used for sample 2. There is no indication in the report that there was a problem with the second sample. The RESULTs for sample 2 are incorrect.

Recommendation: Add error status to the report so that the report indicates whether the workflow was error free at the time the report was generated.

History: Describes operation in RESULT versions 1.2 – 3.0. Added to release notes in June 2004. Tracking number: V&V03742.

At the end of a workflow the following error was reported: “Internet Explorer cannot open the Internet site file: C:{subject} Data\Images\report.htm. Operation aborted.” Clicking OK to this message generated the “Cannot find server or DNS error.”

Recommendation: RESULT software writes a temporary copy of the report to the file report.htm in the Images directory. This directory is typically C:{subject} Data\Images. The user must have write permission to this file in order to view reports as they are created by a RESULT workflow.

History: Describes operation in RESULT versions 1.2 – 3.0. Added to release notes in June 2004. Tracking number: V&V04040.

The operator is unable to view the contents of the service log.

Recommendation: In order to view any of the logs, the operator must have read access to the RESULT database (*.mdb) file.

History: Describes operation in RESULT versions 1.0 – 3.0. Added to release notes in June 2004. Tracking number: V&V03989.

Pirouette is open and then RESULT Integrator is opened. If you browse through a workflow with a Pirouette measure event, then you get a message that only one copy of Pirouette may be open at a time. RESULT Integration closes after the warning message.

Recommendation: This is a known feature of Pirouette. Close RESULT before running Pirouette and close Pirouette before running RESULT.

History: Describes operation in RESULT versions 1.0 – 3.0. Added to release notes in June 2004. Tracking number: V&V03535.

A RESULT user must have read/write privileges to the RESULT database file in order to properly add or view entries in the database.

Recommendation: Insure that all RESULT users have read/write privileges to the RESULT database. The file is typically located in c:{subject} Data\config and is named RESULT.mdb.

To check the file privileges using FAT32 file systems, right-click the database file in Windows Explorer. From the popup menu, select Properties. In the Properties dialog box, verify that the Read-Only check box is cleared.

On NTFS file systems, the file security properties are located on the Security tab, which some users may not be able to access. If your computer uses the NTFS file system, have your Windows administrator give you read/write privileges for the RESULT database folder and file.

History: Describes operation in RESULT versions 1.0 – 3.0. Added to release notes in May 2002. Tracking number: V&V03592.

A RESULT user must have read/write privileges to the RESULT database folder and file in order to view or change settings in the Configure System dialog box.

Recommendation: Have your Windows administrator give you read/write privileges for the RESULT database folder and file. The file is typically located in c:{subject} Data\config and is named RESULT.mdb.

History: Describes operation in RESULT versions 1.0 – 3.0. Added to release notes in May 2002. Tracking number: V&V03593.

You are operating a computer running the Windows NT operating system as a local workstation (network cable is unplugged), but it is configured for networking.

Recommendation: Configure the networking options on your computer according to the recommendations in Installing Your Software.

History: Describes operation in RESULT versions 1.0 – 3.0. Added to release notes in May 2002. Tracking number: V&V03594.

RESULT cannot access PLSplus/IQ method files that were saved as read-only.

Recommendation: Turn off the Read-Only property of your method file(s) and then rerun the workflow.

History: Describes operation in RESULT version 1.0-3.0. Added to release notes in October 2001. Tracking number: V&V02732.

A verification workflow must store a workflow status RESULT in the RESULT database. If your verification workflow does not store a passing workflow status RESULT, you will not be allowed to run the associated workflow.

Recommendation: At the end of your verification workflow, add a check event named “Workflow status” and link it to a logic specification defining the desired pass/fail condition. Make sure the check event has the Store Pass/Fail RESULT To Database check box selected and the logical test specification has the Logical Test Is Always False If Workflow Errors Have Been Detected check box selected. See “Check events” and “Logical test specifications” in the “RESULT Integration Software” section of your Antaris User’s Guide for more information.

History: Describes operation in RESULT version 1.0-3.0. Added to release notes in April 2001. Tracking number: V&V02204.

RESULT uses the same engine as Internet Explorer for displaying and printing reports. When you right-click on a graphic image, the software disables the Print option and enables menu items that are specific to graphic images.

Recommendation: To print a report displayed in RESULT software, right click on a portion of the report that doesn’t include a graphic image. Then select a print option from the popup menu.

History: Describes operation in RESULT version 1.0-3.0. Added to release notes in April 2001. Tracking number: V&V01920.

RESULT software uses the event logging services of the Windows operating system to track unauthorized attempts to log on to RESULT.

Recommendation: To configure RESULT to track unauthorized attempts to log on or to digitally sign files, configure the Windows event logging service to log unauthorized logon attempts. The event logging service works the same way in RESULT as it does in Windows. For example, you can configure Windows to disable a user account if that user makes too many invalid attempts to log on. The account will be disabled if the user attempts to log on to Windows or RESULT software. See “Windows security features” in the “Software Administration” section of your Antaris User’s Guide for more information.

History: Describes operation in RESULT version 1.0-3.0. Added to release notes in January 2001. Tracking number: V&V01603.

Baseline offsets occur when the operator uses different aperture settings to collect the sample and background spectra. When using the software’s default settings to collect transmission spectra using the three-position sample tube holder, the software measures background spectra through the center opening in the sample tube holder which does not have an aperture. If you install an aperture in the sample holder position used to measure a liquid sample, the RESULTing spectrum will have an offset baseline.

Recommendation: If you want to measure a liquid sample using an aperture, install an aperture in both the front and back positions of the sample tube holder and then place the sample tube in one of those positions (front is easiest). Set the Sample Position list box on the sample specification associated with your collection event to match the location of the sample (Front Sample Compartment or Rear Sample Compartment). Set the Position list box on the associated background specification to the other position (Front Sample Compartment or Rear Sample Compartment) and then run the workflow. See the “Sample specifications” and “Background specifications” chapters in the “RESULT Integration Software” section of your Antaris User’s Guide for more information about the Sample Position and Background Position parameters.

History: Describes operation in RESULT version 1.0-3.0. Added to release notes in January 2001. Tracking number: V&V01387.

The Collect Simulation Spectrum dialog box (displayed by choosing New Sample For Simulation on the sample specification) allows you to create or select the spectra that will be used for simulated runs of a workflow. The Collect Associated Background Spectrum check box in the Collect Simulation Spectrum dialog box specifies whether a new simulation sample spectrum will include a corresponding background spectrum. This is true whether you collect the simulation sample or select an existing spectral file. If Collect Associated Background Spectrum is selected and you select a simulation spectrum that contains only sample data such as a Single Beam or Interferogram file (by choosing From File in the Collect Simulation Spectrum dialog), when you close the dialog box, the software will not add the spectrum to the Samples For Simulation list box on the sample specification.

Recommendation: If you want to run the workflow in simulation mode using a sample spectrum and its corresponding background spectrum, select a spectral file that contains both a sample and a background interferogram. Most spectral files contain both a sample and a background interferogram. Spectra that are collected with Data Format (located on the collection event) set to Interferogram or Single Beam contain only a sample interferogram.

If you want to run the workflow in simulation mode using an interferogram or single-beam spectrum (Data Format is set to Interferogram or Single Beam), clear the Collect Associated Background Spectrum check box before selecting the simulation spectrum.

History: Describes operation in RESULT version 1.0-3.0. Added to release notes in January 2001. Tracking number: V&V01518.

RESULT Operation does not provide proper access privileges to users when the computer or domain name contains a space. Microsoft strongly discourages using spaces when entering computer and domain names in their Windows operating system because Windows does not handle the space correctly in all situations. The Windows operating system presents a warning after a user enters a computer name that contains a space.

Recommendation: Remove the space from your computer or domain name in Windows and then restart the RESULT Operation application. You should also remove any spaces from the user names defined in RESULT Operation software.

History: Problem occurs in RESULT version 1.0-3.0. Added to release notes in January 2001. Tracking number: V&V01566.

If you expand or collapse the items displayed in the workflow navigation frame in the RESULT Integration main window and then switch back and forth between the Workflow tab and the Details tab, the software does not retain the previous view. For example, if you select the Workflow tab, select Expand from the toolbar to expand the displayed workflow, switch to the Details tab, and then switch back to the Workflow tab (or vice versa), the view is no longer expanded. Choose Expand again to expand the displayed items.

History: Describes operation in RESULT version 1.0-3.0. Added to release notes in October 2000. Tracking number: V&V00690.

Some collection and measurement event parameters are interdependent. If you delete a collection event whose RESULT spectrum is used by a subsequent measurement event, and then create another collection event, add its RESULT spectrum to the measurement event and rerun the workflow, the workflow may produce a measurement error due to inconsistent parameter settings between the collection event and the measurement event or its associated TQ Analyst method.

Recommendation: Use the workflow error text to determine which parameters are inconsistent with the measurement event and then change the collection event parameters to fix the error.

Tip: The workflow wizard will automatically make your collection parameters consistent if you create a measurement event that uses an existing TQ Analyst method when you run the wizard.

History: Describes operation in RESULT version 1.0-3.0. Added to release notes in October 2000. Tracking number: V&V01060.

If you change a TQ Analyst method that is linked to a measurement specification in the current workflow, the measurement specification won’t reflect the change until you select another event or specification and then reselect the measurement specification. Let’s say, for example, you are running RESULT Integration and you select a measurement specification that is linked to a TQ Analyst quantitative method and decide to add another component to that method. Then you start TQ Analyst software, add the component and save the method. When you return to RESULT Integration, the new component doesn’t appear in the list of measurements on the measurement specification.

Recommendation: Select another item in the workflow navigation frame, such as the measurement event or another measurement specification, and then reselect the previous measurement specification.

History: Describes operation in RESULT version 1.0-3.0. Added to release notes in October 2000. Tracking number: V&V01044.

The software reports a fit value of 0.0 whenever the spectral range for the collection event doesn’t cover the full range of the standards in the associated TQ Analyst method (for example, when the spectral range on the sample specification is 4000 -10000 cm^-1 and the method standards range from 3800 – 12000 cm^-1). If your spectral range is set appropriately, you might see a low fit value but you are unlikely to see a fit value of 0.0, which is the lowest possible fit value. When the spectral ranges of the samples and standards are inconsistent, the software reports a fit value of 0.0 even for spectra that are very similar.

Recommendation: To achieve an appropriate reading for the fit value, change the spectral range for the collection event (located on its associated sample specification) to cover the full range of the standards. In the example above, you would need to change the spectral range for the collection event to 3800-12000 cm^-1.

History: Describes operation in RESULT version 1.0-3.0. Added to release notes in October 2000. Tracking number: V&V01214.

When you view Instrument Status under the Maintenance menu in RESULT Operation software, the start date displayed for the validation wheel is the date on which the wheel was calibrated; not the date it was installed.

Recommendation: Use the validation wheel installation date to determine when to re-qualify the validation wheel. That date is noted in the Validation Wheel Standard booklet provided at installation.

History: Describes operation in RESULT version 1.0-3.0. Added to release notes in January 2000. Tracking number: V&V01657.

The Build TQ Analyst Method command provides two buttons for defining the method standards: a Browse button and a Select button. The Browse button sets the directory and path that will be used to add standards to the new method; the Select button allows you to specify a base name for adding a group of standards to the method by selecting a representative spectral data file.

Recommendation: Make sure the path points to the same location as the spectral data file you select as your representative standard.

History: Describes operation in RESULT version 1.0-3.0. Added to release notes in October 2001. Tracking number: V&V02652.

After the OPC Server has been running for two to three hours, it stops producing data. This is confirmed by the fact that the Client shows Bad Data Values for all tags. Disconnecting and reconnecting to the OPC Server does not fix the problem. However after restarting the Client the communication is OK for another two to three hours.

History: Problem was reported in RESULT version 2.1B and was fixed in RESULT version 2.1C. Added to release notes in April 2006. Tracking number: CST07363.

During instrument setup, initializing the memories on the instrument causes occasional communication problems with the instrument.

History: Problem was reported in RESULT version 2.1B and early versions. Problem was fixed in RESULT version 2.1C. Added to release notes in April 2006.

When version 9.2 of the Unscrambler On-line Predictor and Classifier were released, it was not possible to open Unscrambler methods from those routines. It is now possible to open methods created in version 9.2 while continuing to support earlier versions of the On-line Predictor and Classifier.

History: Feature added to RESULT version 2.1B.

The class number for a QC Compare method when accessed from RESULT software is found in the library. In older versions of RESULT if the library was created from a non-classification method, then the class number was not in the library. In older versions the class number could not be updated from TQ Analyst. If this combination of events occurred, then an incorrect class number and class name were reported. The fix is to read the class number from the method and not from the library. In that case there are no possible conflicts.

History: Problem was reported in RESULT version 1.3A and may have been present in earlier versions. Problem was fixed in RESULT version 2.1B. Added to release notes in February 2006.

About once every month or two on a few systems, when RESULT Operation is run, the list of users is lost. The only alternative is to reenter the set of users.

History: Problem was reported in RESULT version 1.3A and may have been present in earlier versions. Problem was fixed in RESULT version 2.1B. Added to release notes in September 2005.

Rather than using the values assigned for the external linearity standards, the values for the validation wheel are being used. This causes the linearity test to report incorrect values.

History: Problem occurred in RESULT version 2.0. Problem was fixed in RESULT version 2.1B. Added to release notes in September 2005.

When a gas spectrum is collected on an Antaris IGS, the pressure value is saved in torr when it should be saved in hPa. When the spectrum is measured, the measurement assumes that the value is in hPa and therefore the incorrect answer is reported.

History: Problem occurred in RESULT version 2.0. Problem was fixed in RESULT version 2.1B. Added to release notes in September 2005.

The ideal gas law defines how changes in the temperature and pressure will affect how concentrations are reported. This correction was done backwards. That is, if the pressure value when the measurement is made is lower than the reference value, then the concentration should be increased to scale to the reference conditions. Instead in past versions, this would cause the concentration value to decrease.

History: Problem occurred in RESULT version 2.0. Problem was fixed in RESULT version 2.1B. Added to release notes in September 2005.

Using the Request item to enter multiple class values does not work properly. This feature is supposed to work with an automated loop of data collections to predict if classes match.

History: Problem occurred in RESULT version 2.1. Problem was fixed in RESULT version 2.1B. Added to release notes in September 2005.

Data collection on an Antaris with an autosampler sometimes fails during a multi-hour experiment.

History: Problem occurred in RESULT version 2.0. Problem was fixed in RESULT version 2.1B. Added to release notes in September 2005.

The number of ADC bits is not set properly for an Antaris NIR data collection. Several data collection values are set incorrectly and therefore assume default values. This is caused by an incorrect initialization step in the communication between RESULT software and the optical bench.

History: Problem occurred in RESULT version 2.0. Problem was fixed in RESULT version 2.1A. Added to release notes in January 2005.

The Algorithm Verification workflow that is run from ValPro fails when the regional settings are set to French or German. This is a decimal point separator problem in a text file that is used for two of the algorithm tests.

History: Problem occurred in RESULT version 2.0. Problem was fixed in RESULT version 2.1A. Added to release notes in February 2005.

If you have a workflow that performs a data collect with the sample cup spinning and there is a prompt before the sample is collected, then the sample cup starts spinning before the prompt is shown.

Comment: If you have selected Preview data collection in the operator prompt, then the sample cup will be spinning before the prompt is displayed. This is necessary in order to preview the appearance of the spectrum under actual data collection conditions_._

History: Problem occurred in Result version 2.0. Problem was fixed in Result version 2.1A. Added to release notes in February 2005.

Frequently you want to test a carousel load of samples to see if they belong to a particular class of compounds. However each sample in the carousel may belong to a different category. It is not possible to set up this experiment.

History: Problem occurred in all versions of RESULT. Problem was fixed in RESULT version 2.1A. Added to release notes in February 2005.

The Test Sample, Test Background and Test Measure menu commands in RESULT Operation produce an error when the collect is associated with an autosampler or with the multiplexer.

History: Problem occurred in earlier versions of RESULT. Problem was fixed in RESULT version 2.1A. Added to release notes in February 2005.

After an extended period of time running a workflow in RESULT Operation, the upper left corner of the Operation window displays spurious text.

History: Problem occurred in RESULT version 2.0. Problem was fixed in RESULT version 2.1A. Added to release notes in February 2005_._

For a qualitative (classification) TQ Analyst method, only the first RESULT is output to OPC. Subsequent expected values are not output to OPC.

History: Problem occurred in RESULT version 2.0. Problem was fixed in RESULT version 2.1A. Added to release notes in February 2005.

For certain situations if the autosampler motor stalls, the autosampler will continue to spin or it will no longer respond.

Comment: The problem that was fixed occurred when the autosampler was moving to the Home position.

Comment: After the stall is cleared, the autosampler performs a hardware command to find its zero position. If this step is stalled, then the motor will continue to run attempting to find its zero.

History: Problem occurred in RESULT version 2.0. Problem was fixed in RESULT version 2.1A. Added to release notes in February 2005.

If you select to Preview data collection from the Operator Prompt dialog, then the sample cup spinner will start spinning before the prompt is shown and the integrating sphere flag will open before the prompt is shown. This is done so that the data collect can be previewed under actual data collection conditions.

Recommendation: If you do not select Preview data collection form the Operator Prompt dialog, then the operator prompt will appear before the sample cup starts spinning or before the integrating sphere opens.

History: Describes operation in RESULT versions 2.1 and corrects a problem that was seen in RESULT 2.0. Added to release notes in February 2005.

About once every month or two on a few systems, when RESULT Operation is run, the list of users is lost. The only alternative is to reenter the set of users.

History: Problem was reported in RESULT version 1.3A and may have been present in earlier versions. Added to release notes in September 2005.

Rather than using the values assigned for the external linearity standards, the values for the validation wheel are being used. This causes the linearity test to report incorrect values.

History: Problem occurred in RESULT version 2.0. Added to release notes in September 2005.

When you press the Stop button produced by a Start/Stop event in a workflow created in RESULT 2.0, the software always generates a workflow error. In RESULT 2.1, a check box has been added to the Stop specification to allow the user to specify whether a workflow error should be generated when the Stop button is pressed.

History: Feature added to RESULT version 2.1. Request documented as tracking number ENH06204.

The time stamp for the OPC historical data interface is not initialized. As a RESULT, users cannot use the trend chart features in Iconic GraphWorx to view the component concentration data produced in RESULT software.

History: This problem was reported in RESULT version 2.0; it was resolved in RESULT version 2.1. Added to release notes in October 2004. Tracking number: V&V06104.

When using the RESULT Data View application, the software does not save the defined display settings for the displayed components.

History: This problem was reported in RESULT version 2.0; it was resolved in RESULT version 2.1 which includes features to assign a display settings file to a sequence data set. Added to release notes in October 2004. Tracking number: V&V06105.

When using the Save Sequence As feature in the RESULT Data View application, the software saves the data incorrectly.

History: This problem was reported in Result version 2.0; it was resolved in Result version 2.1. Added to release notes in October 2004. Tracking number: V&V06106(part 1)_._

When using the Result Data View application, the comparison of default component names with current component names is case sensitive.

History: This problem was reported in RESULT version 2.0; it was resolved in RESULT version 2.1. Added to release notes in October 2004. Tracking number: V&V06106(part 4).

When creating workflow reports in RESULT Integration software that include a Heading Item specification that is set up to add a date/time stamp (Current Date/Time) to the report heading, the software reports the time stamp incorrectly.

History: This problem was reported in RESULT version 2.0; it was resolved in RESULT version 2.1. Added to release notes in October 2004. Tracking number: V&V06107.

If you use Microsoft® Excel® to open a sequence concentration (*.cnc) file and then save the data as a text file, you cannot open the text file in the RESULT Data View application.

History: This problem was reported in RESULT version 2.0; it was resolved in RESULT version 2.1. Added to release notes in October 2004. Tracking number: V&V06108.

If you collect enough scans to cause the data collection buffer to overflow, the software saves the overflow but fails to use it when processing the data. This is not a problem if the number of scans is low enough that the data collection buffer does not overflow.

History: This problem was reported in RESULT version 1.3a, but was present in all previous versions; it was resolved in RESULT version 2.1. Added to release notes in October 2004. Tracking number: V&V06109.

When running RESULT Operation, the “In Progress” status bar sometimes causes the software to lock up, especially during sequence data collection.

History: This problem was reported in RESULT version 2.0; it was resolved in RESULT version 2.1. Added to release notes in October 2004. Tracking number: V&V06110.

When setting up a position autosampler event in a workflow in RESULT Integration, if you set Autosampler Position to Next Position In Sampling Sequence, reset to Prompt For Position Number and then select another event in the workflow, when you return to the position autosampler event, Autosampler Position is reset to Next Position In Sampling Sequence.

History: This problem was reported in RESULT version 2.0; it was resolved in RESULT version 2.1. Added to release notes in October 2004. Tracking number: V&V06111.

When setting up an archive event to save spectral data in RESULT Integration, if you select Add Spectrum Title, the software adds the spectrum title to the file name but the title includes the date and time which includes a colon (“:”). The colon causes the archive event to fail because it is not a legal character for a Windows file name.

History: This problem was reported in RESULT version 2.0; it was resolved in RESULT version 2.1. Added to release notes in October 2004. Tracking number: V&V06112.

When attaching a simulation spectrum to a workflow in RESULT Integration, the software does not allow you to use a single beam spectrum as a simulation sample.

History: This problem was reported in RESULT version 2.0 but has been present in older versions; it was resolved in RESULT version 2.1. Added to release notes in October 2004. Tracking number: V&V06114.

After changing the password in Windows XP, when you attempt to start RESULT Operation, you get the message 'The dwFlags parameter is CRYPT_NEWKEYSET, but the key container already exists'.

History: This problem was reported in RESULT version 1.3a; it was resolved in RESULT version 2.1. Added to release notes in October 2004. Tracking number: V&V06041.

If a RESULT workflow contains a collect event that is positioned in a loop and the loop is followed by a process event (to compute a mean spectrum) and then a measure event (to measure the mean spectrum), the workflow causes RESULT to quit if you use the workflow to collect standards.

Comment: A Collect Standards action no longer causes Result to quit, but this type of workflow still cannot be used to collect standards. Collect Standards accesses the collect event attached to a specific measure event. However, in this case the measure event is attached to a process event instead of a collect event.

History: This problem was reported in Result version 2.0; it was resolved in Result version 2.1. Added to release notes in October 2004. Tracking number: V&V06167.

If you restart the computer, start RESULT software and then run a workflow that contains a sequence or other data collection with a request event with the Preview Data Collect feature enabled, the preview window does not show a spectrum the first time you run the workflow.

History: This problem was reported in RESULT version 2.0; it was resolved in RESULT version 2.1. Added to release notes in October 2004. Tracking number: V&V06239.

If you open a workflow that was created in version 1.x of RESULT, you are unable to access the Start or Stop specification to configure the Start/Stop event.

History: This problem was reported in RESULT version 1.3a; it was resolved in RESULT version 2.1. Added to release notes in November 2004. Tracking number: V&V06244.

About once every month or two on a few systems, when RESULT Operation is run, the list of users is lost. The only alternative is to reenter the set of users.

History: Problem was reported in RESULT version 1.3A and may have been present in earlier versions. Added to release notes in September 2005.

Rather than using the values assigned for the external linearity standards, the values for the validation wheel are being used. This causes the linearity test to report incorrect values.

History: Problem occurred in RESULT version 2.0. Added to release notes in September 2005.

The number of ADC bits is not set properly for an Antaris NIR data collection. Several data collection values are set incorrectly and therefore assume default values. This may make it difficult to attain the expected signal-to-noise on the optical bench.

History: Problem occurred in RESULT version 2.1. Added to release notes in January 2005.

History: Problem occurred in RESULT version 2.0. Added to release notes in February 2005.

The Algorithm Verification workflow that is run from ValPro fails when the regional settings are set to French or German. This is a decimal point separator problem in a text file that is used for two of the algorithm tests.

History: Problem occurred in RESULT version 2.0. Added to release notes in February 2005.

History: Problem occurred in RESULT version 2.0. Added to release notes in February 2005.

An event is added to allow a prompt before a set of workflow steps is performed. This event also allows a set of workflow steps to be stopped by the person using the workflow before each of the steps have been completed.

History: Feature added to RESULT version 2.0.

This event allows information from workflow events to be added to the title or to the comments associated with the collected spectrum.

History: Feature added to RESULT version 2.0.

This event allows information from workflow events to be reported by the RESULT OPC Server to OPC clients. This event is only present when the OPC Add-in is installed.

History: Feature added to RESULT version 2.0.

This event allows you to collect, process and perform measurements on a series of spectra at regular intervals over a specified period of time. This event is only present when the Sequence Add-in is installed.

History: Feature added to RESULT version 2.0.

This event sets up the data collect used by a sequence event. The event can only be selected to be part of a sequence. This event is only present when the Sequence Add-in is installed.

History: Feature added to RESULT version 2.0.

This standalone program is installed by the Sequence Add-in. It allows for the post-analysis review and processing of the RESULTs of a sequence collect. This application is only present when the Sequence Add-in is installed.

History: Feature added to RESULT version 2.0.

This standalone program is useful to demonstrate the features of the RESULT OPC server. It may also be used to verify the information that is being provided by the server to OPC Clients. This application is only present when the RESULT OPC Test Client is installed is installed.

History: Feature added to RESULT version 2.0.

In addition to allowing the manual entry of prompted request information, this information may be read from a file. The file may be used to supply default values for the fields in which case the entries must be confirmed by the operator or the file may be used to configure the workflow so that no operator intervention is necessary.

History: Feature added to RESULT version 2.0.

Manual data entry of requested fields may be entered from a bar code. The field delimiter and the end of data option may be defined to optimize bar code input by the operator.

History: Feature added to RESULT version 2.0.

Request fields may be controlled and read from the OPC client. If set up in the client, this will automatically enter the request information. The OPC client can control whether operator confirmation of the request fields is required. This event is only present when the OPC Server Add-in is installed.

History: Feature added to RESULT version 2.0.

The three new options are Every 7 days, Every 30 days and No expiration.

History: Feature added to RESULT version 2.0.

Classification measurements can be performed against multiple TQ Analyst methods. The specification can be configured to classify against all methods or against a specific method that matches a text value.

History: Feature added to RESULT version 2.0.

This specification will return a logical RESULT based on the comparison of two text string RESULTs.

History: Feature added to RESULT version 2.0.

Add an option to the Report Event so that a text version of the HTML report may be created.

History: Feature added to RESULT version 2.0.

Sequence Component, to report the RESULTs for a particular component during a sequence run, and Sequence Summary, to report summary information about a sequence run, have been added to the list of possible sections that may be shown in a report. These specifications are only present when the Sequence Add-in is installed.

History: Feature added to RESULT version 2.0.

The spectrum title, especially the title from a sampling sequence, may be appended to the file name for a spectrum or report that will be archived. The index is now a separate option from the date and time in the file name.

History: Feature added to RESULT version 2.0.

The information that is used in a sampling sequence is read from a file. It is now possible to predefine the file that will be used. The contents of the file will be automatically entered into the sampling sequence table. The workflow can be configured to require operator confirmation of the sampling information or proceed without operator intervention.

History: Feature added to RESULT version 2.0.

The spectrum title, especially the title from a sampling sequence, may be appended to the file name for a standard spectrum that will be collected. The index is now a separate option from the date and time in the file name.

History: Feature added to RESULT version 2.0.

This is an event used by the Antaris IGS to define how the temperature and pressure of the gas sample will be determined.

History: Feature added to RESULT version 2.0.

For Antaris IGS, new sample and background specifications are available to define data collection settings for a gas cell sample.

History: Feature added to RESULT version 2.0.

For Antaris IGS, new sample and background specifications are available to define data collection settings for the Antaris IGS validation wheel.

History: Feature added to RESULT version 2.0.

The Quick Collect command may be run for the Gas cell and Instrument paths on an Antaris IGS.

History: Feature added to RESULT version 2.0.

The Show gas cell option is added to the Report options list in the Instrument Status command that is available in RESULT Operation.

History: Feature added to RESULT version 2.0.

If the operator does not fill in a required field and then uses the mouse to fill in the field and presses the Accept key an error will appear. If the operator uses the mouse to fill in missing fields and not the tab key to advance through fields some entered values will not be properly recorded by the request event. If these fields are displayed in a report the wrong values may be reported.

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V04588.

When you report the “Full spectrum check” warning for the Best Class Match, the values for “Full spectrum check” and “Full spectrum check value” are correct. However the values for the Second Best Class Match (and subsequent matches) are incorrect. They should be the same as the values for the best class match.

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V04564.

When running a workflow for the Autosampler RS that uses an external background reference, the workflow will give an error when run in simulation mode. The error message that is displayed has no content.

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V03744.

In Configure Standards, choose prompt for sample title and on the Save tab, choose to use the sample title. If a character that is illegal for use in Windows filenames such as the “:” character is entered into the title prompt, the file is not saved and there is no error message.

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V03769.

If a file name is entered with a character that is illegal for use in Windows filenames, such as the “:” character, RESULT does not save the spectrum and does not report an error.

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V04041.

In Quick Collect using the integrating sphere, set to collect at least 2 spectra, but with one background. The background and first spectrum collect fine. Before the second spectrum, the flag flips shut and the collection is unsuccessful. The error states that the interferogram peak cannot be found.

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V03755.

Regardless of the actual setting in the workflow, the border in a Report Item specification is always reported as ‘Thick’ when exporting a workflow as *.htm or *.txt

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V03734.

If you attempt to archive a spectrum or report with “prompt for file name”, there is no warning if you are overwriting a file. Also if a spectrum or report is archived as read only, a workflow error occurs and there is no opportunity to save the data as a different name.

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V03665.

The Instrument Status report does not display information about the installation and version number of the MultiPro autosampler software option.

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V03431.

If you are monitoring a peak location at 5402 cm-1 and you set the y display limits to 5400 to 5404 cm-1, you will see no numbers on the y axis. It appears that the space allowed for the y axis is not wide enough for the number of digits required.

Comment: The problem has been alleviated, but there are some restrictions. For numbers greater than 99, but less than 999, the smallest range of y axis values is 0.05. For numbers greater than 999, but less than 100,000, the smallest range of y axis values is 0.5.

History: This problem was reported in RESULT version 1.1; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V02807.

When collecting standards, if you have chosen to select the spectral title as the file name, then you may overwrite a spectrum with the same name. The user is not given a warning that the file is overwritten.

Comment: A warning message was added in RESULT 2.0.

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V04453.

The Optimize Gain button on the sample specifications for the Autosampler – Tablet Transmission Module and for the Autosampler – SoftGel Transmission Module is grayed. This is done for a technical reason in the software.

Recommendation: The gain and screen setting may be determined by using the Quick Collect command. The Optimize Gain button on this dialog is not grayed and is available. Run the command and copy the gain and screen setting to the sample specifications.

History: Describes operation in RESULT versions 1.2 – 2.0. Added to release notes in June 2004. Tracking number: V&V04445.

Consider a workflow where five samples are run in a loop. During sample 2 there is an air bubble that causes a workflow error that states “interferogram peak too large.” However in the report the RESULTs from sample 1 are used for sample 2. There is no indication in the report that there was a problem with the second sample. The RESULTs for sample 2 are incorrect.

Recommendation: Add error status to the report so that the report indicates whether the workflow was error free at the time the report was generated.

History: Describes operation in RESULT versions 1.2 – 2.0. Added to release notes in June 2004. Tracking number: V&V03742.

At the end of a workflow the following error was reported: “Internet Explorer cannot open the Internet site file: C:{subject} Data\Images\report.htm. Operation aborted.” Clicking OK to this message generated the “Cannot find server or DNS error.”

Recommendation: RESULT software writes a temporary copy of the report to the file report.htm in the Images directory. This directory is typically C:{subject} Data\Images. The user must have write permission to this file in order to view reports as they are created by a RESULT workflow.

History: Describes operation in RESULT versions 1.2 – 2.0. Added to release notes in June 2004. Tracking number: V&V04040.

The operator is unable to view the contents of the service log.

Recommendation: In order to view any of the logs, the operator must have read access to the RESULT database (*.mdb) file.

History: Describes operation in RESULT versions 1.0 – 2.0. Added to release notes in June 2004. Tracking number: V&V03989.

Pirouette is open and then RESULT Integrator is opened. If you browse through a workflow with a Pirouette measure event, then you get a message that only one copy of Pirouette may be open at a time. RESULT Integration closes after the warning message.

Recommendation: This is a known feature of Pirouette. Close RESULT before running Pirouette and close Pirouette before running RESULT.

History: Describes operation in RESULT versions 1.0 – 2.0. Added to release notes in June 2004. Tracking number: V&V03535.

RESULT software honors the local security policy for blank passwords. If the local security policy is set to disable blank passwords, RESULT will not allow a user to login with a blank password even if that is the current setting for the user’s password.

Recommendation: Use the Local Security Policy application in the Administrative Tools folder within control panel to set the Local Policies Security Options for Accounts: Limit local use of blank passwords to consol login only to Disabled if you want to allow blank passwords..

History: Describes operation in RESULT version 1.0-3.0. Added to release notes in June 2003. Tracking number: V&V4356.

A RESULT user must have read/write privileges to the RESULT database file in order to properly add or view entries in the database.

Recommendation: Insure that all RESULT users have read/write privileges to the RESULT database. The file is typically located in c:{subject} Data\config and is named RESULT.mdb.

To check the file privileges using FAT32 file systems, right-click the database file in Windows Explorer. From the popup menu, select Properties. In the Properties dialog box, verify that the Read-Only check box is cleared.

On NTFS file systems, the file security properties are located on the Security tab, which some users may not be able to access. If your computer uses the NTFS file system, have your Windows administrator give you read/write privileges for the RESULT database folder and file.

History: Describes operation in RESULT versions 1.0 – 1.1. Added to release notes in May 2002. Tracking number: V&V03592.

A RESULT user must have read/write privileges to the RESULT database folder and file in order to view or change settings in the Configure System dialog box.

Recommendation: Have your Windows administrator give you read/write privileges for the RESULT database folder and file. The file is typically located in c:{subject} Data\config and is named RESULT.mdb.

History: Describes operation in RESULT versions 1.0 – 1.1. Added to release notes in May 2002. Tracking number: V&V03593.

You are operating a computer running the Windows NT operating system as a local workstation (network cable is unplugged), but it is configured for networking.

Recommendation: Configure the networking options on your computer according to the recommendations in Installing Your Software.

History: Describes operation in RESULT versions 1.0 – 1.1. Added to release notes in May 2002. Tracking number: V&V03594.

RESULT cannot access PLSplus/IQ method files that were saved as read-only.

Recommendation: Turn off the Read-Only property of your method file(s) and then rerun the workflow.

History: Describes operation in RESULT version 1.1. Added to release notes in October 2001. Tracking number: V&V02732.

A verification workflow must store a workflow status RESULT in the RESULT database. If your verification workflow does not store a passing workflow status RESULT, you will not be allowed to run the associated workflow.

Recommendation: At the end of your verification workflow, add a check event named “Workflow status” and link it to a logic specification defining the desired pass/fail condition. Make sure the check event has the Store Pass/Fail RESULT To Database check box selected and the logical test specification has the Logical Test Is Always False If Workflow Errors Have Been Detected check box selected. See “Check events” and “Logical test specifications” in the “RESULT Integration Software” section of your Antaris User’s Guide for more information.

History: Describes operation in RESULT version 1.0. Added to release notes in April 2001. Tracking number: V&V02204.

RESULT uses the same engine as Internet Explorer for displaying and printing reports. When you right-click on a graphic image, the software disables the Print option and enables menu items that are specific to graphic images.

Recommendation: To print a report displayed in RESULT software, right click on a portion of the report that doesn’t include a graphic image. Then select a print option from the popup menu.

History: Describes operation in RESULT version 1.0. Added to release notes in April 2001. Tracking number: V&V01920.

RESULT software uses the event logging services of the Windows operating system to track unauthorized attempts to log on to RESULT.

Recommendation: To configure RESULT to track unauthorized attempts to log on or to digitally sign files, configure the Windows event logging service to log unauthorized logon attempts. The event logging service works the same way in RESULT as it does in Windows. For example, you can configure Windows to disable a user account if that user makes too many invalid attempts to log on. The account will be disabled if the user attempts to log on to Windows or RESULT software. See “Windows security features” in the “Software Administration” section of your Antaris User’s Guide for more information.

History: Describes operation in RESULT version 1.0. Added to release notes in January 2001. Tracking number: V&V01603.

Baseline offsets occur when the operator uses different aperture settings to collect the sample and background spectra. When using the software’s default settings to collect transmission spectra using the three-position sample tube holder, the software measures background spectra through the center opening in the sample tube holder which does not have an aperture. If you install an aperture in the sample holder position used to measure a liquid sample, the RESULTing spectrum will have an offset baseline.

Recommendation: If you want to measure a liquid sample using an aperture, install an aperture in both the front and back positions of the sample tube holder and then place the sample tube in one of those positions (front is easiest). Set the Sample Position list box on the sample specification associated with your collection event to match the location of the sample (Front Sample Compartment or Rear Sample Compartment). Set the Position list box on the associated background specification to the other position (Front Sample Compartment or Rear Sample Compartment) and then run the workflow. See the “Sample specifications” and “Background specifications” chapters in the “RESULT Integration Software” section of your Antaris User’s Guide for more information about the Sample Position and Background Position parameters.

History: Describes operation in RESULT version 1.0. Added to release notes in January 2001. Tracking number: V&V01387.

The Collect Simulation Spectrum dialog box (displayed by choosing New Sample For Simulation on the sample specification) allows you to create or select the spectra that will be used for simulated runs of a workflow. The Collect Associated Background Spectrum check box in the Collect Simulation Spectrum dialog box specifies whether a new simulation sample spectrum will include a corresponding background spectrum. This is true whether you collect the simulation sample or select an existing spectral file. If Collect Associated Background Spectrum is selected and you select a simulation spectrum that contains only sample data such as a Single Beam or Interferogram file (by choosing From File in the Collect Simulation Spectrum dialog), when you close the dialog box, the software will not add the spectrum to the Samples For Simulation list box on the sample specification.

Recommendation: If you want to run the workflow in simulation mode using a sample spectrum and its corresponding background spectrum, select a spectral file that contains both a sample and a background interferogram. Most spectral files contain both a sample and a background interferogram. Spectra that are collected with Data Format (located on the collection event) set to Interferogram or Single Beam contain only a sample interferogram.

If you want to run the workflow in simulation mode using an interferogram or single-beam spectrum (Data Format is set to Interferogram or Single Beam), clear the Collect Associated Background Spectrum check box before selecting the simulation spectrum.

History: Describes operation in RESULT version 1.0. Added to release notes in January 2001. Tracking number: V&V01518.

RESULT Operation does not provide proper access privileges to users when the computer or domain name contains a space. Microsoft strongly discourages using spaces when entering computer and domain names in their Windows operating system because Windows does not handle the space correctly in all situations. The Windows operating system presents a warning after a user enters a computer name that contains a space.

Recommendation: Remove the space from your computer or domain name in Windows and then restart the RESULT Operation application. You should also remove any spaces from the user names defined in RESULT Operation software.

History: Problem occurs in RESULT version 1.0. Added to release notes in January 2001. Tracking number: V&V01566.

If you expand or collapse the items displayed in the workflow navigation frame in the RESULT Integration main window and then switch back and forth between the Workflow tab and the Details tab, the software does not retain the previous view. For example, if you select the Workflow tab, select Expand from the toolbar to expand the displayed workflow, switch to the Details tab, and then switch back to the Workflow tab (or vice versa), the view is no longer expanded. Choose Expand again to expand the displayed items.

History: Describes operation in RESULT version 1.0. Added to release notes in October 2000. Tracking number: V&V00690.

Some collection and measurement event parameters are interdependent. If you delete a collection event whose RESULT spectrum is used by a subsequent measurement event, and then create another collection event, add its RESULT spectrum to the measurement event and rerun the workflow, the workflow may produce a measurement error due to inconsistent parameter settings between the collection event and the measurement event or its associated TQ Analyst method.

Recommendation: Use the workflow error text to determine which parameters are inconsistent with the measurement event and then change the collection event parameters to fix the error.

Tip: The workflow wizard will automatically make your collection parameters consistent if you create a measurement event that uses an existing TQ Analyst method when you run the wizard.

History: Describes operation in RESULT version 1.0. Added to release notes in October 2000. Tracking number: V&V01060.

If you change a TQ Analyst method that is linked to a measurement specification in the current workflow, the measurement specification won’t reflect the change until you select another event or specification and then reselect the measurement specification. Let’s say, for example, you are running RESULT Integration and you select a measurement specification that is linked to a TQ Analyst quantitative method and decide to add another component to that method. Then you start TQ Analyst software, add the component and save the method. When you return to RESULT Integration, the new component doesn’t appear in the list of measurements on the measurement specification.

Recommendation: Select another item in the workflow navigation frame, such as the measurement event or another measurement specification, and then reselect the previous measurement specification.

History: Describes operation in RESULT version 1.0. Added to release notes in October 2000. Tracking number: V&V01044.

The software reports a fit value of 0.0 whenever the spectral range for the collection event doesn’t cover the full range of the standards in the associated TQ Analyst method (for example, when the spectral range on the sample specification is 4000 -10000 cm^-1 and the method standards range from 3800 – 12000 cm^-1). If your spectral range is set appropriately, you might see a low fit value but you are unlikely to see a fit value of 0.0, which is the lowest possible fit value. When the spectral ranges of the samples and standards are inconsistent, the software reports a fit value of 0.0 even for spectra that are very similar.

Recommendation: To achieve an appropriate reading for the fit value, change the spectral range for the collection event (located on its associated sample specification) to cover the full range of the standards. In the example above, you would need to change the spectral range for the collection event to 3800-12000 cm^-1.

History: Describes operation in RESULT version 1.0. Added to release notes in October 2000. Tracking number: V&V01214.

When you view Instrument Status under the Maintenance menu in RESULT Operation software, the start date displayed for the validation wheel is the date on which the wheel was calibrated; not the date it was installed.

Recommendation: Use the validation wheel installation date to determine when to re-qualify the validation wheel. That date is noted in the Validation Wheel Standard booklet provided at installation.

History: Describes operation in RESULT version 1.0. Added to release notes in January 2000. Tracking number: V&V01657.

The Build TQ Analyst Method command provides two buttons for defining the method standards: a Browse button and a Select button. The Browse button sets the directory and path that will be used to add standards to the new method; the Select button allows you to specify a base name for adding a group of standards to the method by selecting a representative spectral data file.

Recommendation: Make sure the path points to the same location as the spectral data file you select as your representative standard.

History: Describes operation in RESULT version 1.0. Added to release notes in October 2001. Tracking number: V&V02652.

About once every month or two on a few systems, when RESULT Operation is run, the list of users is lost. The only alternative is to reenter the set of users.

History: Problem was reported in RESULT version 1.3A and may have been present in earlier versions. Added to release notes in September 2005.

Rather than using the values assigned for the external linearity standards, the values for the validation wheel are being used. This causes the linearity test to report incorrect values.

History: Problem occurred in RESULT version 2.0. Added to release notes in September 2005.

If the Windows administrator uses a blank password to log on to Windows 2000 or Windows XP operating system software and then starts RESULT Operation software, RESULT Operation does not accept the blank password.

Comments: The default delay period was shortened to allow faster positioning of the autosampler carousels.

History: Problem occurred in RESULT version 1.3. Problem was fixed in RESULT version 1.3A. Added to release notes in June 2004.

When the autosampler was moved counter-clockwise past the zero position a positioning error could occur..

History: Problem occurred in RESULT version 1.3. Problem was fixed in RESULT version 1.3A. Added to release notes in June 2004.

When the autosampler moves from one position to another it does not always rotate in the direction of the shortest distance to the new position

History: Problem occurred in RESULT version 1.3. Problem was fixed in RESULT version 1.3A. Added to release notes in June 2004.

RESULT supports the Nicolet® Antaris® Multiplexer system. To operate the Multiplexer system, RESULT must include the corresponding add-in software option. See Installing Your Software for information about installing add-in options with RESULT. To learn how to operate the Multiplexer system from RESULT, see the Antaris Multiplexer System User’s Guide.

History: Feature added to RESULT version 1.3.

When the Multiplexer add-in option is installed, RESULT Integration includes the multiplexer specification, which defines the multiplexer module configuration (6 or 12 channels) and the status of each channel. You must specify this information when you set up a workflow. Multiplexer specifications are linked to position multiplexer events and sample specifications in workflows.

To add a multiplexer specification to a workflow, in the workflow navigation frame in RESULT Integration, choose the Details button. Click the General Specifications group and then choose the Add button on the toolbar. A list of specification templates is displayed. Select the multiplexer specification and then choose OK. See your Antaris Multiplexer System User’s Guide for more information.

History: Feature added to RESULT version 1.3.

When the Multiplexer add-in option for RESULT is installed, RESULT Integration includes a new position multiplexer event. A position multiplexer event instructs the workflow to direct the near-infrared light beam to a specified channel or to the internal reference for data collection or other purposes in a workflow. Position multiplexer events are typically placed at the beginning of a workflow and right before or after a collect event. These events produce a single RESULT containing the current multiplexer channel number. See the Antaris Multiplexer System User’s Guide for more information.

History: Feature added to RESULT version 1.3.

When the Multiplexer add-in option for RESULT is installed, RESULT includes a new Position Multiplexer command, which allows you to specify the multiplexer channel for sample or background collections done without using a workflow. The Position Multiplexer command is available in the Maintenance menu in RESULT Operation software and in the Tools menu in RESULT Integration software. See the Antaris Multiplexer System User’s Guide for more information.

History: Feature added to RESULT version 1.3.

When the Multiplexer add-in option for RESULT is installed, RESULT Integration includes a new sample specification for use with multiplexer collect events in a workflow.

_Multiplexer fiber optic module sample specification _– Use this specification to set up data collection with any fiber optic probe mounted on the Multiplexer module, including the Thermo Scientific SabIR diffuse-reflectance probe. See the Antaris Multiplexer User’s Guide for more information.

History: Feature added to RESULT version 1.3.

When the Multiplexer add-in option for RESULT is installed, RESULT Integration includes a new background specification for use with multiplexer collect events in a workflow.

_Multiplexer fiber optic module background specification _– Use this specification to set up background data collection with any fiber optic probe mounted on the Multiplexer module, including the Thermo Scientific SabIR diffuse-reflectance probe. See the Antaris Multiplexer User’s Guide for more information.

History: Feature added to RESULT version 1.3.

RESULT Integration includes a new Clear event, which allows you to delete background spectra or selected workflow RESULTs that are no longer needed while the workflow is running. The Clear event can be set up to delete the current background spectrum or spectra or to delete the RESULTs produced by the previous collect, measure, process, or report event, or any combination of those RESULTs. When the software encounters a Clear event, it deletes the specified items before continuing.

You can use the clear event to force the software to prompt for a new background spectrum before the current background has expired. The clear event is also useful for preventing a long workflow that produces lots of interim data from filling up the computer’s internal memory, and for clearing important workflow RESULTs after they’ve been saved.

Note: If the Clear event occurs in a repeat loop, the software deletes the specified background or workflow RESULT produced in each iteration of the loop. If the Clear event occurs after a loop, the software deletes the specified items produced in all iterations of the loop, even if the event that produced the RESULTs specified that those RESULTs be retained.

History: Feature added to RESULT version 1.3.

When an autosampler was sent to position zero, it did not take the autosampler offset into account. Therefore the signal measured at position zero was not optimum.

History: This problem occurred in RESULT version 1.2; it was resolved in RESULT version 1.3. Added to release notes in June 2003.

When the “between dates” and “before date” Date Options were selected in the Log settings dialog box, no action was taken in the report. When the query was made to the data base, no entries were found

History: This problem occurred in RESULT version 1.2; it was resolved in RESULT version 1.3. Added to release notes in June 2003. Tracking number: V&V03795.

The Align Instrument command in the Maintenance menu of RESULT Operation software failed when the instrument was severely out of alignment (i.e., when the endplate positions were bad). The normal workaround for this type of problem was to reset the servo mechanism. However, in this case, it was also necessary to perform the laser alignment step.

History: This problem occurred in RESULT version 1.2; it was resolved in RESULT version 1.3. Added to release notes in June 2003.

Workflows set up to collect backgrounds infrequently sometimes continued using the background from a previous workflow instead of collecting a new background. RESULT now requires each workflow to collect a new background.

History: This problem occurred in RESULT version 1.2; it was resolved in RESULT version 1.3. Added to release notes in June 2003.

If the Windows administrator uses a blank password to log on to Windows 2000 or Windows XP operating system software and then starts RESULT Operation software, RESULT Operation does not accept the blank password.

Comments: The default delay period was shortened to allow faster positioning of the autosampler carousels.

History: Problem occurred in RESULT version 1.3. Problem was fixed in RESULT version 1.3A. Added to release notes in June 2004.

When the autosampler was moved counter-clockwise past the zero position a positioning error could occur..

History: Problem occurred in RESULT version 1.3. Problem was fixed in RESULT version 1.3A. Added to release notes in June 2004.

When the autosampler moves from one position to another it does not always rotate in the direction of the shortest distance to the new position

History: Problem occurred in RESULT version 1.3. Problem was fixed in RESULT version 1.3A. Added to release notes in June 2004.

If the operator does not fill in a required field and then uses the mouse to fill in the field and presses the Accept key an error will appear. If the operator uses the mouse to fill in missing fields and not the tab key to advance through fields some entered values will not be properly recorded by the request event. If these fields are displayed in a report the wrong values may be reported.

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V04588.

When you report the “Full spectrum check” warning for the Best Class Match, the values for “Full spectrum check” and “Full spectrum check value” are correct. However the values for the Second Best Class Match (and subsequent matches) are incorrect. They should be the same as the values for the best class match.

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V04564.

When running a workflow for the Autosampler RS that uses an external background reference, the workflow will give an error when run in simulation mode. The error message that is displayed has no content.

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V03744.

In Configure Standards, choose prompt for sample title and on the Save tab, choose to use the sample title. If an character that is illegal for use in Windows filenames such as the “:” character is entered into the title prompt, the file is not saved and there is no error message.

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V03769.

If a file name is entered with a character that is illegal for use in Windows filenames, such as the “:” character, RESULT does not save the spectrum and does not report an error.

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V04041.

In Quick Collect using the integrating sphere, set to collect at least 2 spectra, but with one background. The background and first spectrum collect fine. Before the second spectrum, the flag flips shut and the collection is unsuccessful. The error states that the interferogram peak cannot be found.

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V03755.

Regardless of the actual setting in the workflow, the border in a Report Item specification is always reported as ‘Thick’ when exporting a workflow as *.htm or *.txt

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V03734.

If you attempt to archive a spectrum or report with “prompt for file name”, there is no warning if you are overwriting a file. Also if a spectrum or report is archived as read only, a workflow error occurs and there is no opportunity to save the data as a different name.

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V03665.

The Instrument Status report does not display information about the installation and version number of the MultiPro autosampler software option.

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V03431.

If you are monitoring a peak location at 5402 cm-1 and you set the y display limits to 5400 to 5404 cm-1, you will see no numbers on the y axis. It appears that the space allowed for the y axis is not wide enough for the number of digits required.

Comment: The problem has been alleviated, but there are some restrictions. For numbers greater than 99, but less than 999, the smallest range of y axis values is 0.05. For numbers greater than 999, but less than 100,000, the smallest range of y axis values is 0.5.

History: This problem was reported in RESULT version 1.1; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V02807.

When collecting standards, if you have chosen to select the spectral title as the file name, then you may overwrite a spectrum with the same name. The user is not given a warning that the file is overwritten.

Comment: A warning message was added in RESULT 2.0.

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V04453.

About once every month or two on a few systems, when RESULT Operation is run, the list of users is lost. The only alternative is to reenter the set of users.

History: Problem was reported in RESULT version 1.3A and may have been present in earlier versions. Added to release notes in September 2005.

If the Windows administrator uses a blank password to log on to Windows 2000 or Windows XP operating system software and then starts RESULT Operation software, RESULT Operation does not accept the blank password.

Recommendation: Make sure the Windows administrator uses a standard password to log on to Windows 2000 and Windows XP operating system software.

History: Problem occurred in RESULT version 1.3. Added to release notes in June 2003. Tracking number: V&V4356.

RESULT is now compatible with the Microsoft® Windows® XP operating system software.

History: Feature added to RESULT version 1.2.

RESULT supports two new hardware devices, the Sample Cup Spinner and MultiPro Autosampler accessories for Antaris^® systems. To operate the MultiPro autosampler, RESULT must include the corresponding add-in software option. See Installing Your Software for information about installing add-in options with RESULT. To learn how to operate one of these hardware devices from RESULT, see the documentation that came with the device.

History: Feature added to RESULT version 1.2.

When the MultiPro Autosampler or Autosampler RS add-in option is installed, RESULT Integration includes the autosampler specification. To add an autosampler specification to a workflow, in the workflow navigation frame in RESULT Integration, choose the Details button. Click the General Specifications group and then choose the Add button on the toolbar. A list of specification templates is displayed. Select the autosampler specification and then choose OK. See your autosampler user’s manual for more information.

History: Feature added to RESULT version 1.2.

When the MultiPro Autosampler add-in option for RESULT is installed, RESULT Integration includes two new sample specifications for use with MultiPro Autosampler collect events in a workflow.

_Autosampler tablet transmission module sample specification _– Use this specification to set up transmission data collection with a tablet transmission module mounted on the MultiPro Autosampler. (This sample specification does not have a unique background specification; it is compatible with the Antaris tablet transmission module background specification.)

_Autosampler softgel transmission module sample specification _– Use this specification to set up transmission data collection with a softgel transmission module mounted on the MultiPro Autosampler. (This sample specification does not have a unique background specification; it is compatible with the Antaris softgel transmission module background specification.)

Use the Autosampler integrating sphere sample and background specifications to set up diffuse reflection sample and background collections using any autosampler and the Antaris integrating sphere sampling module.

See the MultiPro Autosampler user’s manual for more information.

History: Feature added to RESULT version 1.2.

The integrating sphere sample specification in RESULT Integration includes a Sample Cup Spinner list box for setting up data collection with the Sample Cup Spinner accessory for Antaris systems. See the Sample Cup Spinner user’s manual for more information.

History: Feature added to RESULT version 1.2.

RESULT is compatible with Pirouette^® version 3.04 method development software from InfoMetrix^®, Inc. See “Using Third-Party Methods with RESULT” in your Antaris Update for more information.

History: Feature added to RESULT version 1.2.

RESULT Operation now provides information about the status of the Antaris system. The status indicator is a green bar that appears at the top left corner of the RESULT Operation main window. When a workflow or other process is selected and running, the status indicator reads “In progress.” After the workflow or other process is completed, the status indicator disappears.

History: Feature added to RESULT version 1.2.

The Add button on the RESULT Integration toolbar now offers two new events: process events and run exe events. Run exe events allow you to run an executable program from a RESULT workflow. See “Run Exe Events” in your Antaris Update for more information.

In workflows that produce multiple spectra from a single collect event, such as the spectra collected from an autosampler, a process event allows you to use the collection RESULTs to calculate a mean spectrum, a variance spectrum, or a subtraction spectrum. You can also calculate a subtraction RESULT from the spectra generated by two different collect events. See “Process Events” in your Antaris Update for details.

History: Feature added to RESULT version 1.2.

In RESULT Integration, the set position event was renamed Position Autosampler and features were added to accommodate a variety of autosamplers and sampling stations. See “Position Autosampler Events” in your Antaris Update for more information.

History: Feature added to RESULT version 1.2.

Repeat events added to workflows in RESULT Integration can now be configured to prompt the operator to enter a sampling sequence at run time. This is useful for running an autosampler or for running a series of samples manually without requiring the operator to enter information about each sample. You can also specify a sampling sequence for collecting standards.

The sampling sequence must specify a sample name and identification (ID) number, or position number if using an autosampler, for each sample. When collecting standards, the component concentrations (or class index number) should also be included. The information may be entered manually or imported from a text file. See “Using a sampling sequence with RESULT Software” in your Antaris Update for more information.

History: Feature added to RESULT version 1.2.

Events that allow archiving of data in RESULT Integration now provide options for naming files with user-specified sample titles or a user-specified base name and a date stamp in addition to a globally unique identifier (GUID). The date stamp includes the current month, day, time and year in GMT (Greenwich Mean Time) format plus a three-digit index number. See “New File Naming Options for Archive Events” in your Antaris Update for details and examples.

History: Feature added to RESULT version 1.2.

When running workflows in RESULT Integration, the software allows you to view the spectral data or the sample report during data collection. (Previous versions of RESULT showed only the sample report.) See “Viewing collected spectra while running workflows in RESULT Integration” in your Antaris Update for more information.

History: Feature added to RESULT version 1.2.

The Configure Standards dialog box in RESULT Integration was updated to accommodate the collection of multiple standards using an autosampler. To display the dialog box, open the Tools menu and then choose Configure Standards. See “Configure Standards dialog box” in your Antaris Update for details.

History: Feature added to RESULT version 1.2.

The Build TQ Analyst Method dialog box in RESULT Integration was updated to allow the user to easily create a TQ Analyst quantitative method that contains selected standards directly from RESULT Integration software. To display the dialog box, open the Tools menu and then choose Build TQ Analyst Method. See “Building a TQ Analyst method with imported standards” in your Antaris Update for more information.

History: Feature added to RESULT version 1.2.

In RESULT Integration, the Save Workflow command in the File menu was renamed Save As Workflow. The Save button on the toolbar was also changed to Save As. The new names are more consistent with the behavior of these features.

History: Feature added to RESULT version 1.2.

When setting up a workflow that collects and measures a spectrum based on a QC Compare Search TQ Analyst method, the measure event produces several data types including the match index number which can be used by other events in the workflow such as report events and check events. In previous versions of RESULT, the match index provided the index number of the library spectrum that best matched the spectrum that was measured. RESULT now reports the match index as the index number of the class that best matches the measured spectrum.

History: Feature added to RESULT version 1.2.

When you specify a background frequency of "Every hour" you collect one background and are never again requested to collect another background.  This only is a problem in RESULT Operation software.  (Also if you set "Every 4 hours", you are asked for a new background every one hour.)

History: This problem occurred in RESULT version 1.1a; it was resolved in RESULT version 1.2. Added to release notes in September 2002. Tracking number: V&V03631.

After creating a TQ Analyst qualitative (classification) method, linking the method to a workflow in RESULT Integration software and running the workflow, if you then opened the method in TQ Analyst, added classes, saved the method and then ran the workflow, RESULT failed to recognize the additional classes.

History: This problem occurred in RESULT version 1.1a; it was resolved in RESULT version 1.2. Added to release notes in November 2002. Tracking number: V&V02817.

If a workflow that was linked to a qualitative (classification) method was set up to report both the match value and name of the best matched class in a summary table, RESULT reported one or the other but not both. The reported item was the attribute that was listed first in the workflow measurement specification. Any item that appeared second or third in the list of attributes was not reported.

History: This problem occurred in RESULT version 1.1a; it was resolved in RESULT version 1.2. Added to release notes in September 2002. Tracking number: V&V02889.

After querying the RESULT database for archived items in RESULT Operation software, if you then queried for a subset of the original list and the subset produced no entries, RESULT did not display the new list of items but instead retained the list from the first query.

History: This problem occurred in RESULT version 1.1a; it was resolved in RESULT version 1.2. Added to release notes in November 2002. Tracking number: V&V03090.

When setting up a workflow that is linked to a qualitative (classification) method in RESULT Integration software, it was not possible to create a Perform If event with the logic dependent upon the best matched class. RESULT now provides a Match Index data type for all measure events linked to a classification method. The Match Index gives the index number of the class that best matches the measured spectrum.

History: This problem occurred in RESULT version 1.1a; it was resolved in RESULT version 1.2. Added to release notes in November 2002. Tracking number: ENH03188.

If a workflow set up a sample report that included two spectra that had different x-axis limits such as a transmission spectrum collected with a tablet analyzer module and a diffuse-reflection spectrum collected with the integrating sphere module and used the default x-axis limits, the software used the x-axis limits of the first spectrum to set up the display and then overlaid the second spectrum using the same X-axis limits. This changed the locations of the peaks in the second spectrum. RESULT still uses the x-axis limits of the first spectrum to set up the display and then overlays the second spectrum, but it places the second spectrum in its proper location on the x-axis.

History: This problem occurred in RESULT version 1.1a; it was resolved in RESULT version 1.2. Added to release notes in November 2002. Tracking number: V&V03326.

When running a workflow in RESULT Operation, if the operator interrupted the workflow by choosing the Stop button in the software, the button to open the transmission module door on the front of the Antaris instrument no longer worked. The operator had to turn the power switch for the instrument off and back on before the button would operate.

History: This problem occurred in RESULT version 1.1a; it was resolved in RESULT version 1.2. Added to release notes in November 2002. Tracking number: V&V03499.

If you used the Build TQ Analyst Method command in RESULT Integration software to create an analytical method, the software saved the method files using the path for storing workflows and methods specified in RESULT Operation rather than the path for storing workflows and method specified in RESULT Integration.

History: This problem occurred in RESULT version 1.1a; it was resolved in RESULT version 1.2. Added to release notes in November 2002. Tracking number: V&V03549.

After using RESULT software to collect standards for a quantitative method, if you imported the standards into TQ Analyst, any component concentration values greater than 1000 that were entered in RESULT were not copied to TQ Analyst.

History: This problem occurred in RESULT version 1.1a; it was resolved in RESULT version 1.2. Added to release notes in November 2002. Tracking number: V&V03596.

When setting up a workflow in RESULT Integration, if you set Number Of Background Scans on the background specification to Twice As Many Scans As For Samples, the workflow collected twice as many background scans as sample scans but it also doubled the number of sample scans.

History: This problem occurred in RESULT version 1.1a; it was resolved in RESULT version 1.2. Added to release notes in November 2002. Tracking number: V&V03650.

If you install the standard tablet analyzer on the Antaris instrument and then run a workflow that is set up for the softgel tablet analyzer, RESULT displays a dialog box with the message “Connect standard tablet analyzer to Antaris and then press Acknowledge.” If you pressed the Acknowledge button on the instrument without installing the correct tablet analyzer, the workflow continued running. This was corrected so that the workflow will not run when the sample and background specifications do not match the tablet analyzer installed on the instrument.

History: This problem occurred in RESULT version 1.1a; it was resolved in RESULT version 1.2. Added to release notes in November 2002. Tracking number: V&V03692.

When setting up a workflow in RESULT Integration software, if you created a loop that compared a classification RESULT to a particular class, the software required the operator to specify the expected class during each iteration of the loop. RESULT now allows you to define the expected class one time and use it for all the measurements in a loop. There are two ways to set this up. If the expected class is known and never changes, you can define it by setting Class Check on the Report tab in your TQ Analyst method. If the RESULT operator must define the expected class while running the workflow, create a loop that contains the collect and measure event sequence. Then place a request event before the loop. In the request event parameters, select the Prompt For Expected Class check box and then select the associated measure event in the Measure Event drop down list box. The measure event will generate a pass or fail RESULT that compares the measured class to the expected class. To access the comparison RESULT, for example to add that RESULT to a sample report, select the measure event when Data Type is set to Class Check.

History: This problem occurred in RESULT version 1.1a; it was resolved in RESULT version 1.2. Added to release notes in November 2002. Tracking number: CST03283.

After querying the RESULT database for archived items in RESULT Operation software, RESULT displayed the Date/Time, File Name and Data Type columns in the archive log window. If you then resized the window to make it wider, the File Name and Data Type columns disappeared.

Improvement: RESULT displays all items correctly after the archive log window is resized.

History: This problem occurred in RESULT version 1.1a; it was improved in RESULT version 1.2. Added to release notes in November 2002. Tracking number: V&V03099.

When running a workflow set up to collect data using the SabIR fiber optic probe, if the background specification is configured to collect background data using the probe’s internal Spectralon reference, the probe must be placed in the holster for background collections. If you removed the probe from the holster while background collection was in progress, RESULT continued collecting the background data.

Improvement: RESULT stops collecting the background data and displays a message asking the operator to place the probe back in the holster.

History: This problem occurred in RESULT version 1.1a; it was resolved in RESULT version 1.2. Added to release notes in November 2002. Tracking number: V&V03640.

The Optimize Gain button on the sample specifications for the Autosampler – Tablet Transmission Module and for the Autosampler – SoftGel Transmission Module is grayed. This is done for a technical reason in the software.

Recommendation: The gain and screen setting may be determined by using the Quick Collect command. The Optimize Gain button on this dialog is not grayed and is available. Run the command and copy the gain and screen setting to the sample specifications.

History: Describes operation in RESULT versions 1.2 – 2.0. Added to release notes in June 2004. Tracking number: V&V04445.

Consider a workflow where five samples are run in a loop. During sample 2 there is an air bubble that causes a workflow error that states “interferogram peak too large.” However in the report the RESULTs from sample 1 are used for sample 2. There is no indication in the report that there was a problem with the second sample. The RESULTs for sample 2 are incorrect.

Recommendation: Add error status to the report so that the report indicates whether the workflow was error free at the time the report was generated.

History: Describes operation in RESULT versions 1.2 – 2.0. Added to release notes in June 2004. Tracking number: V&V03742.

At the end of a workflow the following error was reported: “Internet Explorer cannot open the Internet site file: C:{subject} Data\Images\report.htm. Operation aborted.” Clicking OK to this message generated the “Cannot find server or DNS error.”

Recommendation: RESULT software writes a temporary copy of the report to the file report.htm in the Images directory. This directory is typically C:{subject} Data\Images. The user must have write permission to this file in order to view reports as they are created by a RESULT workflow.

History: Describes operation in RESULT versions 1.2 – 2.0. Added to release notes in June 2004. Tracking number: V&V04040.

The operator is unable to view the contents of the service log.

Recommendation: In order to view any of the logs, the operator must have read access to the RESULT database (*.mdb) file.

History: Describes operation in RESULT versions 1.0 – 2.0. Added to release notes in June 2004. Tracking number: V&V03989.

Pirouette is open and then RESULT Integrator is opened. If you browse through a workflow with a Pirouette measure event, then you get a message that only one copy of Pirouette may be open at a time. RESULT Integration closes after the warning message.

Recommendation: This is a known feature of Pirouette. Close RESULT before running Pirouette and close Pirouette before running RESULT.

History: Describes operation in RESULT versions 1.0 – 2.0. Added to release notes in June 2004. Tracking number: V&V03535.

A RESULT user must have read/write privileges to the RESULT database file in order to properly add or view entries in the database.

Recommendation: Insure that all RESULT users have read/write privileges to the RESULT database. The file is typically located in c:{subject} Data\config and is named RESULT.mdb.

To check the file privileges using FAT32 file systems, right-click the database file in Windows Explorer. From the popup menu, select Properties. In the Properties dialog box, verify that the Read-Only check box is cleared.

On NTFS file systems, the file security properties are located on the Security tab, which some users may not be able to access. If your computer uses the NTFS file system, have your Windows administrator give you read/write privileges for the RESULT database folder and file.

History: Describes operation in RESULT versions 1.0 – 1.1. Added to release notes in May 2002. Tracking number: V&V03592.

A RESULT user must have read/write privileges to the RESULT database folder and file in order to view or change settings in the Configure System dialog box.

Recommendation: Have your Windows administrator give you read/write privileges for the RESULT database folder and file. The file is typically located in c:{subject} Data\config and is named RESULT.mdb.

History: Describes operation in RESULT versions 1.0 – 1.1. Added to release notes in May 2002. Tracking number: V&V03593.

You are operating a computer running the Windows NT operating system as a local workstation (network cable is unplugged), but it is configured for networking.

Recommendation: Configure the networking options on your computer according to the recommendations in Installing Your Software.

History: Describes operation in RESULT versions 1.0 – 1.1. Added to release notes in May 2002. Tracking number: V&V03594.

RESULT cannot access PLSplus/IQ method files that were saved as read-only.

Recommendation: Turn off the Read-Only property of your method file(s) and then rerun the workflow.

History: Describes operation in RESULT version 1.1. Added to release notes in October 2001. Tracking number: V&V02732.

A verification workflow must store a workflow status RESULT in the RESULT database. If your verification workflow does not store a passing workflow status RESULT, you will not be allowed to run the associated workflow.

Recommendation: At the end of your verification workflow, add a check event named “Workflow status” and link it to a logic specification defining the desired pass/fail condition. Make sure the check event has the Store Pass/Fail RESULT To Database check box selected and the logical test specification has the Logical Test Is Always False If Workflow Errors Have Been Detected check box selected. See “Check events” and “Logical test specifications” in the “RESULT Integration Software” section of your Antaris User’s Guide for more information.

History: Describes operation in RESULT version 1.0. Added to release notes in April 2001. Tracking number: V&V02204.

RESULT uses the same engine as Internet Explorer for displaying and printing reports. When you right-click on a graphic image, the software disables the Print option and enables menu items that are specific to graphic images.

Recommendation: To print a report displayed in RESULT software, right click on a portion of the report that doesn’t include a graphic image. Then select a print option from the popup menu.

History: Describes operation in RESULT version 1.0. Added to release notes in April 2001. Tracking number: V&V01920.

RESULT software uses the event logging services of the Windows operating system to track unauthorized attempts to log on to RESULT.

Recommendation: To configure RESULT to track unauthorized attempts to log on or to digitally sign files, configure the Windows event logging service to log unauthorized logon attempts. The event logging service works the same way in RESULT as it does in Windows. For example, you can configure Windows to disable a user account if that user makes too many invalid attempts to log on. The account will be disabled if the user attempts to log on to Windows or RESULT software. See “Windows security features” in the “Software Administration” section of your Antaris User’s Guide for more information.

History: Describes operation in RESULT version 1.0. Added to release notes in January 2001. Tracking number: V&V01603.

Baseline offsets occur when the operator uses different aperture settings to collect the sample and background spectra. When using the software’s default settings to collect transmission spectra using the three-position sample tube holder, the software measures background spectra through the center opening in the sample tube holder which does not have an aperture. If you install an aperture in the sample holder position used to measure a liquid sample, the RESULTing spectrum will have an offset baseline.

Recommendation: If you want to measure a liquid sample using an aperture, install an aperture in both the front and back positions of the sample tube holder and then place the sample tube in one of those positions (front is easiest). Set the Sample Position list box on the sample specification associated with your collection event to match the location of the sample (Front Sample Compartment or Rear Sample Compartment). Set the Position list box on the associated background specification to the other position (Front Sample Compartment or Rear Sample Compartment) and then run the workflow. See the “Sample specifications” and “Background specifications” chapters in the “RESULT Integration Software” section of your Antaris User’s Guide for more information about the Sample Position and Background Position parameters.

History: Describes operation in RESULT version 1.0. Added to release notes in January 2001. Tracking number: V&V01387.

The Collect Simulation Spectrum dialog box (displayed by choosing New Sample For Simulation on the sample specification) allows you to create or select the spectra that will be used for simulated runs of a workflow. The Collect Associated Background Spectrum check box in the Collect Simulation Spectrum dialog box specifies whether a new simulation sample spectrum will include a corresponding background spectrum. This is true whether you collect the simulation sample or select an existing spectral file. If Collect Associated Background Spectrum is selected and you select a simulation spectrum that contains only sample data such as a Single Beam or Interferogram file (by choosing From File in the Collect Simulation Spectrum dialog), when you close the dialog box, the software will not add the spectrum to the Samples For Simulation list box on the sample specification.

Recommendation: If you want to run the workflow in simulation mode using a sample spectrum and its corresponding background spectrum, select a spectral file that contains both a sample and a background interferogram. Most spectral files contain both a sample and a background interferogram. Spectra that are collected with Data Format (located on the collection event) set to Interferogram or Single Beam contain only a sample interferogram.

If you want to run the workflow in simulation mode using an interferogram or single-beam spectrum (Data Format is set to Interferogram or Single Beam), clear the Collect Associated Background Spectrum check box before selecting the simulation spectrum.

History: Describes operation in RESULT version 1.0. Added to release notes in January 2001. Tracking number: V&V01518.

RESULT Operation does not provide proper access privileges to users when the computer or domain name contains a space. Microsoft strongly discourages using spaces when entering computer and domain names in their Windows operating system because Windows does not handle the space correctly in all situations. The Windows operating system presents a warning after a user enters a computer name that contains a space.

Recommendation: Remove the space from your computer or domain name in Windows and then restart the RESULT Operation application. You should also remove any spaces from the user names defined in RESULT Operation software.

History: Problem occurs in RESULT version 1.0. Added to release notes in January 2001. Tracking number: V&V01566.

If you expand or collapse the items displayed in the workflow navigation frame in the RESULT Integration main window and then switch back and forth between the Workflow tab and the Details tab, the software does not retain the previous view. For example, if you select the Workflow tab, select Expand from the toolbar to expand the displayed workflow, switch to the Details tab, and then switch back to the Workflow tab (or vice versa), the view is no longer expanded. Choose Expand again to expand the displayed items.

History: Describes operation in RESULT version 1.0. Added to release notes in October 2000. Tracking number: V&V00690.

Some collection and measurement event parameters are interdependent. If you delete a collection event whose RESULT spectrum is used by a subsequent measurement event, and then create another collection event, add its RESULT spectrum to the measurement event and rerun the workflow, the workflow may produce a measurement error due to inconsistent parameter settings between the collection event and the measurement event or its associated TQ Analyst method.

Recommendation: Use the workflow error text to determine which parameters are inconsistent with the measurement event and then change the collection event parameters to fix the error.

Tip: The workflow wizard will automatically make your collection parameters consistent if you create a measurement event that uses an existing TQ Analyst method when you run the wizard.

History: Describes operation in RESULT version 1.0. Added to release notes in October 2000. Tracking number: V&V01060.

If you change a TQ Analyst method that is linked to a measurement specification in the current workflow, the measurement specification won’t reflect the change until you select another event or specification and then reselect the measurement specification. Let’s say, for example, you are running RESULT Integration and you select a measurement specification that is linked to a TQ Analyst quantitative method and decide to add another component to that method. Then you start TQ Analyst software, add the component and save the method. When you return to RESULT Integration, the new component doesn’t appear in the list of measurements on the measurement specification.

Recommendation: Select another item in the workflow navigation frame, such as the measurement event or another measurement specification, and then reselect the previous measurement specification.

History: Describes operation in RESULT version 1.0. Added to release notes in October 2000. Tracking number: V&V01044.

The software reports a fit value of 0.0 whenever the spectral range for the collection event doesn’t cover the full range of the standards in the associated TQ Analyst method (for example, when the spectral range on the sample specification is 4000 -10000 cm^-1 and the method standards range from 3800 – 12000 cm^-1). If your spectral range is set appropriately, you might see a low fit value but you are unlikely to see a fit value of 0.0, which is the lowest possible fit value. When the spectral ranges of the samples and standards are inconsistent, the software reports a fit value of 0.0 even for spectra that are very similar.

Recommendation: To achieve an appropriate reading for the fit value, change the spectral range for the collection event (located on its associated sample specification) to cover the full range of the standards. In the example above, you would need to change the spectral range for the collection event to 3800-12000 cm^-1.

History: Describes operation in RESULT version 1.0. Added to release notes in October 2000. Tracking number: V&V01214.

When you view Instrument Status under the Maintenance menu in RESULT Operation software, the start date displayed for the validation wheel is the date on which the wheel was calibrated; not the date it was installed.

Recommendation: Use the validation wheel installation date to determine when to re-qualify the validation wheel. That date is noted in the Validation Wheel Standard booklet provided at installation.

History: Describes operation in RESULT version 1.0. Added to release notes in January 2000. Tracking number: V&V01657.

The Build TQ Analyst Method command provides two buttons for defining the method standards: a Browse button and a Select button. The Browse button sets the directory and path that will be used to add standards to the new method; the Select button allows you to specify a base name for adding a group of standards to the method by selecting a representative spectral data file.

Recommendation: Make sure the path points to the same location as the spectral data file you select as your representative standard.

History: Describes operation in RESULT version 1.0. Added to release notes in October 2001. Tracking number: V&V02652.

If the operator does not fill in a required field and then uses the mouse to fill in the field and presses the Accept key an error will appear. If the operator uses the mouse to fill in missing fields and not the tab key to advance through fields some entered values will not be properly recorded by the request event. If these fields are displayed in a report the wrong values may be reported.

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V04588.

When you report the “Full spectrum check” warning for the Best Class Match, the values for “Full spectrum check” and “Full spectrum check value” are correct. However the values for the Second Best Class Match (and subsequent matches) are incorrect. They should be the same as the values for the best class match.

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V04564.

When running a workflow for the Autosampler RS that uses an external background reference, the workflow will give an error when run in simulation mode. The error message that is displayed has no content.

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V03744.

In Configure Standards, choose prompt for sample title and on the Save tab, choose to use the sample title. If an character that is illegal for use in Windows filenames such as the “:” character is entered into the title prompt, the file is not saved and there is no error message.

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V03769.

If a file name is entered with a character that is illegal for use in Windows filenames, such as the “:” character, RESULT does not save the spectrum and does not report an error.

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V04041.

In Quick Collect using the integrating sphere, set to collect at least 2 spectra, but with one background. The background and first spectrum collect fine. Before the second spectrum, the flag flips shut and the collection is unsuccessful. The error states that the interferogram peak cannot be found.

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V03755.

Regardless of the actual setting in the workflow, the border in a Report Item specification is always reported as ‘Thick’ when exporting a workflow as *.htm or *.txt

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V03734.

If you attempt to archive a spectrum or report with “prompt for file name”, there is no warning if you are overwriting a file. Also if a spectrum or report is archived as read only, a workflow error occurs and there is no opportunity to save the data as a different name.

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V03665.

The Instrument Status report does not display information about the installation and version number of the MultiPro autosampler software option.

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V03431.

If you are monitoring a peak location at 5402 cm-1 and you set the y display limits to 5400 to 5404 cm-1, you will see no numbers on the y axis. It appears that the space allowed for the y axis is not wide enough for the number of digits required.

Comment: The problem has been alleviated, but there are some restrictions. For numbers greater than 99, but less than 999, the smallest range of y axis values is 0.05. For numbers greater than 999, but less than 100,000, the smallest range of y axis values is 0.5.

History: This problem was reported in RESULT version 1.1; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V02807.

When collecting standards, if you have chosen to select the spectral title as the file name, then you may overwrite a spectrum with the same name. The user is not given a warning that the file is overwritten.

Comment: A warning message was added in RESULT 2.0.

History: This problem was reported in RESULT version 1.2; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V04453.

If the cursor is left highlighting the measure event in a given workflow and Build TQ method is selected, the checkbox for automatically link new method to measure event is checked, the new method will not be linked to the measure event.  The cursor must be left on a different event.

Recommendation: Leave the cursor on a an event other than the linked measure event, before selecting the Build TQ Method command from the menu.

History: Problem occurred in RESULT version 1.2-2.0. Added to release notes in June 2004. Tracking number: V&V3636.

Many Windows 2000 computers support Advanced Power Management. These computers can be set up to enter standby mode after a period of inactivity in order to save power. The device driver used by RESULT software is not currently compatible with standby mode. If the computer enters standby mode when RESULT is running, or if it tries to communicate with the Antaris instrument after leaving standby mode, RESULT stops running.

Recommendation: Disable Standby Mode in the Power Options dialog box of Windows software for all RESULT users. To access the Power Options dialog box, right-click on the Windows desktop and then select Properties. The Display Properties dialog box appears. Select the Screen Saver tab. On the Screen Saver tab, choose the Power button. In the RESULTing dialog box, select the Power Schemes tab. On the Power Schemes tab, set the Turn Off Monitor list box to Never and the Turn Off Hard Disks list box to Never. Choose OK to close the dialog box. Choose OK again to close the Display Properties dialog box.

History: Problem occurred in RESULT version 1.1. Added to release notes in May 2002. Tracking number: V&V03591.

If you have Internet Explorer version 5.5 loaded on your computer, you may have problems printing tables in reports generated in RESULT software when using the HP LaserJet 8000 DN printer. The printer may fail to print a row in a table that crosses a page boundary.

Recommendation: Install Internet Explorer version 4.0 or 5.0.

History: Problem occurred in RESULT version 1.0. Added to release notes in October 2000. Tracking number: V&V01255. This problem was reported to Microsoft and is tracked by Microsoft incident SRZ000816000156.

In RESULT Integration software, when the user changes a setting in a collection event that has Background Frequency set to Once Every Hour or Once Every Four Hours and then either tests the workflow or collects a standard, the software does not collect a new background (or prompt the operator to do so) until the specified background frequency period has elapsed.

Recommendation: Set Background Frequency to Before Every Sample and then either test the workflow or collect a standard. This forces the software to collect a new background before collecting the first sample or standard. Then you are free to use other Background Frequency settings.

History: Problem occurred in RESULT version 1.0. Added to release notes in October 2000. Tracking number: V&V01434.

In RESULT Integration software, when the user collects a simulation spectrum for the tablet analyzer with the Collect Associated Background Spectrum check box selected, sample collection begins immediately following background collection. The software does not allow time for or prompt the user to insert the sample.

Recommendation: Use the tablet analyzer to collect and save the sample and background spectra that will be used for simulated runs of your workflow. Then display the sample specification and choose New in the Samples For Simulation group. In the RESULTing dialog box, use the From File button to add the sample and background files to your workflow.

History: Problem occurred in RESULT version 1.0. Added to release notes in October 2001. Tracking number: V&V02649.

RESULT is now compatible with the Microsoft® Windows® 2000 operating system software.

History: Feature added to RESULT version 1.1.

We added Back and Next commands to the toolbar and Edit menu of RESULT Integration to help you easily navigate between screens in the open workflow. The Back command returns to the previous screen. After you use the Back command, the Next command becomes available in the software. Use the Next button to return to screen that was displayed the last time you pressed the Back button.

History: Feature added to RESULT version 1.1.

We added a Reset command to the toolbar and Edit menu of RESULT Integration. After editing the parameter settings for a workflow event or specification displayed in RESULT Integration software, you can use the Reset command to restore those parameters to the settings displayed when you first selected that workflow event or specification.

History: Feature added to RESULT version 1.1.

We added an Export command to the RESULT Integration File menu to allow you to export workflows or the simulation spectra attached to a workflow in various formats.

History: Feature added to RESULT version 1.1.

We added the Optimize Gain feature to Quick Collect in RESULT Operation and RESULT Integration. Use Optimize Gain to see the Gain and attenuation wheel settings the software recommends for the current sample. Optimize Gain is most useful for tablets and gel-cap or softgel samples measured using the tablet analyzer sampling module.

History: Feature added to RESULT version 1.1.

The current version number for RESULT software now appears in the instrument status report. To view the instrument status report, choose Instrument Status from the Maintenance menu of RESULT Operation software.

History: Feature added to RESULT version 1.1.

Information about add-in options now appears in the instrument status report. For example, if you installed any add-in options for RESULT, such as the option for the Autosampler RS, those options will be listed in the instrument status report. To view the instrument status report, choose Instrument Status from the Maintenance menu of RESULT Operation software.

History: Feature added to RESULT version 1.1.

You may now configure RESULT Integration and RESULT Operation software for the Antaris Reflection Transmission Sampling (RTS) system. The RTS option appears in the Model drop-down list in the RESULT Integration Options dialog box (choose Options from the Edit menu in the RESULT Integration main window) and in the RESULT Options dialog box in RESULT Operation (choose RESULT Options from the Administration menu in the RESULT Operation main window).

History: Feature added to RESULT version 1.1.

The Update Instrument Information dialog box in RESULT Operation now allows you to create backup files that contain configuration information for optional hardware devices, such as the Autosampler RS. To display the dialog box, open the Service menu in the RESULT Operation main window and then choose Update Instrument Information. The software saves hardware configuration files in the same directory where it stores software configuration files.

History: Feature added to RESULT version 1.1.

The Instrument Check diagnostic now works with all Antaris instrument models (previously available on all models except the Antaris Fiber Optic and Solid Sampling systems). Instrument Check uses the main analyzer transmission detector to produce a series of spectra for diagnostic purposes. When compared to previous instrument check spectra, these tests are helpful in determining whether a problem exists with your instrument. The Instrument Check feature is available from the Maintenance menu in the RESULT Operation main window.

History: Feature added to RESULT version 1.1.

The Archive event now provides two options for Report Format: standard HTML and Unicode HTML. Report Format defines the format for reports archived by a workflow. You may prefer the Unicode HTML format if your report contains text from double-byte character sets, such as Kanji.

History: Feature added to RESULT version 1.1.

The Align Instrument function in RESULT Operation selected a good optical alignment for the Antaris FT-NIR analyzer but failed to find the optimum optical alignment for that system. We implemented a modified alignment routine that ensures the instrument always reaches the best possible optical alignment.

History: Improvement added to RESULT 1.1

If you are monitoring a peak location at 5402 cm-1 and you set the y display limits to 5400 to 5404 cm-1, you will see no numbers on the y axis. It appears that the space allowed for the y axis is not wide enough for the number of digits required.

Comment: The problem has been alleviated, but there are some restrictions. For numbers greater than 99, but less than 999, the smallest range of y axis values is 0.05. For numbers greater than 999, but less than 100,000, the smallest range of y axis values is 0.5.

History: This problem was reported in RESULT version 1.1; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V02807.

When a comma was used for the number separator instead of a period, (standard setting for European computer configurations), the software incorrectly translated the spectral range settings to numeric values. This caused a collection error in the workflow.

History: This problem occurred in RESULT version 1.0; it was resolved in RESULT version 1.1. Added to release notes in October 2001. Tracking number: V&V02566.

If you held down the Shift key while you dragged and then dropped a workflow item onto the topmost item in the open workflow, when you ran the workflow, the dropped item would not execute and would disappear if you switched between the Details tab and the Workflow tab.

History: This problem occurred in RESULT version 1.0; it was resolved in RESULT version 1.1. Added to release notes in October 2001. Tracking number: V&V02389.

The peak location measurement requires three data points to determine the peak location. If you changed the resolution so that the specified region no longer contained three data points, the measurement did not produce a RESULT. RESULT now ensures that the selected regions contain at least three data points for all of the resolution settings used with the method.

History: This problem occurred in RESULT version 1.0; it was resolved in RESULT version 1.1. Added to release notes in October 2001. Tracking number: V&V01676.

If you set up a QC Compare method to report the class name for the second, third, etc. best matched spectrum, the software reported the correct class name for the best matched spectrum but not for the second, third, etc. best matches. The class names reported for the second, third, etc. best matches were the same as for the best match.

History: This problem occurred in RESULT version 1.0; it was resolved in RESULT version 1.1. Added to release notes in October 2001. Tracking number: V&V02340.

The apodization function used by RESULT software contained an error that caused channeling in spectra produced from single-sided interferograms. RESULT is configured to collect single-sided interferograms only when the Resolution parameter on the sample specification is set to 2 cm-1.

History: This problem occurred in RESULT version 1.0; it was resolved in RESULT version 1.1. Added to release notes in January 2001. Tracking number: V&V01404.

When arranging events in a workflow displayed in the workflow navigation frame of the RESULT Integration main window, if you dragged and dropped an item to a lower position in the same event group, the software sometimes placed the item one position below the specified location.

History: This problem occurred in RESULT version 1.0; it was resolved in RESULT version 1.1. Added to release notes in January 2001. Tracking number: V&V01420.

If you used the standard tablet analyzer sampling module to collect a spectrum and then aligned the instrument in RESULT Operation software, the alignment sometimes failed. The failure occurred because the software did not always reset the velocity to the correct value for the main transmission detector before starting the alignment procedure.

History: This problem occurred in RESULT version 1.0; it was resolved in RESULT version 1.1. Added to release notes in January 2001. Tracking number: V&V01499.

The Cycle Through Simulation Samples check box on the sample specification was unavailable in the software even though the Samples For Simulation drop-down list contained multiple simulation spectra.

History: This problem occurred in RESULT version 1.0; it was resolved in RESULT version 1.1. Added to release notes in January 2001. Tracking number: V&V01518.

After the operator digitally signed a file, certain computers sometimes reported an error similar to the following:

"The Registry entry for the key container could not be opened and may not exist. Confirm software installation."

The error occurred whether the file was signed in RESULT Integration or RESULT Operation software.

History: This problem occurred in RESULT version 1.0; it was resolved in RESULT version 1.1. Added to release notes in January 2001. Tracking number: V&V01574.

Version 1.0 of RESULT software depends on the file ATL.DLL. The file is typically present on most computers. If the file was not available, the software displayed an error message similar to the following:

“The dynamic link library ATL.DLL could not be found in the specified path.”

History: This problem occurred in RESULT version 1.0; it was resolved in RESULT version 1.1. Added to release notes in January 2001. Tracking number: V&V01609.

In RESULT Integration software, Alt key combinations that are associated with menu items and tool bar buttons worked correctly, but unassigned Alt key combinations, such as Alt+R and Alt+Q, sometimes caused the application to stop responding. The problem occurred only when the Alt key combination was used while the cursor was located in an edit field or check box in the display area of RESULT Integration. It did not occur when the cursor was in the menu, toolbar, or workflow navigation frame.

History: This problem occurred in RESULT version 1.0; it was resolved in RESULT version 1.1. Added to release notes in October 2000. Tracking number: V&V01375.

When using the Antaris integrating sphere sampling module with Gain set to 4 or 8 and a Background Frequency setting other than Before Every Sample, you could usually collect an initial spectrum but every subsequent collection either produced bad spectra or generated a workflow error that related to a peak location problem.

History: This problem occurred in RESULT version 1.0; it was resolved in RESULT version 1.1. Added to release notes in October 2000. Tracking number: V&V01386.

When using the transmission sampling module, the Optimize Gain feature sometimes recommended the B Screen and Empty attenuation wheel settings, which are not appropriate for use with the transmission module.

History: This problem occurred in RESULT version 1.0; it was resolved in RESULT version 1.1. Added to release notes in October 2000. Tracking number: V&V01403.

The Y-axis limits for spectral plots in Absorbance units were restricted to positive numbers. This made it difficult to plot a 100% line in Absorbance using fixed Y-axis limits.

History: This problem occurred in RESULT version 1.0; it was resolved in RESULT version 1.1. Added to release notes in October 2000. Tracking number: V&V01436.

In RESULT Operation software, the Manage Workflows dialog box allowed the user to add the same workflow multiple times and to select different options for each entry. When the user tried to select and then run the workflow by choosing Select Workflow, multiple copies of the workflow appeared in the selection list.

History: This problem occurred in RESULT version 1.0; it was resolved in RESULT version 1.1. Added to release notes in October 2000. Tracking number: V&V01437.

The Page Up and Page Down keys did not function when viewing work instructions using RESULT Operation software.

History: This problem occurred in RESULT version 1.0; it was resolved in RESULT version 1.1. Added to release notes in October 2000. Tracking number: V&V00699.

The Instrument Status Report sometimes indicates a communication error occurred. Communication errors occur for three reasons: the instrument is powered off, the cable that runs between the computer and the analyzer is disconnected, or the instrument is too busy to reply to a request. To correct the first two cases, reconnect the cable and turn on the instrument. The third case is temporary and will correct itself.

Recommendation: If the Instrument Status Report contains a communication error and the instrument is running with the cable properly connected, then rerun the Instrument Status Report. If the communication error is gone, it was due to a temporary time out caused by multiple simultaneous requests.

Improvement: We significantly reduced the frequency of communication errors.

History: This problem occurred in RESULT version 1.0; it was improved in RESULT version 1.1. Added to release notes in January 2001. Tracking number: V&V01533.

The operator is unable to view the contents of the service log.

Recommendation: In order to view any of the logs, the operator must have read access to the RESULT database (*.mdb) file.

History: Describes operation in RESULT versions 1.0 – 2.0. Added to release notes in June 2004. Tracking number: V&V03989.

Pirouette is open and then RESULT Integrator is opened. If you browse through a workflow with a Pirouette measure event, then you get a message that only one copy of Pirouette may be open at a time. RESULT Integration closes after the warning message.

Recommendation: This is a known feature of Pirouette. Close RESULT before running Pirouette and close Pirouette before running RESULT.

History: Describes operation in RESULT versions 1.0 – 2.0. Added to release notes in June 2004. Tracking number: V&V03535.

A RESULT user must have read/write privileges to the RESULT database file in order to properly add or view entries in the database.

Recommendation: Insure that all RESULT users have read/write privileges to the RESULT database. The file is typically located in c:{subject} Data\config and is named RESULT.mdb.

To check the file privileges using FAT32 file systems, right-click the database file in Windows Explorer. From the popup menu, select Properties. In the Properties dialog box, verify that the Read-Only check box is cleared.

On NTFS file systems, the file security properties are located on the Security tab, which some users may not be able to access. If your computer uses the NTFS file system, have your Windows administrator give you read/write privileges for the RESULT database folder and file.

History: Describes operation in RESULT versions 1.0 – 1.1. Added to release notes in May 2002. Tracking number: V&V03592.

A RESULT user must have read/write privileges to the RESULT database folder and file in order to view or change settings in the Configure System dialog box.

Recommendation: Have your Windows administrator give you read/write privileges for the RESULT database folder and file. The file is typically located in c:{subject} Data\config and is named RESULT.mdb.

History: Describes operation in RESULT versions 1.0 – 1.1. Added to release notes in May 2002. Tracking number: V&V03593.

You are operating a computer running the Windows NT operating system as a local workstation (network cable is unplugged), but it is configured for networking.

Recommendation: Configure the networking options on your computer according to the recommendations in Installing Your Software.

History: Describes operation in RESULT versions 1.0 – 1.1. Added to release notes in May 2002. Tracking number: V&V03594.

RESULT cannot access PLSplus/IQ method files that files were saved as Read-only.

Recommendation: Turn off the Read-only property of your method file(s) and then rerun the workflow.

History: Describes operation in RESULT version 1.1. Added to release notes in October 2001. Tracking number: V&V02732.

A verification workflow must store a workflow status RESULT to the database. If your verification workflow does not store a passing workflow status RESULT, you will not be allowed to run the associated workflow.

Recommendation: At the end of your verification workflow, add a Check event named “Workflow status” and link it to a Logic specification defining the desired pass/fail condition. Make sure the Check event has the Store Pass/Fail RESULT To Database check box selected and the Logical Test Specification has the Logical Test Is Always False If Workflow Errors Have Been Detected check box selected. See Check events” and “Logical test specifications” in the “RESULT Integration Software” section of your Antaris User’s Guide for more information.

History: Describes operation in RESULT version 1.0. Added to release notes in April 2001. Tracking number: V&V02204.

RESULT uses the same engine as Internet Explorer for displaying and printing reports. When you right click on a graphic image, the software disables the Print option and enables menu items that are specific to graphic images.

Recommendation: To print a report displayed in RESULT software, right click on a portion of the report that doesn’t include a graphic image. Then select a print option from the popup menu.

History: Describes operation in RESULT version 1.0. Added to release notes in April 2001. Tracking number: V&V01920.

RESULT software uses the event logging services of the Windows operating system to track unauthorized attempts to log on to RESULT.

Recommendation: To configure RESULT to track unauthorized attempts to log on or to digitally sign files, configure the Windows event logging service to log unauthorized logon attempts. The event logging service works the same way in RESULT as it does in Windows. For example, you can configure Windows to disable a user account if that user makes too many invalid attempts to log on. The account will be disabled if the user attempts to log on to Windows or RESULT software. See “Windows security features” in the “Software Administration” section of your Antaris User’s Guide for more information.

History: Describes operation in RESULT version 1.0. Added to release notes in January 2001. Tracking number: V&V01603.

Baseline offsets occur when the operator uses different aperture settings to collect the sample and background spectra. When using the software’s default settings to collect transmission spectra using the three-position sample tube holder, the software measures background spectra through the center opening in the sample tube holder which does not have an aperture. If you install an aperture in the sample holder position used to measure a liquid sample, the RESULTing spectrum will have an offset baseline.

Recommendation: If you want to measure a liquid sample using an aperture, install an aperture in both the front and back positions of the sample tube holder and then place the sample tube in one of those positions (front is easiest). Set the Sample Position list box on the sample specification associated with your collection event to match the location of the sample (Front Sample Compartment or Rear Sample Compartment). Set the Position list box on the associated background specification to the other position (Front Sample Compartment or Rear Sample Compartment) and then run the workflow. See the “Sample specifications” and “Background specifications” chapters in the “RESULT Integration Software” section of your Antaris User’s Guide for more information about the Sample Position and Background Position parameters.

History: Describes operation in RESULT version 1.0. Added to release notes in January 2001. Tracking number: V&V01387.

The Collect Simulation Spectrum dialog box (displayed by choosing New Sample For Simulation on the sample specification) allows you to create or select the spectra that will be used for simulated runs of a workflow. The Collect Associated Background Spectrum check box in the Collect Simulation Spectrum dialog box specifies whether a new simulation sample spectrum will include a corresponding background spectrum. This is true whether you collect the simulation sample or select an existing spectral file. If Collect Associated Background Spectrum is selected and you select a simulation spectrum that contains only sample data such as a Single Beam or Interferogram file (by choosing From File in the Collect Simulation Spectrum dialog), when you close the dialog box, the software will not add the spectrum to the Samples For Simulation list box on the sample specification.

Recommendation: If you want to run the workflow in simulation mode using a sample spectrum and its corresponding background spectrum, select a spectral file that contains both a sample and a background interferogram. Most spectral files contain both a sample and a background interferogram. Spectra that are collected with Data Format (located on the collection event) set to Interferogram or Single Beam contain only a sample interferogram.

If you want to run the workflow in simulation mode using an interferogram or single-beam spectrum (Data Format is set to Interferogram or Single Beam), clear the Collect Associated Background Spectrum check box before selecting the simulation spectrum.

History: Describes operation in RESULT version 1.0. Added to release notes in January 2001. Tracking number: V&V01518.

RESULT Operation does not provide proper access privileges to users when the computer or domain name contains a space. Microsoft strongly discourages using spaces when entering computer and domain names in their Windows operating system because Windows does not handle the space correctly in all situations. The Windows operating system presents a warning after a user enters a computer name that contains a space.

Recommendation: Remove the space from your computer or domain name in Windows and then restart the RESULT Operation application. You should also remove any spaces from the user names defined in RESULT Operation software.

History: Problem occurs in RESULT version 1.0. Added to release notes in January 2001. Tracking number: V&V01566.

If you expand or collapse the items displayed in the workflow navigation frame in the RESULT Integration main window and then switch back and forth between the Workflow tab and the Details tab, the software does not retain the previous view. For example, if you select the Workflow tab, select Expand from the toolbar to expand the displayed workflow, switch to the Details tab, and then switch back to the Workflow tab (or vice versa), the view is no longer expanded. Choose Expand again to expand the displayed items.

History: Describes operation in RESULT version 1.0. Added to release notes in October 2000. Tracking number: V&V00690.

Some collection and measurement event parameters are interdependent. If you delete a collection event whose RESULT spectrum is used by a subsequent measurement event, and then create another collection event, add its RESULT spectrum to the measurement event and rerun the workflow, the workflow may produce a measurement error due to inconsistent parameter settings between the collection event and the measurement event or its associated TQ Analyst method.

Recommendation: Use the workflow error text to determine which parameters are inconsistent with the measurement event and then change the collection event parameters to fix the error.

Tip: The workflow wizard will automatically make your collection parameters consistent if you create a measurement event that uses an existing TQ Analyst method when you run the wizard.

History: Describes operation in RESULT version 1.0. Added to release notes in October 2000. Tracking number: V&V01060.

If you change a TQ Analyst method that is linked to a measurement specification in the current workflow, the measurement specification won’t reflect the change until you select another event or specification and then reselect the measurement specification. Let’s say, for example, you are running RESULT Integration and you select a measurement specification that is linked to a TQ Analyst quantitative method and decide to add another component to that method. Then you start TQ Analyst software, add the component and save the method. When you return to RESULT Integration, the new component doesn’t appear in the list of measurements on the measurement specification.

Recommendation: Select another item in the workflow navigation frame, such as the measurement event or another measurement specification, and then reselect the previous measurement specification.

History: Describes operation in RESULT version 1.0. Added to release notes in October 2000. Tracking number: V&V01044.

The software reports a fit value of 0.0 whenever the spectral range for the collection event doesn’t cover the full range of the standards in the associated TQ Analyst method (for example, when the spectral range on the sample specification is 4000 -10000 cm^-1 and the method standards range from 3800 – 12000 cm^-1). If your spectral range is set appropriately, you might see a low fit value but you are unlikely to see a fit value of 0.0, which is the lowest possible fit value. When the spectral ranges of the samples and standards are inconsistent, the software reports a fit value of 0.0 even for spectra that are very similar.

Recommendation: To achieve an appropriate reading for the fit value, change the spectral range for the collection event (located on its associated sample specification) to cover the full range of the standards. In the example above, you would need to change the spectral range for the collection event to 3800-12000 cm^-1.

History: Describes operation in RESULT version 1.0. Added to release notes in October 2000. Tracking number: V&V01214.

When you view Instrument Status under the Maintenance menu in RESULT Operation software, the start date displayed for the validation wheel is the date on which the wheel was calibrated; not the date it was installed.

Recommendation: Use the validation wheel installation date to determine when to re-qualify the validation wheel. That date is noted in the Validation Wheel Standard booklet provided at installation.

History: Describes operation in RESULT version 1.0. Added to release notes in January 2000. Tracking number: V&V01657.

The Build TQ Analyst Method command provides two buttons for defining the method standards: a Browse button and a Select button. The Browse button sets the directory and path that will be used to add standards to the new method; the Select button allows you to specify a base name for adding a group of standards to the method by selecting a representative spectral data file.

Recommendation: Make sure the path points to the same location as the spectral data file you select as your representative standard.

History: Describes operation in RESULT version 1.0. Added to release notes in October 2001. Tracking number: V&V02652.

If you are monitoring a peak location at 5402 cm-1 and you set the y display limits to 5400 to 5404 cm-1, you will see no numbers on the y axis. It appears that the space allowed for the y axis is not wide enough for the number of digits required.

Comment: The problem has been alleviated, but there are some restrictions. For numbers greater than 99, but less than 999, the smallest range of y axis values is 0.05. For numbers greater than 999, but less than 100,000, the smallest range of y axis values is 0.5.

History: This problem was reported in RESULT version 1.1; it was resolved in RESULT version 2.0. Added to release notes in June 2004. Tracking number: V&V02807.

If the cursor is left highlighting the measure event in a given workflow and Build TQ method is selected, the checkbox for automatically link new method to measure event is checked, the new method will not be linked to the measure event.  The cursor must be left on a different event.

Recommendation: Leave the cursor on a an event other than the linked measure event, before selecting the Build TQ Method command from the menu.

History: Problem occurred in RESULT version 1.2-2.0. Added to release notes in June 2004. Tracking number: V&V3636.

An ACLS quant method that has the mean centering option on produces incorrect measurement RESULTs.

Recommendation: Modify the quant method so that either ACLS or mean centering is not required or upgrade to RESULT 1.2 or later.

History: Problem occurred in RESULT versions 1.0 and 1.1. Added to release notes in December 2003. Tracking number: V&V2957. Resolved in RESULT 1.2.

Many Windows 2000 computers support Advanced Power Management. These computers can be set up to enter standby mode after a period of inactivity in order to save power. The device driver used by RESULT software is not currently compatible with standby mode. If the computer enters standby mode when RESULT is running, or if it tries to communicate with the Antaris instrument after leaving standby mode, RESULT stops running.

Recommendation: Disable Standby Mode in the Power Options dialog box of Windows software for all RESULT users. To access the Power Options dialog box, right-click on the Windows desktop and then select Properties. The Display Properties dialog box appears. Select the Screen Saver tab. On the Screen Saver tab, choose the Power button. In the RESULTing dialog box, select the Power Schemes tab. On the Power Schemes tab, set the Turn Off Monitor list box to Never and the Turn Off Hard Disks list box to Never. Choose OK to close the dialog box. Choose OK again to close the Display Properties dialog box.

History: Problem occurred in RESULT version 1.1. Added to release notes in May 2002. Tracking number: V&V03591.

If you have Internet Explorer version 5.5 loaded on your computer, you may have problems printing tables in reports generated in RESULT software when using the HP LaserJet 8000 DN printer. The printer may fail to print a row in a table that crosses a page boundary.

Recommendation: Install Internet Explorer version 4.0 or 5.0.

History: Problem occurs in RESULT version 1.0. Added to release notes in October 2000. Tracking number: V&V01255. This problem was reported to Microsoft and is tracked by Microsoft incident SRZ000816000156.

In RESULT Integration software, when the user changes a setting in a collection event that has Background Frequency set to Once Every Hour or Once Every Four Hours and then either tests the workflow or collects a standard, the software does not collect a new background (or prompt the operator to do so) until the specified background frequency period has elapsed.

Recommendation: Set Background Frequency to Before Every Sample and then either test the workflow or collect a standard. This forces the software to collect a new background before collecting the first sample or standard. Then you are free to use other Background Frequency settings.

History: Problem occurs in RESULT version 1.0. Added to release notes in October 2000. Tracking number: V&V01434.

In RESULT Integration software, when the user collects a simulation spectrum for the tablet analyzer with the Collect Associated Background Spectrum check box selected, sample collection begins immediately following background collection. The software does not allow time for or prompt the user to insert the sample.

Recommendation: Use the tablet analyzer to collect and save the sample and background spectra that will be used for simulated runs of your workflow. Then display the sample specification and choose New in the Samples For Simulation group. In the RESULTing dialog box, use the From File button to add the sample and background files to your workflow.

History: Problem occurs in RESULT version 1.0. Added to release notes in October 2001. Tracking number: V&V02649.

The operator is unable to view the contents of the service log.

Recommendation: In order to view any of the logs, the operator must have read access to the RESULT database (*.mdb) file.

History: Describes operation in RESULT versions 1.0 – 2.0. Added to release notes in June 2004. Tracking number: V&V03989.

Pirouette is open and then RESULT Integrator is opened. If you browse through a workflow with a Pirouette measure event, then you get a message that only one copy of Pirouette may be open at a time. RESULT Integration closes after the warning message.

Recommendation: This is a known feature of Pirouette. Close RESULT before running Pirouette and close Pirouette before running RESULT.

History: Describes operation in RESULT versions 1.0 – 2.0. Added to release notes in June 2004. Tracking number: V&V03535.

A verification workflow must store a workflow status RESULT to the database. If your verification workflow does not store a passing workflow status RESULT, you will not be allowed to run the associated workflow.

Recommendation: At the end of your verification workflow, add a Check event named “Workflow status” and link it to a Logic specification defining the desired pass/fail condition. Make sure the Check event has the Store Pass/Fail RESULT To Database check box selected and the Logical Test Specification has the Logical Test Is Always False If Workflow Errors Have Been Detected check box selected. See Check events” and “Logical test specifications” in the “RESULT Integration Software” section of your Antaris User’s Guide for more information.

History: Describes operation in RESULT version 1.0. Added to release notes in April 2001. Tracking number: V&V02204.

RESULT uses the same engine as Internet Explorer for displaying and printing reports. When you right click on a graphic image, the software disables the Print option and enables menu items that are specific to graphic images.

Recommendation: To print a report displayed in RESULT software, right click on a portion of the report that doesn’t include a graphic image. Then select a print option from the popup menu.

History: Describes operation in RESULT version 1.0. Added to release notes in April 2001. Tracking number: V&V01920.

The Build TQ Analyst Method command provides two buttons for defining the method standards: a Browse button and a Select button. The Browse button sets the directory and path that will be used to add standards to the new method; the Select button allows you to specify a base name for adding a group of standards to the method by selecting a representative spectral data file.

Recommendation: Make sure the path points to the same location as the spectral data file you select as your representative standard.

History: Describes operation in RESULT version 1.0. Added to release notes in October 2001. Tracking number: V&V02652.

RESULT software uses the event logging services of the Windows operating system to track unauthorized attempts to log on to RESULT.

Recommendation: To configure RESULT to track unauthorized attempts to log on or to digitally sign files, configure the Windows event logging service to log unauthorized logon attempts. The event logging service works the same way in RESULT as it does in Windows. For example, you can configure Windows to disable a user account if that user makes too many invalid attempts to log on. The account will be disabled if the user attempts to log on to Windows or RESULT software. See “Windows security features” in the “Software Administration” section of your Antaris User’s Guide for more information.

History: Describes operation in RESULT version 1.0. Added to release notes in January 2001. Tracking number: V&V01603.

Baseline offsets occur when the operator uses different aperture settings to collect the sample and background spectra. When using the software’s default settings to collect transmission spectra using the three-position sample tube holder, the software measures background spectra through the center opening in the sample tube holder which does not have an aperture. If you install an aperture in the sample holder position used to measure a liquid sample, the RESULTing spectrum will have an offset baseline.

Recommendation: If you want to measure a liquid sample using an aperture, install an aperture in both the front and back positions of the sample tube holder and then place the sample tube in one of those positions (front is easiest). Set the Sample Position list box on the sample specification associated with your collection event to match the location of the sample (Front Sample Compartment or Rear Sample Compartment). Set the Position list box on the associated background specification to the other position (Front Sample Compartment or Rear Sample Compartment) and then run the workflow. See the “Sample specifications” and “Background specifications” chapters in the “RESULT Integration Software” section of your Antaris User’s Guide for more information about the Sample Position and Background Position parameters.

History: Describes operation in RESULT version 1.0. Added to release notes in January 2001. Tracking number: V&V01387.

The Collect Simulation Spectrum dialog box (displayed by choosing New Sample For Simulation on the sample specification) allows you to create or select the spectra that will be used for simulated runs of a workflow. The Collect Associated Background Spectrum check box in the Collect Simulation Spectrum dialog box specifies whether a new simulation sample spectrum will include a corresponding background spectrum. This is true whether you collect the simulation sample or select an existing spectral file. If Collect Associated Background Spectrum is selected and you select a simulation spectrum that contains only sample data such as a Single Beam or Interferogram file (by choosing From File in the Collect Simulation Spectrum dialog), when you close the dialog box, the software will not add the spectrum to the Samples For Simulation list box on the sample specification.

Recommendation: If you want to run the workflow in simulation mode using a sample spectrum and its corresponding background spectrum, select a spectral file that contains both a sample and a background interferogram. Most spectral files contain both a sample and a background interferogram. Spectra that are collected with Data Format (located on the collection event) set to Interferogram or Single Beam contain only a sample interferogram.

If you want to run the workflow in simulation mode using an interferogram or single-beam spectrum (Data Format is set to Interferogram or Single Beam), clear the Collect Associated Background Spectrum check box before selecting the simulation spectrum.

History: Describes operation in RESULT version 1.0. Added to release notes in January 2001. Tracking number: V&V01518.

RESULT Operation does not provide proper access privileges to users when the computer or domain name contains a space. Microsoft strongly discourages using spaces when entering computer and domain names in their Windows operating system because Windows does not handle the space correctly in all situations. The Windows operating system presents a warning after a user enters a computer name that contains a space.

Recommendation: Remove the space from your computer or domain name in Windows and then restart the RESULT Operation application. You should also remove any spaces from the user names defined in RESULT Operation software.

History: Problem occurs in RESULT version 1.0. Added to release notes in January 2001. Tracking number: V&V01566.

If you expand or collapse the items displayed in the workflow navigation frame in the RESULT Integration main window and then switch back and forth between the Workflow tab and the Details tab, the software does not retain the previous view. For example, if you select the Workflow tab, select Expand from the toolbar to expand the displayed workflow, switch to the Details tab, and then switch back to the Workflow tab (or vice versa), the view is no longer expanded. Choose Expand again to expand the displayed items.

History: Describes operation in RESULT version 1.0. Added to release notes in October 2000. Tracking number: V&V00690.

Some collection and measurement event parameters are interdependent. If you delete a collection event whose RESULT spectrum is used by a subsequent measurement event, and then create another collection event, add its RESULT spectrum to the measurement event and rerun the workflow, the workflow may produce a measurement error due to inconsistent parameter settings between the collection event and the measurement event or its associated TQ Analyst method.

Recommendation: Use the workflow error text to determine which parameters are inconsistent with the measurement event and then change the collection event parameters to fix the error.

Tip: The workflow wizard will automatically make your collection parameters consistent if you create a measurement event that uses an existing TQ Analyst method when you run the wizard.

History: Describes operation in RESULT version 1.0. Added to release notes in October 2000. Tracking number: V&V01060.

If you change a TQ Analyst method that is linked to a measurement specification in the current workflow, the measurement specification won’t reflect the change until you select another event or specification and then reselect the measurement specification. Let’s say, for example, you are running RESULT Integration and you select a measurement specification that is linked to a TQ Analyst quantitative method and decide to add another component to that method. Then you start TQ Analyst software, add the component and save the method. When you return to RESULT Integration, the new component doesn’t appear in the list of measurements on the measurement specification.

Recommendation: Select another item in the workflow navigation frame, such as the measurement event or another measurement specification, and then reselect the previous measurement specification.

History: Describes operation in RESULT version 1.0. Added to release notes in October 2000. Tracking number: V&V01044.

The software reports a fit value of 0.0 whenever the spectral range for the collection event doesn’t cover the full range of the standards in the associated TQ Analyst method (for example, when the spectral range on the sample specification is 4000 -10000 cm^-1 and the method standards range from 3800 – 12000 cm^-1). If your spectral range is set appropriately, you might see a low fit value but you are unlikely to see a fit value of 0.0, which is the lowest possible fit value. When the spectral ranges of the samples and standards are inconsistent, the software reports a fit value of 0.0 even for spectra that are very similar.

Recommendation: To achieve an appropriate reading for the fit value, change the spectral range for the collection event (located on its associated sample specification) to cover the full range of the standards. In the example above, you would need to change the spectral range for the collection event to 3800-12000 cm^-1.

History: Describes operation in RESULT version 1.0. Added to release notes in October 2000. Tracking number: V&V01214.

When you view Instrument Status under the Maintenance menu in RESULT Operation software, the start date displayed for the validation wheel is the date on which the wheel was calibrated; not the date it was installed.

Recommendation: Use the validation wheel installation date to determine when to re-qualify the validation wheel. That date is noted in the Validation Wheel Standard booklet provided at installation.

History: Describes operation in RESULT version 1.0. Added to release notes in January 2000. Tracking number: V&V01657.

If the cursor is left highlighting the measure event in a given workflow and Build TQ method is selected, the checkbox for automatically link new method to measure event is checked, the new method will not be linked to the measure event.  The cursor must be left on a different event.

Recommendation: Leave the cursor on a an event other than the linked measure event, before selecting the Build TQ Method command from the menu.

History: Problem occurred in RESULT version 1.2-2.0. Added to release notes in June 2004. Tracking number: V&V3636.

An ACLS quant method that has the mean centering option on produces incorrect measurement RESULTs.

Recommendation: Modify the quant method so that either ACLS or mean centering is not required or upgrade to RESULT 1.2 or later.

History: Problem occurred in RESULT versions 1.0 and 1.1. Added to release notes in December 2003. Tracking number: V&V2957. Resolved in RESULT 1.2.

When a comma is used for the number separator instead of a period, (standard setting for European computer configurations), the software incorrectly translates the spectral range settings to numeric values. This causes a collection error in the workflow.

Recommendation: Use the standard spectral range instead of a custom spectral range.

History: Problem occurs in RESULT version 1.0. Added to release notes in October 2001. Tracking number: V&V02566.

The peak location measurement requires three data points to determine the peak location. If you change the resolution so that a specified region no longer contains three data points, the measurement does not produce a RESULT.

Recommendation: Open your analytical method and increase the selected regions so they include at least three data points for all of the resolution settings used with the method.

History: Problem occurs in RESULT version 1.0. Added to release notes in October 2001. Tracking number: V&V01676.

If you set up a QC Compare method to report the class name for the second, third, etc. best matched spectrum, the software reports the correct class name for the best matched spectrum but not for the second, third, etc. best matches. The class names reported for the second, third, etc. best matches are the same as for the best match.

Recommendation: Don’t include the second best match in your report or, if you need to include the second best match, use a different classification technique such as discriminant analysis.

History: Problem occurs in RESULT version 1.0. Added to release notes in October 2001. Tracking number: V&V02340.

If you hold down the Shift key while you drag and then drop a workflow item onto the topmost item in the open workflow, when you run the workflow, the dropped item will not execute and will disappear if you switch between the Details tab and the Workflow tab.

Recommendation: Release the Shift key before you drop a workflow item onto the topmost item in your workflow.

History: Problem occurs in RESULT version 1.0. Added to release notes in October 2001. Tracking number: V&V02389.

Sample prompt is missing when collecting simulation spectra for tablet analyzers.

In RESULT Integration software, when the user collects a simulation spectrum for the tablet analyzer with the collect associated background spectrum option checked, sample collection occurs immediately following background collection. This does not provide an opportunity to insert the sample during the collection of the simulation spectrum.

Recommendation: Uncheck the collect associated background spectrum option, place your sample in the tablet analyzer and click collect. You must also collect at least one background simulation spectrum from the associated background specification. Alternatively you can use the from file option to add simulated spectra to your workflow.

History: Problem occurs in RESULT version 1.0. Added to release notes in October 2001. Tracking number: V&V02649.

The apodization function used by RESULT software contains an error that causes channeling in spectra produced from single-sided interferograms. RESULT is configured to collect single-sided interferograms only when the Resolution parameter on the sample specification is set to 2 cm-1.

Recommendation: Set Resolution to a value other than 2 cm-1.

History: Problem occurs in RESULT version 1.0. Added to release notes in January 2001. Tracking number: V&V01404.

When arranging events in a workflow displayed in the workflow navigation frame of the RESULT Integration main window, if you drag and drop an item to a lower position in the same event group, the software sometimes places the item one position below the specified location.

Recommendation: Switch to the Details tab and then back to the Workflow tab to see the change.

History: Problem occurs in RESULT version 1.0. Added to release notes in January 2001. Tracking number: V&V01420.

If you use the standard tablet analyzer sampling module to collect a spectrum and then align the instrument in RESULT Operation software, the alignment sometimes fails. The failure occurs because the software does not always reset the velocity to the correct value for the main transmission detector before starting the alignment procedure.

Recommendation: If you need to align the instrument and you just finished collecting a spectrum using the standard tablet analyzer, use the Quick Collect feature of RESULT Operation software to collect a spectrum using one of the other sampling modules. When the collection is completed, run the alignment procedure.

History: Problem occurs in RESULT version 1.0. Added to release notes in January 2001. Tracking number: V&V01499.

The Cycle Through Simulation Samples check box on the sample specification is unavailable in the software even though the Samples For Simulation drop-down list contains multiple simulation spectra.

Recommendation: If the Samples For Simulation list box on the sample specification includes multiple entries but the Cycle Through Simulation Samples check box is not available in the software, select another specification or event in the workflow navigation frame and then redisplay the sample specification. The check box should be enabled.