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: XSPRESS3 hdf5 problems |
From: | Mark Rivers via Tech-talk <[email protected]> |
To: | 'John Dobbins' <[email protected]> |
Cc: | "[email protected]" <[email protected]> |
Date: | Thu, 23 Jan 2020 16:27:04 +0000 |
Hi John, Ø
I have contacted Quantum. I thought that while waiting to hear from them it would make sense to build an IOC from source. On github I see Ø
epics-modules/xspress3 The IOC that Quantum distributes is ancient, using areaDetector R1-9-1. That is the one I recommend you use. Matt Newville in our group here at the APS is maintaining it. It is working with the latest version of ADCore, ADSupport, etc. It uses NDPluginROIStat for ROI statistics. There are new OPI screens. Mark From: Tech-talk <[email protected]>
On Behalf Of John Dobbins via Tech-talk All, I have a new 5 channel Quantum Xspress3 data readout unit which when taking multiple frames will start generating hdf5 related error messages at what seems like random (will acquire
between a few or thousands of frames before generating errors). Once these messages start they seem to continue until the IOC segfaults. repeating pair of error messages on the IOC console:
This IOC is a binary that comes with the detector. I have contacted Quantum. I thought that while waiting to hear from them it would make sense to build an IOC from source. On github I see epics-modules/xspress3 and quantumdetectors/xspress3-epics forked from the above. Any advice on which i should go with? Any suspicions regarding the hdf5 errors? Thanks, John Dobbins Research Support Specialist Cornell High Energy Synchrotron Source Cornell University |