Experimental Physics and Industrial Control System
|
From: Matteo C. <matteo603 at hotmail.it>
Sent: Monday, May 4, 2020 2:33 AM
To: Engbretson, Mark S. <engbretson at anl.gov>
Subject: R: Synchronization and saving frame rate
thank you for the numerous and useful answers.
Probably Mr. Engbretson answer is the most suited for what I need: it allows to obtain directly what I need, i.e. 1 images for every 10 frames, even if it doesn't seem the cleanest way. I'll try
that.
Now another question comes to my mind: since in the other 9 frames there is information I need (namely the average of the array), would it be possible through the scatter plugin to send one frame
with the total array to say a JPEG plugin to save directly images, and the other 9 with the attributes I want to save and WITHOUT the image array to a HDF5 file to save these attributes?
Wouldn’t a quick-and-dirty way to fake this effect be by using the NDPluginScatter plugin to fan out those 10 images , only 1 of which actually generates a file and the other 10 just go to something like the nullfileplugin so that no file
is actually generated?
hope you are all safe and sound.
I need some help to solve a synchronization problem using Areadetector and its Plug-ins.
We would need to get different pieces of data from a camera and a Picoscope (Oscilloscope). The idea is to get data from the Picoscope and the average of the image at a certain rate, and the image
itself at a 10th of this rate. I was wondering if there's an option to save via JPEG or HDF5 (which take care also of the time synchronization of the two) at different rates than the rate acquisition of the StdArray: for example if the frame rates of the camera
and the Picoscope are at 10frames/s (we want an image for every second, and we want 10 sample of picoscope/average image per image), the image is saved every second and the picoscope/average of image 10 times per second. The reason is that we do not need that
many images but mainly we are interested in the Picoscope and image average and we want to save some space.
|
- Replies:
- RE: Synchronization and saving frame rate Mark Rivers via Tech-talk
- References:
- Synchronization and saving frame rate Matteo C. via Tech-talk
- Navigate by Date:
- Prev:
EPICS Qt 3.7.3 [SEC=UNOFFICIAL] STARRITT, Andrew via Tech-talk
- Next:
RE: Synchronization and saving frame rate Mark Rivers via Tech-talk
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
<2020>
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
defining debug in modules/libcom/src/osi/epicsGeneralTime.c in epics-base leads to compilation error for TestIoc junkes via Tech-talk
- Next:
RE: Synchronization and saving frame rate Mark Rivers via Tech-talk
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
<2020>
2021
2022
2023
2024
|
ANJ, 04 May 2020 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|