Is the Eve Event Display still supported?

This may be a too-generic or ill-informed question for this forum, but I’ll give it a try:

I’d like to develop an event display for an experiment I’m working on. Since I’m familiar with ROOT in general (I used to be known for my ROOT tutorial), I thought of delving into the Eve Event Display.

When I look in the tutorials, I see that none of the code is commented. There isn’t even a "Start here’ or README file to suggest which examples might be appropriate for self-instruction.

Even the simplest examples can be cryptic. For example, geom_cms.C is among the simplest ones, but there’s no explanation of why the geometry is divided and read in three different nodes (TRK, CALO, MUON), or what the different “SetVisLevels” do. The geom_atlas.C basically does the same thing (INNE, CENT, OUTE). Why? No answers.

Many of the examples refer to files and sites which no longer exist. This suggests to me that no one is currently maintaining the tutorial files.

When I look in this forum, most of the Eve-related posts are over a decade old.

When I look for documentation elsewhere, I can’t find any. Certainly there’s nothing in the ROOT Reference Guide apart from the most cursory description of the classes. There’s lots of pretty pictures, but not much more.

Has Eve fallen off the cliff of relevance? Should I be looking elsewhere for an event display package? Or do I have to bite the bullet and write my own from scratch?

Or (perhaps more likely) is there some tutorial or course out there somewhere, and my web-fu isn’t strong enough to find it?


ROOT Version: 6.36.04
Platform: macosxarm64


Hi,

EVE is not maintained since a long time.
We now developing new web-based REve which should provide similar functionality.
You can find some examples in $ROOTSYS/tutorials/visualisation/eve7/ directory

And definitely @matevz and @alja can give you more details.

Regards,
Sergey

I tried a couple of REve examples within eve7. I didn’t pursue them because:

  • The REve classes are in namespace ROOT::Experimental, which I assume means that they’re “not ready for prime time.” At least, that’s the case in the eve7 tutorials in ROOT 6.36.04.

  • My memory is probably playing tricks on me, but I thought “REve” was the precursor to Eve, the one originally developed by ALICE. I came to this (incorrect?) conclusion because the name/prefix REve is used in the circa 2008 papers linked on the ROOT Event Display page.

  • The REve examples are web-based, as you said. When I tried them, instead of opening a window in the default web browser I set in Mac OS (Vivaldi) it opened them in Chrome instead. I don’t want to use Chrome for a number of reasons.

  • A web-based toolkit sounds fine if you’re running ROOT on your laptop. It’s not a great solution if you’re running ROOT on a remote computer. For all the flaws of X11, it’s designed for exactly that.
    This is not unique to REve: ROOT’s web-based solutions when run on a remote system either run the web browser on the remote system, or they require ssh port forwarding (e.g., the rootssh script) to get them to use a browser on the local computer. I’d rather tell my users “To run the event display, login to central.nevis.columbia.edu and type evd”, instead of “You’ll have to install ROOT your laptop, then copy 120 GB of our data files in order to display run=1707 event=2022.”

What I take away from Sergey’s response is that there is no current ROOT-based event-display mechanism. Is that correct? Beyond that, even when there was, there’s no documentation for it?

Hi,

REve is completely new development and has nothing to do with old event display of ALICE

Chrome used as default web browser in root, but you always can switch to any other starting
root --web=safari tutorials/hsimple.C

REve is still experimental, but there are plans to finalize API soon. Here @matevz and @alja can give much better overview when such consolidation will take place.

In my mind it is other way around. It is big pain to run GL-based applications on remote X11 displays. And even you manage to configure everything right - it always will be slow. With web-based solution you always have option to run your display locally when application runs on remote server - either using rootssh or just providing special server instance which can serve requests from many users. Prototype of such system exists since several years for CMS event display.

REve is event display framework which provided by ROOT. Unfortunately, there is no much documentation. But I hope this will be improved soon.

Regards,
Sergey

The command

root --web=safari $(root-config --tutdir)/visualisation/eve7/event_demo.C

does indeed work on my Mac, but

root --web=vivaldi $(root-config --tutdir)/visualisation/eve7/event_demo.C

does not. However, my faulty memory worked for once: I recalled another topic in which you addressed this: Rootssh from Mac OS with Homebrew fails with netcat. Looking through that gave me the correct solution, at least for MacOS:

root --web=open $(root-config --tutdir)/visualisation/eve7/event_demo.C

This will open whatever web browser I’ve selected as the default in my system (Vivaldi, Brave, Zen, whatever).

The fun part: I remember three years ago that there was some documentation on rootssh. Now there no longer is, or at least I couldn’t find it. This loops back to my complaint about lack of documentation for Eve and REve.

While everything should be documented, of course, I think it’s more important that the rootssh documentation be restored/re-written/revised than REve, at least in the short term!

There is no special docu - just help which you get when type rootssh without args.
But probably it is necessary to have somewhere in our docu.

@seligman

I will add a bit more information to Sergey’s reply about the REve development stage. We’ve done a lot of development since 6.36.04 to migrate functionality from TEve (X11 implementation) to REve (web graphics implementation).

For my development setup, I use a fixed port, disable automatic window opening, and turn off the authentication key. This helps me reuse URL multiple times. Here is an edited example of the jets.C demo.

I want to list a couple more options for remote use, in addition to the rootssh script.

  • create ssh tunnel, e.g.

  • Using a SOCKS proxy: Enable a SOCKS proxy on Mac in System Preferences, or use Chrome with the socks-proxy option:

    • ssh -N -D 6666 lxplus.cern.ch
      Start Chrome with the above proxy; one might want to use a dedicated profile:
      google-chrome --proxy-server=socks://localhost:6666
  • Open system port on the remote host

Please, keep us updated with experience of web event display in your environment so we can effectively work on documentation.

Alja

If you’re hoping to get something from me about my experience with developing a web-based event display, you’re going to have wait a long time… if ever.

I tried creating a conda environment with ROOT 6.40.06. The ROOT-based program suite I’ve developed over the past four years (GramsSim if you’re curious) developed many problems. The compilation process changed. The Geant4 portion of the suite lost its visualization capabilities (issues with Qt versions). The changes in the ROOT_GENERATE_DICTIONARY macro required rewriting my CMakeLists.txt files. An existing ROOT-based visualization application stopped working (in the sense that it now only shows a black screen).

All this from changing ROOT 6.36 to ROOT 6.40!

From my perspective as an ignorant developer who knows nothing about OpenGL and Qt5/6, something that worked has turned into something broken and complicated; what the heck is a “SOCKS proxy”, and how do I teach that to students who only understand Python notebooks?

I’ve looked at Sergey’s webgui guide and my heart sinks. How do I translate my 2000-line application to this structure? Would it work, or would I still get a black screen?

I understand where Sergey is coming from, and in spirit I agree with it. X11 is on its way out and web-based alternatives are compelling. But I have no idea how to make this transition.

Obviously, I’ve strayed far from my original question of a ROOT-based event display. There appears to be a massive amount of work on my part to adapt the visualization in my project to the latest ROOT. I have to decide whether it’s worth the effort to maintain any visualization capabilities in my program suite, much less go to the effort of trying to code a new event-display program.