Skip to content
This repository has been archived by the owner on Nov 3, 2021. It is now read-only.

Time estimations and time statistics in continuous scans are wrong #1692

Open
reszelaz opened this issue Sep 22, 2021 · 0 comments
Open

Time estimations and time statistics in continuous scans are wrong #1692

reszelaz opened this issue Sep 22, 2021 · 0 comments

Comments

@reszelaz
Copy link
Collaborator

For example:

Door/zreszela/1 [3]: ascanct mot01 0 10 10 0.1
Operation will be saved in /tmp/scans.h5 (HDF5::NXscan from NXscanH5_FileRecorder)
Scan #31 started at Wed Sep 22 08:27:53 2021. It will take at least 0:00:00
Motor positions and relative timestamp (dt) columns contains theoretical values

 Motor   Velocity[u/s]   Acceleration[s]   Deceleration[s]    Start[u]   End[u] 
 mot01         10              0.1               0.1            -0.5      11.5  

 #Pt No    mot01      ct01       dt   
   0         0        0.1       0.1   
   1         1        nan       0.2   
   2         2        0.1       0.3   
   3         3        nan       0.4   
   4         4        0.1       0.5   
   5         5        nan       0.6   
   6         6        0.1       0.7   
   7         7        nan       0.8   
   8         8        0.1       0.9   
   9         9        nan        1    
   10        10       0.1       1.1   
Correcting overshoot...
Operation saved in /tmp/scans.h5 (HDF5::NXscan)
Scan #31 ended at Wed Sep 22 08:27:55 2021, taking 0:00:01.589567. Dead time 97.0% (setup time 3.0%, motion dead time 97.0%)

The wrong information is:

  • It will take at least 0:00:00
  • Dead time 97.0% (setup time 3.0%, motion dead time 97.0%)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant