2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024 | Index | 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | pvMonitor questions |
From: | Mark L Rivers via Core-talk <core-talk at aps.anl.gov> |
To: | "core-talk at aps.anl.gov" <core-talk at aps.anl.gov> |
Date: | Wed, 3 Nov 2021 17:52:34 +0000 |
Folks, I’m trying to understand the –q option to pvMonitor. This is the help output: TahoeU18:/corvette/home/epics/scratch> /corvette/usr/local/epics-devel/base-7.0.5/bin/linux-x86_64-ub18/pvmonitor -h Usage: pvmonitor [options] <PV name>... options: -h: Help: Print this message -V: Print version and exit -r <pv request>: Request, specifies what fields to return and options, default is '' -w <sec>: Wait time, specifies timeout, default is 5.000000 second(s) -p <provider>: Set default provider name, default is 'pva' -M <raw|nt|json>: Output mode. default is 'nt' -v: Show entire structure (implies Raw mode) -q: Quiet mode, print only error messages -d: Enable debug output deprecated options: -q, -t, -i, -n, -F: ignored -f <input file>: errors Output details: -m -v: Monitor in Raw mode. Print only fields marked as changed. -m -vv: Monitor in Raw mode. Highlight fields marked as changed, show all valid fields. -m -vvv: Monitor in Raw mode. Highlight fields marked as changed, show all fields. -vv: Get in Raw mode. Highlight valid fields, show all fields. example: pvmonitor double01 It appears to have contradictory information. It says that –q is quite mode and prints only error messages, and then it says that –q is deprecated. When I run with –q it is not quiet, it outputs the same information as it does without –q. TahoeU18:/corvette/home/epics/scratch> /corvette/usr/local/epics-devel/base-7.0.5/bin/linux-x86_64-ub18/pvmonitor -r "value" -q 13SIM1:Pva1:Image 13SIM1:Pva1:Image structure union value float[] [912250,912251,912252,912253,912254,912255,912256,912257,912258,912259,912260,912261,912262,912263,912326,… It would be really nice to be able to limit the output of pvmonitor, similar to the -# option in camonitor. I don’t care if it subscribes to the entire array, I just want to limit the processing time in pvmonitor to convert to ASCII, and
to limit the amount of output it produces. Can someone also explain what the –Mraw flag to pvget and pvmonitor does? I don’t see any difference in the output with and without that option: TahoeU18:/corvette/home/epics/scratch> /corvette/usr/local/epics-devel/base-7.0.5/bin/linux-x86_64-ub18/pvget -r "value" 13SIM1:Pva1:Image | more 13SIM1:Pva1:Image structure union value float[] [912445,912446,912447,912448,912449,912450,912451,912452,912453,912454,912455 TahoeU18:/corvette/home/epics/scratch> /corvette/usr/local/epics-devel/base-7.0.5/bin/linux-x86_64-ub18/pvget -r "value" -Mraw 13SIM1:Pva1:Image | more 13SIM1:Pva1:Image structure union value float[] [912445,912446,912447,912448,912449,912450,912451,912452,912453,912454,912455, Thanks, Mark |