From bc3a5990a7e940ffe6b3d967cd3ff578135e1467 Mon Sep 17 00:00:00 2001 From: rivers Date: Mon, 30 Jul 2012 13:59:07 +0000 Subject: [PATCH] Added note about memory leak on Perkin Elmer optical frame grabbers when averaging 2^N frames git-svn-id: https://subversion.xor.aps.anl.gov/synApps/areaDetector/trunk@14918 dc6c5ff5-0b8b-c028-a01f-ffb33f00fc8b --- documentation/areaDetectorReleaseNotes.html | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/documentation/areaDetectorReleaseNotes.html b/documentation/areaDetectorReleaseNotes.html index f9aa010..a743fc8 100755 --- a/documentation/areaDetectorReleaseNotes.html +++ b/documentation/areaDetectorReleaseNotes.html @@ -32,7 +32,11 @@
  • Added an additional ImageMode="Average". In this mode NumImages frames are averaged in the Perkin Elmer driver. This is useful for long acquisition times, because the maximum acquisition time that the hardware supports in Internal trigger mode is - 5 seconds.
    • + 5 seconds. NOTE: There is a bug in the current Perkin Elmer SDK library which causes + a memory leak if the number of frames to average is 2^N (2,4,8,16, etc.) on optical + interface frame grabbers. This problem can be worked around by average a different + number of frames (7 rather than 8 for example). It will be fixed in the next release + of their SDK.
  • Removed the maxSizeX, maxSizeY, and dataType arguments from the PerkinElmerConfig() command. These values are now determined automatically. This means that startup scripts need to be modified.