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: Point Grey Flea3 areaDetector ImageJ Viewer Problems |
From: | John Dobbins <[email protected]> |
To: | "Zachary A. Brown" <[email protected]>, "[email protected]" <[email protected]> |
Date: | Fri, 2 May 2014 18:57:18 +0000 |
A quick look at the source code for ImageJ shows that it is looking for a UniqueID change, so I don't think ImageJ will work without the Unique ID updating.
John Dobbins
From: [email protected] <[email protected]> on behalf of Zachary Brown <[email protected]>
Sent: Friday, May 02, 2014 2:00 PM To: [email protected] Subject: Re: Point Grey Flea3 areaDetector ImageJ Viewer Problems From more testing:
A camonitor on PG1:image1:ArrayData shows that the values in the array are changing as the camera is moved around, so the array is getting updated.
ImageJ still shows a zero-value array. The image shown from the plugin is 1280x1024 (8-bit) as it should be, but no pixel values.
The Array Counter in for the StdArray increases with the image count, but I did notice that the Unique ID for each array does not change (not sure if this is relevent, have not paid attention to this parameter before).
-Zachary Brown, John Dobbins
On Fri, May 2, 2014 at 1:02 PM, Zachary Brown
<[email protected]> wrote:
|