Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  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  <20182019  2020 
<== Date ==> <== Thread ==>

Subject: ADSimDetector and ADURL - runtime issues with FFT and HDF5
From: "Heesterman, Peter J via Tech-talk" <tech-talk@aps.anl.gov>
To: "EPICS Tech-Talk (tech-talk@aps.anl.gov)" <tech-talk@aps.anl.gov>
Date: Mon, 19 Nov 2018 14:23:37 +0000
Hi,
 
I’m seeking to use these modules with HDF5 data archiving.
Accordingly, I’ve been looking at the iocHDF5Test within ADSimDetector, and focused on test5.sh.
 
I’m working with an Ubuntu 18.04 VM.
I have:
    areaDetector and ADCore R3-3-2
    ADSupport R1-5
  ADViewers R1-2
    ADURL R2-2
    Asyn4-33
    Base 3.15.6
 
There are some issues that I need to raise:
 
a. st.cmd in ADSimDetector hasn’t been updated to reflect module paths – in particular lines like
        dbLoadRecords("$(ADCORE)/db/simDetector.template","P=$(PREFIX),R=cam1:,PORT=$(PORT),ADDR=0,TIMEOUT=1"), where the file is no longer in ADCore.
    This is easily corrected. Actually, I believe st_base.cmd from iocSimDetector can just be used.
 
b. When I run the sim detector and try to visualise with ImageJ, I get green on both 13SIM1:image1 and 13SIM1:image2.
    But, I don’t get any image displayed for either.
 
c. I note an error:
    NDPluginDriver::connectToArrayPort Error calling pasynManager->connectDevice to array port FFT1 address 0, status=3, error=asynManager:connectDevice port FFT1 not found.
 
    Could my (b) have anything to do with this error?
    I understand that image2 would be the FFT of the simulated data generated for image1?
 
d. I am able to create a HDF5 file (for either ADSimDetector or ADURL) as requested by the test5.sh script (I cloned the logic of this for the ADURL module).
    These files are large (>~100MB), and clearly contain the simulated and URL data, respectively.
    I’m able to open the file(s) with the hdfview application (after closing the IOC, to avoid any file write/read share issues).
    But, I’m unable to view any of the data because there are no attribute nodes under the ‘test5_001.h5’ root, in the viewer.
 
    Viewing the ‘properties’ on the ‘test5_001.h5’ node in hdfview, shows no attributes and no datasets.
 
    I refer to http://cars9.uchicago.edu/software/epics/NDFileHDF5.html , which I’ve studied in some detail.
 
I am able to visualise data from the ADURL module, quite normally.
 
What is it that I’m missing?
 
Many thanks,
 
Peter.
 
 

Attachment: iocURLDriver.log
Description: iocURLDriver.log

Attachment: iocHDF5Test.log
Description: iocHDF5Test.log


Navigate by Date:
Prev: Re: EPICS Application Package J. Lewis Muir
Next: FW: ADSimDetector and ADURL - runtime issues with FFT and HDF5 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  <20182019  2020 
Navigate by Thread:
Prev: job opportunities at ORNL Hartman, Steven M. via Tech-talk
Next: FW: ADSimDetector and ADURL - runtime issues with FFT and HDF5 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  <20182019  2020 
ANJ, 19 Nov 2018 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·