> I'm interested in any feedback on which plotting style people prefer (or any other
> aspects of the rootana webdisplay).
I personally prefer the ROOT style. It seems that they are equivalent, but it is possible to
change to log scale in X, Y (and Z for 2D) by simple click right on the plot. I cannot find
this feature in plot-ly. Unfortunately, it comes back to linear at the next refresh it seems...
Also, I prefer the 1D histograms as colums, not a segments.
I have added some additional features to the example webdisplay that we have for
ROOTANA data (where we are displaying rootana data through ROOT THttpServer).
The main improvement to the display is that I added the ability to plot the data
using the JSROOT package . Previously I had used different packages (dygraphs
and plot-ly) for plotting. The JSROOT plots are not obviously superior, though they
do present data in a more familiar way (at least for me). The rootana webdisplay
currently allows you to switch between the two different styles.
You can see a working example of the webdisplay here:
All details on setting up that example are here:
I'm interested in any feedback on which plotting style people prefer (or any other
aspects of the rootana webdisplay).
> ROOT v6 has been around for a while now, finally got around to test it with ROOTANA.
The problems with loading rdict.pcm files and c++ .h header files is resolved, ROOTANA should be fully usable with ROOTv6:
Put this in your login file:
- LD_LIBRARY_PATH is used to search for rdict.pcm files.
- ROOT_INCLUDE_PATH is used to find the c++ .h header files.
ROOT v6 has been around for a while now, finally got around to test it with ROOTANA.
a) using root-v6-06-08
b) everything compiles and links
c) the example applications - i.e. display_example.exe - seem to run correctly
d) user applications linked against librootana.a show a problem loading the ROOTANA rdict.pcm files.
Failure to load the rdict.pcm files seems to prevent some functions, at least in the GUIs.
I do not fully understand how ROOT is supposed to find these files and I am asking for help on the ROOT forum.
In the mean time, there is a work around:
- symlink all rdict.pcm files into same place as the executable: ln -sv $ROOTANASYS/*/*.pcm .
- symlink all (many) .h files into the same place (this is a bit extreme): ln -sv $ROOTANASYS/include/* .
I have finished a test implementation of a web display for MIDAS online
monitoring. I have a test version of this display running here:
The main features of this way of display MIDAS data are:
- An online rootana program that produces ROOT TH1 and TH2 histogram.
- A web server provided by ROOT (THttpServer) which serves up the histogram
information in JSON format.
I have written a more detailed description of this procedure (including some
known deficiencies) which is available here
should be noted that this procedure is only weakly coupled to rootana; you could
pretty easily take any program that makes ROOT histograms, add this THttpServer
provided by THttpServer (which incidentally is available in newer versions of
both ROOT5 and ROOT6).
I am imagining the following scenario for using these web tools:
- we use this web-based display of online MIDAS data for a sub-set of key plots
for shift-takers and for remote experts to provide quick feed-back (when you are
on the bus, at the bar, on the ski hill).
- we continue to use some rootana GUI that provides a complete set of all the
online MIDAS plots, as well as the ability to play-back data in MIDAS files.
I can imagine a situation where we might only use the web tools, though I
haven't yet thought seriously about how to allow a play-back of MIDAS files
through web display.
Hopefully people find these tools useful. I'm interested in all feed-back.
This is a new forum for discussing the rootana MIDAS analyzer.
Code is on bitbucket:
There is also an associated wiki for rootana documentation