Opened 9 years ago
Closed 3 months ago
#10466 closed defect (duplicate)
graphics_array does not respect axes, ticks options with matrix_plot objects
Reported by: | ddrake | Owned by: | jason, was |
---|---|---|---|
Priority: | major | Milestone: | sage-duplicate/invalid/wontfix |
Component: | graphics | Keywords: | graphics_array matrix_plot ticks axes |
Cc: | kcrisman, chapoton | Merged in: | |
Authors: | Reviewers: | ||
Report Upstream: | N/A | Work issues: | |
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description
I wrote a worksheet that demonstrates a number of problems with graphics_array
and matrix_plot
:
https://sagenb.kaist.ac.kr:8066/home/pub/22/
Briefly, when using graphics_array
on matrix_plot
objects:
- axes are not drawn correctly,
- ticks options do not work well,
- the rightmost object (in a single row) is drawn a bit smaller than other objects -- I think extra axes_pad is put into that image.
Attachments (1)
Change History (14)
Changed 9 years ago by
comment:1 Changed 9 years ago by
Graphics arrays definitely need to be overhauled. There are some very nice features that recently were added to matplotlib (in 1.0.0, now in Sage) that will make very nice graphics arrays. There is a sage-devel message somewhere about this (someone was asking about rewriting graphics arrays a couple of months ago, IIRC).
comment:2 Changed 9 years ago by
Actually, the subplots feature (listed right below the feature I mentioned above) is probably the easiest to use in making a graphics_array.
comment:3 Changed 9 years ago by
#10291 might take care of the extra axes_pad issue.
comment:4 Changed 9 years ago by
- Cc kcrisman added
comment:5 Changed 6 years ago by
- Milestone changed from sage-5.11 to sage-5.12
comment:6 Changed 6 years ago by
- Milestone changed from sage-6.1 to sage-6.2
comment:7 Changed 6 years ago by
- Milestone changed from sage-6.2 to sage-6.3
comment:8 Changed 5 years ago by
- Milestone changed from sage-6.3 to sage-6.4
comment:9 Changed 2 years ago by
Almost certainly related to #10657 and friends.
comment:10 Changed 6 months ago by
The issues described here are fixed in #27865.
comment:11 Changed 4 months ago by
- Cc fchapoton added
- Milestone changed from sage-6.4 to sage-duplicate/invalid/wontfix
- Status changed from new to needs_review
Now that #27865 is merged in Sage 8.9.beta0, this ticket could be closed as duplicate.
comment:12 Changed 4 months ago by
- Cc chapoton added; fchapoton removed
comment:13 Changed 3 months ago by
- Resolution set to duplicate
- Status changed from needs_review to closed
copy of the worksheet in case the KAIST Sage server isn't working