I found the old message below in the mailing list archives; I find I am experiencing exactly the same problem, with RHEL4, StripTool 2.5.12.0, and base 3.14.10 on a 64-bit machine.
To be precise, if more than one curve is displayed, then clicking on the name of a curve to the right of the StripTool plot will cause that curve - and only that curve - to be displayed as if it was on the 0 to 100 scale. All other curves will be displayed as if the minimum and maximum of the plot was set according to its Min-Max settings, even though the Y axis will always nonetheless read 0 to 100. I also see the same error message that Mr. Lynch describes.
Has anyone else experienced this problem and found a way around it?
On the chance that it might be related, I also notice that toggling buttons on and off via the right-click menu tends to cause segmentation faults. Here's a gdb backtrace:
#0 0x000000307094d031 in _XtCountVaList () from /usr/X11R6/lib64/libXt.so.6
#1 0x000000307094ca8e in XtVaGetValues () from /usr/X11R6/lib64/libXt.so.6
#2 0x000000000041da47 in callback (w=0x30709541a9, client=0x6c9250, call=Variable "call" is not available.
) at ../StripGraph.c:477
#3 0x0000003070913fa5 in XtCallCallbackList () from /usr/X11R6/lib64/libXt.so.6
#4 0x000000306bfa0184 in _XmDragUnderAnimation () from /usr/X11R6/lib64/libXm.so.3
#5 0x000000306c05abd7 in _XmIsSubclassOf () from /usr/X11R6/lib64/libXm.so.3
#6 0x0000003070925a08 in XtConfigureWidget () from /usr/X11R6/lib64/libXt.so.6
#7 0x000000306bfb400b in XmeConfigureObject () from /usr/X11R6/lib64/libXm.so.3
#8 0x000000306bfb0b04 in XmCreateFileSelectionDialog () from /usr/X11R6/lib64/libXm.so.3
#9 0x000000306bfb138f in XmCreateFileSelectionDialog () from /usr/X11R6/lib64/libXm.so.3
#10 0x000000306c05ac2b in _XmIsSubclassOf () from /usr/X11R6/lib64/libXm.so.3
#11 0x0000003070925a08 in XtConfigureWidget () from /usr/X11R6/lib64/libXt.so.6
#12 0x000000306bfb400b in XmeConfigureObject () from /usr/X11R6/lib64/libXm.so.3
#13 0x000000306bfb0b04 in XmCreateFileSelectionDialog () from /usr/X11R6/lib64/libXm.so.3
#14 0x000000306bfb108a in XmCreateFileSelectionDialog () from /usr/X11R6/lib64/libXm.so.3
#15 0x000000306c05ae97 in _XmIsSubclassOf () from /usr/X11R6/lib64/libXm.so.3
#16 0x0000003070924f5c in _XtMakeGeometryRequest () from /usr/X11R6/lib64/libXt.so.6
#17 0x0000003070939943 in XtSetValues () from /usr/X11R6/lib64/libXt.so.6
#18 0x000000307094bc07 in XtVaSetValues () from /usr/X11R6/lib64/libXt.so.6
#19 0x000000000041059d in PopupMenu_cb (w=Variable "w" is not available.
) at ../Strip.c:3494
#20 0x0000003070913fa5 in XtCallCallbackList () from /usr/X11R6/lib64/libXt.so.6
#21 0x000000306bfdc0c9 in XmCreatePushButton () from /usr/X11R6/lib64/libXm.so.3
#22 0x000000306bfdd7e8 in XmCreatePushButton () from /usr/X11R6/lib64/libXm.so.3
#23 0x000000306bfb42ac in _XmDispatchGadgetInput () from /usr/X11R6/lib64/libXm.so.3
#24 0x000000306c070c90 in _XmMenuBtnUp () from /usr/X11R6/lib64/libXm.so.3
#25 0x0000003070948591 in _XtMatchAtom () from /usr/X11R6/lib64/libXt.so.6
#26 0x0000003070948b9e in _XtMatchAtom () from /usr/X11R6/lib64/libXt.so.6
#27 0x00000030709492d9 in _XtTranslateEvent () from /usr/X11R6/lib64/libXt.so.6
#28 0x0000003070922058 in XtDispatchEventToWidget () from /usr/X11R6/lib64/libXt.so.6
#29 0x000000307092277a in _XtOnGrabList () from /usr/X11R6/lib64/libXt.so.6
#30 0x0000003070922998 in XtDispatchEvent () from /usr/X11R6/lib64/libXt.so.6
#31 0x000000000040cef3 in Strip_go (the_strip=Variable "the_strip" is not available.
) at ../Strip.c:1431
#32 0x0000000000423508 in StripTool_main (argc=2, argv=0x7fbffff0f8) at ../StripTool.c:152
#33 0x000000306aa1c3fb in __libc_start_main () from /lib64/tls/libc.so.6
#34 0x00000000004073ea in _start ()
#35 0x0000007fbffff0e8 in ?? ()
#36 0x000000000000001c in ?? ()
#37 0x0000000000000002 in ?? ()
#38 0x0000007fbffff405 in ?? ()
#39 0x0000007fbffff446 in ?? ()
#40 0x0000000000000000 in ?? ()
-Kevin Anderson
> Subject: StripTool Y range
> From: "LYNCH, Damien" <[email protected]>
> Date: Thu, 9 Aug 2007 16:05:28 +1000
> Hi,
>
> Has anyone run across a problem with StripTool 2.5.12.0 having trouble
> getting the Y range correct on the graph?
>
> When I specify a PV in the controls dialog the Min and Max values displayed
> there do not match the Y-min and Y-max values on the graph. The Y axis on
> the graph is always 0 to 100. Even if I modify Min and Max in the Curves tab
> of the controls dialog the graph will not change the Y axis range from 0 to
> 100.
> The following error is written to the console with the same period as the
> graph redraw interval:
>
> ==== StripTool Xt Warning Handler ====
> Warning: Axis: minVal is greater than or equal to maxVal
>
> I see this problem when I compile it under OpenSuse 10.1, Linux 2.6, Base
> 3.14.9 on a 64-bit machine. I've compiled the same version of StripTool on
> another machine (RedHat 9, Linux 2.4, Base 3.14.8.2 on a 32-bit machine) and
> the graphs are drawn fine.
>
>
> Thanks,
> Damien Lynch
> Accelerator IT Systems Engineer
> Australian Nuclear Science and Technology Organisation
> PMB 1, Menai NSW 2234
> T 02 9717 3662
> F +61 2 9717 3257
> www.ansto.gov.au
- Navigate by Date:
- Prev:
areaDetector R1-5 released Mark Rivers
- Next:
RE: StripTool Y range Kevin Anderson
- 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
- Navigate by Thread:
- Prev:
Re: Intelligent Picomotor Control Modules from New Focus David Kline
- Next:
RE: StripTool Y range Kevin Anderson
- 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
|