wchargin
commented
4 years ago Is the consensus that we need to use the URL?
I was imagining that we wanted this to be in the URL because people will share links and expect the colors to be shared as well, to avoid confusion when discussing the charts. But I could be convinced otherwise, and I could also be convinced to start with it in local storage and see if that works for people. It’s true that that gives more flexibility about the representation.
it seems to be BSD
BSD 3-Clause is okay: https://opensource.google/docs/thirdparty/licenses/#notice
So here's the new plan. […]
This sounds fine to me.
How would we feel about a "dynamic" palette which would simply choose the n most divergent colors where n is the number of runs?
One problem with this is that the number of runs grows over time, so this would mean that as new data loads the colors for existing runs change. We currently go to some lengths to avoid this: e.g., we sort runs in order of start time, rather than alphabetically, so that the ordering is time-stable. Any ideas on how to address this?
dgrahn
manivaradarajan
martinpopel
stephanwlee
sharvil
liusida
psybuzz
jettero
TevenLeScao
pierre-nedelec
drmeerkat
As discussed in #288 and #449, it is difficult to choose one color palette that suits everyone in all situations. If there are many runs and I select just some of them (with a regex or toggling individual runs), I quite often end up with e.g., red, red, orange, red and I cannot distinguish the runs especially if the curves are crossing each other. I suggest to add a drop-down color picker (e.g. using http://jscolor.com/) to choose a color for each run. I plan to use this especially before posting TensorBoard screenshots to my colleagues.