From: Hironori Ito (hito@rcf.rhic.bnl.gov)
Date: Thu Jan 23 2003 - 15:21:24 EST
Hello, Kris. Regarding brahvo, I have a request on behalf of every BRAHMS shifter. Can you write out current HV conditions in some ascii file? Particularly, if you could write it out in xml format, it might be very good since we can easily overcome the HV setting change (which we do quite often.) Anyway, if you make something like currentHV.xml in operator account whenever a shifter checks brahvo, it would reduce a workload of a shifter tremendously since a shifter is now asked to fill a wire chamber info by hand. (This has about 50 entries.) If there is a current HV condition file, I can easily add a button in E-log to pick up those number without a shifter input. And, this is exactly how I do for "start shift" and "end shift" since KO wrote a lot of scripts to moniter DAQ and Magnet conditions. Hiro Kris Hagel wrote: > Christian, > As for your last question regarding the logging facilities. I saw what > in retrospect looks kind of like a skeleton for having logging > facilities, but is not activated in any way. I also converted that to > the signal/slot stuff and it compiles and it had "interesting" code in > it. But it is still not used. > > Kris > > Christian Holm Christensen wrote: > >> Hi Kris, >> hagel@comp.tamu.edu wrote concerning >> brahvo converted to signal/slot mechanism [Sun, 19 Jan 2003 21:09:57 >> -0600] >> ---------------------------------------------------------------------- >> >> >>> Hello, >>> This is kind of late, but I thought I would let you know. I did >>> surgery on bravho as per request of Flemming to change the gui >>> message handling to the signal/slot mechanism of root. >>> >> >> >> BraHVo :-) >> >> >> >>> It certainly cleaned up the coding immensely. I checked it out as >>> much as I could in offline mode to make sure the signals and slots >>> were behaving properly, but my talent in creating bugs out of thin >>> air is unsurpassed. >> >> >> Nah, I don't believe you. >> >> >>> I will therefore need to check it in a controlled way using live >>> detectors. This is clearly inconvenient given that we now have >>> beam. But the thought was to do this test at some "quiet" time with >>> no beam unless we get lucky and that doesn't happen. >>> In the meantime, if you checkout brahvo to make a "simple" change, >>> be aware that many things changed to convert it to the signal/slot >>> mechanism and those changes are checked into the repository. >> >> >> Doing a >> cvs co brahvo cd brahvo cvs update -A -P -d >> usually does the trick. >> >> >>> I will announce as soon as we manage to do a convincing test. >>> >> >> >> OK. >> Did you incorporate the logging facilities that was planned, but Claus >> never did? We (Claus, Konstantin, Anders and I) sort of figured that >> it had to be a multi-thread to do that properly. I made an example >> using ROOT's threads, which you can find at >> http://cholm.home.cern.ch/cholm/root/#loggui >> should you want to do this. It's rather old, so it may not compile >> anymore, but the design should hold. >> Yours, >> ___ | Christian Holm Christensen |_| | >> ------------------------------------------------------------- >> | | Address: Sankt Hansgade 23, 1. th. Phone: (+45) 35 35 96 91 >> _| DK-2200 Copenhagen N Cell: (+45) 24 61 85 91 >> _| Denmark Office: (+45) 353 25 305 >> ____| Email: cholm@nbi.dk Web: www.nbi.dk/~cholm >> | | >> >> >> >> >
This archive was generated by hypermail 2.1.5 : Thu Jan 23 2003 - 15:13:15 EST