Special meeting - follow up to PPP 187
Notes:
* detect if JSON is already parsed -- maybe such a feature would be useful
* 3D histogram, how big the cubes are? the two implementations result in different cubes sizes - there are a few different ways the 3D histograms are, Serguei - will check, may be related to some draw options -- is it really the size or is it the volume? Volume of the cubes must be proportional to the content -- Serguei will check (now he understands the context)
* dummy div is needed in THPainter or Latex - S: nobody requested such thing before so it was not implemented, so maybe now it could be looked at? (request should be made and this can be implemented)
Stefan: context: this is needed to make everything work in the virtual reality
Nested histograms
3D -- how do you show 2 histograms?
there should be some examples of how to do it - Serguei will follow up, documentation already exists and there are some existing demos
the task will be to see if the C++ and jsroot part can go hand in hand
communicate via issues in the GH repo or root forum
Naming conventions:
3D version -- we need to agree how to call everything
canvas -> environment
pad -> scene
redraw problem: drawing needs to be completed first before the next one starts
******************************************************
THnSparse slowdown
histv7 - will be a data structure, this will not include the visualisation directly, there will an integration step in between
Jonas: how sparse is the THnSparse? less than 5% filled makes sense for the sparse histogram? Martin: it is really needed for us to have THnSparse, it is impossible to have THn at the beginning as this will not fit in the memory at the beginning -- at the end we only look at the parts of the THnSparse. THnSparse is mainly for mapping and it is dynamic.
Stephan: what about doing mapping outside of the THnSparse?
NDMSPC and ROOT histv7
bin content type needs to be something is what can count - that's why a pointer can't be the bin content type