Violin plot recreation code error
When you make a graph with a violin plot and save it or make a recreation macro for that graph, it generates a code as follows:
ModifyViolinPlot trace=ValueMatrix01,PlotSide2,MarkerSize=2,MarkerColor=(39321,1,31457)
and fails when you reload that file or provoke graph macro.
Apparently, this should be
PlotSide=2.
I suppose this is an error that should be corrected.
Best,
F.K.
IGORVERS:9.01
BUILD:39200
IGORKIND:pro64
FREEMEM:140732166516736
PHYSMEM:34185723904
USEDPHYSMEM:332423168
NSCREENS:1
SCREEN1:DEPTH=32,RECT=0,0,960,640
OS:Microsoft Windows 11 Pro (22H2)
OSVERSION:10.0.22621.1413
LOCALE:US
IGORFILEVERSION:9.0.1.2
Igor Pro Serial number: 67052
Default Igor graphics technology: 3
Screen Resolution: 80
Screen scale factor: 3
Graphics Rendering: Intel(R) Iris(R) Xe Graphics
Qt version (runtime): 5.12.11
Qt version (compiled): 5.12.11
XOPs:
Autosave: ENABLED:0;MODE:2;INTERVAL:2;OPTIONS:15;
FK
Sure enough. I thought I'd found all the bugs in violin plot command generation! Get the fix in the latest nightly build tomorrow. Be sure the get build #39914 or later. Use Help->Igor Pro Nightly Builds to go to the download site.
March 27, 2023 at 10:17 am - Permalink
Thank you for this nightly build that solved the issue.
Another issue: how can I change the general violin style for individual dataset of the trace?
It seems that a command
Build 39920.
March 31, 2023 at 07:45 pm - Permalink
You are correct about BoxWidth- but only for box plots and violin plots on a numeric X axis. If you use a category axis, it works. The code for the per-dataset BoxWidth was all in place, but the drawing code always used data set 0 instead of the correct data set.
Fixed for the next nightly build. Build 39942 or later.
My testing with BandWidth shows that it works as expected. The Edit Bandwidths dialog is hard to use, though. It was invented before I implemented the per-dataset settings in Igor 9. I should alter it to use the same method as the other settings, especially since it doesn't generate a command line. That's just wrong!
April 4, 2023 at 02:30 pm - Permalink