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 2025 | 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 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: ADSpinnaker |
From: | Mark Rivers <[email protected]> |
To: | "'Engbretson, Mark S.'" <[email protected]>, "[email protected]" <[email protected]> |
Date: | Thu, 27 Sep 2018 17:53:54 +0000 |
Note that there is not official release of areaDetector/ADSpinnaker yet. There are number of things on my to-do list before I release it. In particular I have not tested
on Linux because I have not had access to an Ubuntu 16 or 18 system. I do now have a triple boot system with Windows 10, Centos 7, and Ubuntu 16 so I can test cameras with the identical hardware and 3 different OS. I have not had a chance to work on this
system yet. Note also that I am thinking of refactoring ADSpinnaker, ADVimba (new driver for AVT/Prosilica cameras), and aravisGigE. These are all drivers for GenICam cameras, and
there is a lot of duplicated code. I have made a proposal to create a new ADGenICam base class from which all 3 of these drivers would derive: https://github.com/areaDetector/areaDetector/issues/36
Mark From: Engbretson, Mark S. <[email protected]> Mark? Any insight as to why an ADSpinnaker might be throwing “2018/09/27 11:46:47.654 ADSpinnaker::grabImage error GetImageStatus returned 9” error messages? Seems to happen no matter if someone is collecting really, really slow images or fast in continuous mode. If one is collecting a fixed number of images, you don’t get an image when these messages are generated, but nothing shows dropped
frames. 9 = “Image Data is incomplete”, BTW. For 10,000 images (66 FPS), this may happen 5-10 times, but at 1 FPS, good chance of still getting that error within the first 100 images.
|