If after calling show on a figure, a plot is added to a subplot and then write is called then the figure is not as expected. This happens for both the backends(similar incorrect figure is drawn)
the device argument is always kept as a file, which indicates saving the figure. Another option is window which is for displaying the figure. This argument can be removed, I will look into this soon.
Plans
solve the bug for consecutive show and write calling
I have booked my visa appointment and I need to travel to Bombay for it and hence I will not be able to work on 11th, 12th and 13th. I will cover for this by working extra after returning.
Yes, I did try it but it had some issues related to calling the init_output_device and stop_output_device functions. I will explain the issues in more detail in todayās call.
Tested with different combinations of the show and write and changing the plots in between
Problems
Suppose I call the write/show function and then add a plot in a subplot without initializing, it doesnāt work. But if it is initialized again, it works. So, it is necessary to initialize again after calling the write/show function.
The same thing happens with matplotlib, initialization is necessary. @v0dro
GR backend does not wait at the show function, suppose I call it two times, it shows the first time for a very short amount of time and then the second one for longer, is there any way to stop it at a show function and allow the user to keep it displaying for however long the user wants and then when a command is given then the code is executed further, @v0dro could you help me with this?
Meeting summary
Summary and To-do list:
Discussed optimizing the show function without having to save the is_initialized state variable
Corrected the tests for plot function, changed the unit of the input of sin and cosine from radians to degrees
Problems
The backend of the plot function uses Line2D(draw_lines) and draw_markers which are already implemented for Magick except for the line types and some marker types.
The plot function currently either plots lines or markers, but ideally, it should do both (if specified)
For the format of fmt argument, the string format should be decided, options are keeping it short like matplotlib or having full strings
There should be different options for marker_fill_color and marker_border_color and line colour
Magick backend can not plot a figure having size 400 cms
I was not able to work yesterday (16 July) as I had to make arrangements for my visa appointment (I have been called again for it). I will be having my visa appointment tomorrow(18 July) and hence wonāt be able to work today and tomorrow due to traveling. However, I will try to complete the blogs during my travel.
Sorry for the inconvenience @v0dro
dot .
plus +
asterisk *
circle O
diagonal_cross x
solid_circle sO
triangle_up ^
solid_triangle_up s^
triangle_down v
solid_triangle_down sv
square q
solid_square sq
bowtie b
solid_bowtie sb
hglass h
solid_hglass sh
diamond d
solid_diamond sd
star s
solid_star ss
tri_up_down ^v
solid_tri_right s>
solid_tri_left s<
hollow_plus h+
solid_plus s+
pentagon p
hexagon hx
heptagon hp
octagon oc
star_4 s4
star_5 s5
star_6 s6
star_7 s7
star_8 s8
vline |
hline _
omark o
@v0dro Some of the marker types of matplotlib differ from Rubyplot and hence these are the characters assigned for each marker type, colour and line type:
I will be unavailable to work from 30th July to 3-4 August due to packing, traveling and shifting to France for my bachelorās thesis.
I had already included this in my timeline and hence my project wonāt be affected.
Sorry for the inconvenience and I will cover up by working extra in the coming weeks. @v0dro