| 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: Strange problem with areaDetector driver |
| From: | Jörn Dreyer via Tech-talk <tech-talk at aps.anl.gov> |
| To: | Mark Rivers <rivers at cars.uchicago.edu> |
| Cc: | tech-talk at aps.anl.gov |
| Date: | Thu, 28 May 2020 09:29:58 +0200 |
Am Mittwoch, 27. Mai 2020, 16:10:26 CEST schrieb Mark Rivers via Tech-talk:
> > Closed the OPI screen that shows the image. Now the number of threads is
> > constant. System load is at normal level.
> When you saw the threads and high system load did you use top -H to see
> whether the threads with high CPU load were CSS threads or IOC threads? I
> suspect they are CSS threads.
No they are all started from the IOC. After 300 threads spawned I decided to stop the IOC. I used
ps -eLF | grep st.cmd | wc
> > Will need some time to gat that going. Java on my system seems to have
> > problem with the code.
> ImageJ on both Linux and Windows comes with its own version of Java in the
> ImageJ/jre directory, so it should be completely independent of your system
> version of Java. Get the latest version of the ImageJ zip file and install
> it in your own directory so you don't need to worry about system
> permissions, etc.
I got it working, but there seems to be a problem that only half of the image is intrerpreted correctly. The ArrayType is UInt16 instead of UInt8. Will need to find out teh reason for that.
Regards,
J�/p>
>
> Mark
>
>
>
> -----Original Message-----
> From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of J�Dreyer via
> Tech-talk Sent: Wednesday, May 27, 2020 8:56 AM
> To: tech-talk at aps.anl.gov
> Subject: Re: Strange problem with areaDetector driver
>
> Am Mittwoch, 27. Mai 2020, 14:46:09 CEST schrieb Mark Rivers:
> > Hi J�
> >
> > > I ran into a severe problem in the image readout handler.
> > >
> > > When calling doCallbackGenericPointer() the IOC creates every time a
> > > couple of new threads and consumes lot of CPU power ( 300% on a
> > > quad core).
> >
> > First a few questions:
> >
> >
> > Is this Linux or Windows?
>
> Linux
>
> > What frame rate are you using?
>
> 0.5 Hz
>
> > What plugins are running?
>
> Only NDStdArray.
>
> > Is the CS-Studio GUI on the same machine as the IOC or a different
> > machine?
>
> On the same machine
>
> > The first thing to establish is whether the problem is the
> > areaDetector IOC or the CS-Studio client. I suggest you do the following:
> >
> >
> > - Disable all plugins except NDPluginStdArrays for testing.
>
> Done,
>
> > - Exit CS-Studio so there is no display client running. What is the
> > CPU load under those conditions?
>
> Closed the OPI screen that shows the image. Now the number of threads is
> constant. System load is at normal level.
> > - Try the ImageJ viewer instead of CS-Studio for testing. Does that
> > also have the problem?
>
> Will need some time to gat that going. Java on my system seems to have
> problem with the code.
>
> Regards,
>
> J�/p>
>
> > Mark
> >
> >
> >
> >
> >
> > ________________________________
> > From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of J�/p>
> > Dreyer via Tech-talk <tech-talk at aps.anl.gov> Sent: Wednesday, May 27,
> > 2020 7:03 AM
> > To: tech-talk at aps.anl.gov
> > Subject: Strange problem with areaDetector driver
> >
> > Hello,
> >
> > currently I have a very strange problem in a code I'm developing to
> > read out cameras from ZWO. I ran into a severe problem in the image
> > readout handler. When calling doCallbackGenericPointer() the IOC creates
> > every time a couple of new threads and consumes lot of CPU power ( 300%
> > on a quad core). So after a very short time the system becomes
> > unresponsive and has to be switched off. The image is 3520*4656 bytes in
> > size and is in monochrome mode, so UInt8 as data type.
> >
> > In a GUI (CS-Studio) that is displaying the image data as Intensity
> > graph I observe a "disconnect" state for every cycle of the image,
> > once the NDStdArray has been enabled. In between it shows "No data".
> >
> > Has anybody seen such behavior before? Any ideas welcome how to search
> > for the reason of this.
> >
> > Regards,
> >
> > J�Dreyer