Thanks as ever to Kit Baum, a new package vennbar is now available from SSC from Tim Morris and myself.
This completes publication (making public) of a trio of commands from a project started on 8 September 2022 in the Fitzroy Tavern, Charlotte Street, London during the London Stata Users' meeting .
The trio started with jaccard (a small deal)
https://www.statalist.org/forums/for...lable-from-ssc
and continued with upsetplot (a bigger deal than jaccard).
https://www.statalist.org/forums/for...lable-from-ssc
vennbar honours John Venn (he of Venn diagrams) but not in the observance: as with upsetplot the aim is to present alternatives to annotated Venn diagrams showing counts (more generally abundances) of overlapping subsets.
So why are there two commands? The answer is twofold. First, a piece of personal history that you need not care about. Second, a more fundamental reason.
When Tim showed me upset plots -- at this point I must have forgotten Andrew Musau 's fine post at https://www.statalist.org/forums/for...mptoms-graphic -- my very first reaction was that an existing command already was available, which was nonsense, so no more of that. My first reaction after that was that I didn't much like the design and thought that you could get something as good or even better just by working out frequencies and feeding them to graph hbar -- or if you prefer graph bar or graph dot So that is how vennbar .started, Later it become clear that some things are easier or work better with a wrapper of that kind -- while other things are easier or work better with a wrapper for graph twoway, which is how upsetplot started. Also, I like the upsetplot design much more than I did. It's a platitude of monumental proportions that you have to try graph types out on real data, not just read about them,
So much for the personal history. The fundamental reason that remains is that there are two commands because they are wrappers for quite different Stata graph commands and none has a monopoly of virtues.
At this point I am going to assume that if this interests you, then either you have looked at the recent posts first linked above, or you can now do that to get more flavour. In any case, the help file for vennbar really is quite detailed. So, just a few token graphs by way of a taster.



PS Tim asked earlier -- If one command is called upsetplot why is this one not called vennbarchart? to which the only answer I could think of was that I didn't want to keep typing vennbarchart.
This completes publication (making public) of a trio of commands from a project started on 8 September 2022 in the Fitzroy Tavern, Charlotte Street, London during the London Stata Users' meeting .
The trio started with jaccard (a small deal)
https://www.statalist.org/forums/for...lable-from-ssc
and continued with upsetplot (a bigger deal than jaccard).
https://www.statalist.org/forums/for...lable-from-ssc
vennbar honours John Venn (he of Venn diagrams) but not in the observance: as with upsetplot the aim is to present alternatives to annotated Venn diagrams showing counts (more generally abundances) of overlapping subsets.
So why are there two commands? The answer is twofold. First, a piece of personal history that you need not care about. Second, a more fundamental reason.
When Tim showed me upset plots -- at this point I must have forgotten Andrew Musau 's fine post at https://www.statalist.org/forums/for...mptoms-graphic -- my very first reaction was that an existing command already was available, which was nonsense, so no more of that. My first reaction after that was that I didn't much like the design and thought that you could get something as good or even better just by working out frequencies and feeding them to graph hbar -- or if you prefer graph bar or graph dot So that is how vennbar .started, Later it become clear that some things are easier or work better with a wrapper of that kind -- while other things are easier or work better with a wrapper for graph twoway, which is how upsetplot started. Also, I like the upsetplot design much more than I did. It's a platitude of monumental proportions that you have to try graph types out on real data, not just read about them,
So much for the personal history. The fundamental reason that remains is that there are two commands because they are wrappers for quite different Stata graph commands and none has a monopoly of virtues.
At this point I am going to assume that if this interests you, then either you have looked at the recent posts first linked above, or you can now do that to get more flavour. In any case, the help file for vennbar really is quite detailed. So, just a few token graphs by way of a taster.
PS Tim asked earlier -- If one command is called upsetplot why is this one not called vennbarchart? to which the only answer I could think of was that I didn't want to keep typing vennbarchart.
Comment