You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: NEWS.md
+23Lines changed: 23 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,7 @@
3
3
2022-11-11
4
4
5
5
Maintenance:
6
+
6
7
- Revert `size` → `linewidth` migration for now to retain compatibility with older ggplot2 versions
7
8
- Use `inherits` to satisfy CRAN checks
8
9
@@ -11,9 +12,11 @@ Maintenance:
11
12
2022-11-11
12
13
13
14
Enhancements:
15
+
14
16
- Accept `tibble`s in `arrange_venn`, thanks @maximilian-heeg! #159
15
17
16
18
Maintenance:
19
+
17
20
- Pass `width=0.9` to workaround change of behaviour in ggplot2 3.4 overextending the width of bars highlighted with `upset_query`
18
21
- Fix deprecation warnings for ggplot 3.4 `size` to `linewidth` transition
19
22
@@ -22,30 +25,35 @@ Maintenance:
22
25
2021-12-07
23
26
24
27
Bug fixes:
28
+
25
29
- Makes zero-degree intersection size for `intersections='all'` mode follow the same behavior as the bar plot #144
26
30
27
31
# Version 1.3.2
28
32
29
33
2021-12-06
30
34
31
35
Bug fixes:
36
+
32
37
- Enable displaying degree 0 intersection with `group_by='sets'`. The old behavior of not displaying degree zero intersection can be achieved by using `min_degree=1` argument #143
33
38
34
39
# Version 1.3.1
35
40
36
41
2021-08-04
37
42
38
43
Fixes:
44
+
39
45
- use `guide="none"` instead of `guide=FALSE` to silence ggplot2 deprecation warning, thanks @MilouArts! #129
40
46
41
47
# Version 1.3.0
42
48
43
49
2021-06-06
44
50
45
51
Changes:
52
+
46
53
- sets on intersection matrix can now be highlighted using `upset_query()`#115
47
54
48
55
Bug fixes:
56
+
49
57
- alleviate visual glitch of `geom_segment` in intersections matrix showing up with an outline #113
50
58
- fixed aesthetics assigned by `upset_query()` which was sometimes not behaving as expected #123
51
59
@@ -54,23 +62,27 @@ Bug fixes:
54
62
2021-04-25
55
63
56
64
Bug fixes:
65
+
57
66
- fixed metadata order in data frame returned by `arrange_venn()` function #116
58
67
59
68
# Version 1.2.0
60
69
61
70
2021-04-03
62
71
63
72
Bug fixes:
73
+
64
74
-[critical] fixed display order of labels when using `encode_sets=TRUE`#110
65
75
- encoding of set names will now properly work around name conflicts #110
66
76
67
77
Major improvements:
78
+
68
79
- manually specified intersections will now display empty intersections and non-exclusive intersections correctly #109
69
80
- manually specified intersections do not require modifying the `intersect` argument to obtain the intended result any longer #109
70
81
- stripes size and other attributes of underlying `geom_segment()` can now be customised with new function: `upset_stripes()`#111
71
82
- stripes colour and other attributes can now be mapped to data #111
72
83
73
84
Minor improvements:
85
+
74
86
- data.table can be passed instead of data.frame (the conversion will be performed automatically) #105
75
87
- warning will be shown if a vector is provided instead of a list to the `intersections` argument #109
76
88
- when `intersections` argument includes sets not specified in `intersect`, a warning will be issued and execution will proceed as if those were included in `intersect`#109
@@ -81,6 +93,7 @@ Minor improvements:
81
93
2021-01-13
82
94
83
95
New features:
96
+
84
97
- it is now possible to select specific intersections passing `intersections = list('Drama', c('Comedy', 'Romance'))`
85
98
- it is now possible to define custom order of intersections passing `intersections = list('Drama', c('Comedy', 'Romance'))` and `sort_intersections = FALSE`
86
99
@@ -89,6 +102,7 @@ New features:
89
102
2021-01-05
90
103
91
104
Bug fixes:
105
+
92
106
- Major performance and memory use improvements, especially when using `intersections = 'all'`
93
107
- The `max_combinations_n` fail-safe was replaced by a more useful `max_combinations_datapoints_n` with more precise error message
94
108
- The atypical use case of filtering with `max_degree = 0` is now accepted again
@@ -99,6 +113,7 @@ Bug fixes:
99
113
2021-01-04
100
114
101
115
Bug fixes:
116
+
102
117
- Fixed regression of non-observed sets causing "no vector columns were selected" caused by fix addressing #90
103
118
- Reduced length of file names for some test doppelgangers
104
119
@@ -107,6 +122,7 @@ Bug fixes:
107
122
2021-01-04
108
123
109
124
Bug fixes:
125
+
110
126
- Filtering by degree when using non-default mode and `intersections='all'` now correctly accounts for all observations (#89)
111
127
- Empty sets/groups are now correctly removed when filtering with a non-default mode (#90)
112
128
- Missing values are now converted to FALSE and a warning is issued to the user rather than causing an undefined behavior (#88)
@@ -116,6 +132,7 @@ Bug fixes:
116
132
2020-12-30
117
133
118
134
Changes:
135
+
119
136
- Lists with computed sizes are now returned in a single list called `sizes` by `upset_data()`
120
137
- Set sizes are now **not** filtered by default when selecting intersections by `min_*` or `max_*` criteria. Pass `filter_intersections=TRUE` to `upset_set_sizes()` to restore the previous behaviour
121
138
- Union sizes are now calculated before data trimming which provides more accurate ratio estimates
@@ -125,12 +142,14 @@ Changes:
125
142
-`min_max_early` argument is no longer required and was removed
126
143
127
144
New features:
145
+
128
146
- Annotations can now access data for any of the available modes by adding `upset_mode()` layer. By default the annotations are given data corresponding to the same mode as the mode of the passed in the `upset()` call.
129
147
- It is now possible to display all intersections, even if those are not present in the data by passing `intersections='all'` to `upset()`; this is only feasible for <20 sets, but filtering by degree can allow to explore a subset of all intersections when there are many more sets; this is only useful for modes different from the default exclusive intersection.
130
148
- If filtering leads to no intersections, an informative error is shown (#80)
131
149
132
150
133
151
Bug fixes:
152
+
134
153
- Modes passed to `upset()` are now also used for sorting and trimming
135
154
- Size calculation for modes was optimised for better performance
136
155
- User-added layers are now shown on top of `intersection_size()` and `intersection_union()`
@@ -141,20 +160,24 @@ Bug fixes:
141
160
2020-12-20
142
161
143
162
Changes:
163
+
144
164
- Pass metadata to the `ggplot2` when arranging Venn diagram, allowing to map elements aesthetics details
145
165
146
166
# Version 0.9.0
147
167
148
168
2020-12-20
149
169
150
170
New features:
171
+
151
172
- Intersection modes were formalised with the default remaining `exclusive_intersection` (alias `distinct`); additional modes are: `inclusive_intersection` (alias `intersect`), `inclusive_union` and `exclusive_union`; please read the [relevant part of the documentation](https://krassowski.github.io/complex-upset/articles/Examples_R.html#0-2-region-selection-modes) for details (#78).
152
173
- Simple Venn diagrams (for two or three sets) can now be constructed using same input (binary presence data frame) using pseudo geoms: `geom_venn_circle()`, `geom_venn_label_region()`, `geom_venn_label_set()`, `geom_venn_region()` and scales `scale_color_venn_mix()` and `scale_fill_venn_mix()`; while developed mostly for the documentation needs, it provides unique capability of highlighting relevant regions of the Venn diagram and placing observations within appropriate regions (which allows to demonstrate their attributes with appropriate aesthetics mapping).
153
174
154
175
Changes:
176
+
155
177
- Breaking: union size for "empty" intersection is now equal to its size
156
178
157
179
Bug fixes:
180
+
158
181
- Layers added to `upset_set_size()` and `intersection_matrix()` will now always go on top (avoiding geoms being hidden underneath)
159
182
- Declare layer in NAMESPACE to allow basic usage without loading `ggplot2`
160
183
-`upset_query()` will now throw an informative error when the user forgets to pass any aesthetics (#79)
0 commit comments