diff --git a/documentation/RoperDoc.html b/documentation/RoperDoc.html index 9225184..46b470b 100755 --- a/documentation/RoperDoc.html +++ b/documentation/RoperDoc.html @@ -385,8 +385,7 @@ roperConfig(const char *portName, int maxBuffers, size_t maxMemory);

The following is an example st.cmd startup script:

- 
-< envPaths
+  
< envPaths
 errlogInit(20000)
 
 dbLoadDatabase("$(AREA_DETECTOR)/dbd/roperApp.dbd")
@@ -460,24 +459,63 @@ create_monitor_set("auto_settings.req", 30,"P=13ROPER1:,D=cam1:")
     

       RoperFile.adl

     RoperFile.png
+  

+    WinView is program that the Roper driver is controlling via Microsoft
+    COM.
+  

+  

+    

+      WinView program from Roper Scientific

+    WinView.png

   

     Performance measurements

   

     The following measurements were done to demonstrate the performance that can be
     obtained with the areaDetector Roper driver. These measurements were made with a
-    CoolSnap-EZ detector which has 1392x1040 pixels. The EPICS IOC was running on the
-    same Windows PC as WinView. The acquisition time was 0.1 second.

+    CoolSnap-HQ2 detector which has 1392x1040 pixels. The acquisition time was 0.01
+    second. The overhead per image in the table below is the total time to acquire the
+    data set minus 1.00 seconds (the acquisition time) divided by 100. Acquisitions
+    were done in 2 modes:

+  
    
+    
  1. In the first mode NumImages=100 and NumAcquisitions=1, i.e. the data were all
+      collected into a single SPE file. In this mode the time per image is really controlled
+      by the acquisition time and readout time. At the end of the acquisition there is
+      then a delay, perhaps in copying the data from one buffer to another. The acquisition
+      time in this mode is the time from when acquire was started until WinView reported
+      acquisition was complete and the write to disk began. The additional time to write
+      the file to disk is also listed.
    2. 
+    
  2. In the second mode NumImages=1 and NumAcquisitions=100, i.e. the data were collected
+      into 100 SPE files. This is equivalent to pressing the Acquire button in WinView
+      100 times. There is additional overhead per image that arises from downloading parameters
+      to the camera and in creating a new display window in WinView. In this mode the
+      test was done both with the EPICS AutoSave PV set to 1 (which effectively does a
+      WinView "Save As" operation for each file), and with AutoSave set to 0, which does
+      not write disk files at all. The acquisition time listed is with AutoSave on, i.e.
+      saving 100 disk files. Interestingly it was generally faster to collect the
+      data with AutoSave on than with it off! The time to save the 100 disk files is thus
+      actually negative, i.e. it took that much longer to collect the data sets without
+      saving the disk files. The reason for this is unclear, but it seems to be something
+      internal to WinView.
    3. 
+  

   
+        
+          Mode
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        
+      
+      
+        
+        
+        
+        
+        
+        
+        
+      
+      
+        
+        
+        
+        
+        
+        
+        
+        
+      
+      
+        
+        
+        
+        
+        
+        
+        
+        

     
       

         
           Binning
+          Image dimensions
         
           Image size
         
-          Time for 10 images (ADNumImages=10)
+          Acquisition time for 100 images
         
           Overhead per image
+          File size
+          File saving time
       

       

         
@@ -487,42 +525,128 @@ create_monitor_set("auto_settings.req", 30,"P=13ROPER1:,D=cam1:")
           1392x1040
         
         
-          50.0
+          2827 KB
         
         
-          4.00
+          1 SPE file
         
+          29.49
+          0.28
+        
+          276 MB
+        
+          20.04
       

       

         
-          2x2
+          1x1
         
         
-          696x520
+          1392x1040
         
         
-          46.2
+          2827 KB
         
         
-          3.62
+          100 SPE files
         
+          80.67
+          0.79
+          2.76 MB
+        
+          -3.62
       

       

         
-          3x3
+          2x2
+          696x520
+          707 KB
         
         
-          1024x1024
+          1 SPE file
         
         
-          Sequential
+          10.27
+          0.09
+          69 MB
         
         
-          29.0
+          4.86

+          2x2
+          696x520
+          707 KB
         
         
-          1.90
+          100 SPE files
         
+          46.14
+          0.45
+          0.71 MB
+        
+          -.72

+          4x4
+          348x260
+          177 KB
+        
+          1 SPE file
+        
+          4.48
+          0.03
+          17 MB
+        
+          1.40

+          4x4
+          348x260
+          177 KB
+        
+          100 SPE files
+        
+          36.59
+          0.35
+          0.18 MB
+        
+          0.69
       

     
   

@@ -538,7 +662,13 @@ create_monitor_set("auto_settings.req", 30,"P=13ROPER1:,D=cam1:")
       add to the EPICS interface if needed in the future. Settings that EPICS does not
       control and which do not need to be frequently changed can simply be set via the
       WinView GUI.
-    
  • Reading data files back into WinView is not currently supported.
    • 
+    
  • Reading data files back into WinView is not currently supported. This may be added
+      in a future release.
    • 
+    
  • The values of ADNumImagesCounter ($(P)$(R)NumImagesCounter_RBV) and ADNumExposuresCounter
+      ($(P)$(R)NumExposuresCounter_RBV) are not updated during acquisition. This is because
+      WinView does not appear to be correctly returning the values of the EXP_CSEQUENTS
+      and EXP_CACCUMS parameters. The reason for this is under investigation and hopefully
+      will be fixed in a future release.
    • 
     
  • The following items are hardcoded in the driver. They can be changed by recompiling
       if necessary.
       
      
@@ -548,6 +678,12 @@ create_monitor_set("auto_settings.req", 30,"P=13ROPER1:,D=cam1:")
           acquisition is complete.
       
    
     
    • 
+    
  • There is a bug in Windows XP SP2 that causes WinView to hang after about 1600
+      acquisitions have been performed in a single WinView session. Acquisition means
+      the equivalent of pressing the Acquire button, regardless of how many images were
+      collected in a single acquisition. This would typically mean that 1600 SPE files
+      had been saved. After 1600 acquisitions it is necessary to exit WinView and restart
+      it. This problem is fixed in SP3 for Windows XP, and in Microsoft Vista.
    •