Software Status Bulletin
G2211AA Metabolite ID Software rev. B.01.01
Revision Log:
|
Revision Date |
Reason For Update |
|
1/15/2008 |
Final release |
1. Overview
The purpose of this document is to list known problems in the software and any known workarounds or recovery paths.
2. Known Problem Summary
The following is a summary of the known problems in the software. This is not an exhaustive list, but is a list of the problems a customer is most likely to encounter. This list cross-references items in our Defect tracking database.
|
SCR # |
Title |
|
10930 |
Some Table Columns Are Too Narrow On Printer After Autosizing the Column |
|
11036 |
Runtime Error in Report Generation When '.' Not Used as Decimal Separator |
|
11151 |
Issues with Detector Saturation in MFE |
|
11248 |
Memory leak on loading new sessions |
3. Known Problems Detailed Description
The following is the detailed descriptions of the known problems in the Personal Pesticide Database software. This section includes more extensive information from our defect tracking database. This section also includes any known workarounds or recovery paths.
|
SCR #10930 |
|
Title |
Some Table Columns Are Too Narrow On Printer After Autosizing the Column |
|
Description |
In the fragments table, the width of some columns that were too narrow, were adjusted by auto-sizing. After making this adjustment, a printout or print preview of the table was done. The columns were still too narrow to show the values correctly.
Workaround:
If the table width is has been adjusted manually, this problem does not occur. |
|
SCR #11036 |
|
Title |
Runtime Error in Report Generation When '.' Not Used as Decimal Separator |
|
Description |
If a period ( . ) is not used as a decimal separator (defined in the regional settings in Windows Control Panel), report generation crashes with a runtime error. |
|
SCR #11151 |
|
Title |
Issues with Detector Saturation in MFE |
|
Description |
In metabolite search, it may happen that a compound is saturated. If in such a case the maximum charge state in MFE is greater than 1, the compound is not found by MFE. If the maximum charge state is set to 1 in MFE, the compound will be found by MFE but this may cause incorrect assignments for compounds with multiple charges. In addition, the compound peak may be 'split'.
Workaround:
Dilute and rerun the sample. Remember that by diluting the sample, lower level peaks may not appear. |
|
SCR #11248 |
|
Title |
Memory leak on loading new sessions |
|
Description |
Each additional LoadSession of a running instance adds an additional ~10MB of memory. The user observed also a serious performance impact as a consequence after 3 days of continuous uptime of the application.
Workaround:
Close the application and restart it once a day.
|
Appendix A. Glossary
|
Term / Acronym |
Definition |
|
UI |
User Interface. The visual representation of the software with which a user interacts. |