Add a 2nd plot manager class, similar to PlotCollection but that generates a matrix (with a diagonal too optionally) with all the pairwise subset combinations. It will be needed for:
plot_pair
plot_elpd
My idea would be to use the same method names as PlotCollection whenever possible, adding new ones for the other features.
For example:
.map will also exist, and will be mapping over the diagonal which is the only mapping operation that can maintain the method signature. Thus, the diagonal of plot_pair could be populated by calling plot_dist using the PlotMatrix class instead of a PlotCollection.
.map_lower and .map_upper to map functions to the plot below the diagonal (lower triangular matrix) and above. These would have signature .map_xyz(da_x, da_y, <same as .map>) with da_x being the data to be mapped to the x axis (thus selected with the column index) and da_y the data mapped to the y axis.
Add a 2nd plot manager class, similar to PlotCollection but that generates a matrix (with a diagonal too optionally) with all the pairwise subset combinations. It will be needed for:
My idea would be to use the same method names as PlotCollection whenever possible, adding new ones for the other features.
For example:
.mapwill also exist, and will be mapping over the diagonal which is the only mapping operation that can maintain the method signature. Thus, the diagonal ofplot_paircould be populated by callingplot_distusing thePlotMatrixclass instead of aPlotCollection..map_lowerand.map_upperto map functions to the plot below the diagonal (lower triangular matrix) and above. These would have signature.map_xyz(da_x, da_y, <same as .map>)with da_x being the data to be mapped to the x axis (thus selected with the column index) and da_y the data mapped to the y axis.