ID |
Date |
Author |
Topic |
Subject |
125
|
26 Sep 2006 |
Konstantin Olchanski | Info | New version coming up... |
> FYI, I am presently working in an updated version of roody.
The new version of Roody has been commited.
It has been tested only on Linux (SL4.3) and while we are shaking out the new bugs,
all are welcome to try it and report any problems. It should not eat your data.
If the new version does not work for you at all, the old version was preserved as
an SVN branch, accessible using this SVN command:
svn checkout svn://ladd00.triumf.ca/roody/branches/roody-v1 roody-v1
K.O. |
128
|
26 Sep 2006 |
Konstantin Olchanski | Info | New version coming up... |
> > FYI, I am presently working in an updated version of roody.
>
> The new version of Roody has been commited.
>
> It has been tested only on Linux (SL4.3) and while we are shaking out the new bugs,
> all are welcome to try it and report any problems. It should not eat your data.
>
> If the new version does not work for you at all, the old version was preserved as
> an SVN branch, accessible using this SVN command:
> svn checkout svn://ladd00.triumf.ca/roody/branches/roody-v1 roody-v1
(the email notification for this message did not work at first, trying again)
K.O. |
144
|
19 Oct 2010 |
Konstantin Olchanski | Info | roody good on macos 10.6.4 |
For the record, ROODY svn rev 236 builds and runs on MacOS 10.6.4 with ROOT 5.26.00c. K.O. |
151
|
24 May 2012 |
Konstantin Olchanski | Info | removed ROOTSYS check |
I removed the checks for ROOTSYS being the same at run time and compilation time.
These checks never worked right and are unnecessary since we always install roody
separately for each experiment and ROOTSYS settings are always consistent.
K.O. |
146
|
25 May 2011 |
Jackie Glister | Forum | Refresh problem when drawing groups |
I'm having a Roody refresh problem: when I draw groups in online mode the entire
canvas is refreshed with the most recently selected single histogram, instead of
the group. I used svn to install the most recent version (svn checkout
svn://ladd00.triumf.ca/roody/trunk roody). Any help would be greatly appreciated! |
147
|
23 Feb 2012 |
Exaos Lee | Forum | How to access the SVN repo anonymously? |
I found that the SVN repo is forbidden for anonymous users now. |
148
|
13 May 2012 |
Konstantin Olchanski | Forum | How to access the SVN repo anonymously? |
> I found that the SVN repo is forbidden for anonymous users now.
Please use username "svn", password "svn", per instructions here:
http://www.triumf.info/wiki/DAQwiki/index.php/DaqSvn
K.O. |
149
|
24 May 2012 |
Konstantin Olchanski | Forum | How to access the SVN repo anonymously? |
> I found that the SVN repo is forbidden for anonymous users now.
It is possible that you are referencing the SVN repo using the "svn:" access method. This access method was recently
disabled.
Please switch to the "https:" method (username/password svn/svn) using this command:
cd .../roody
svn switch --relocate svn://ladd00.triumf.ca/roody https://ladd00.triumf.ca/svn/roody
K.O. |
150
|
24 May 2012 |
Konstantin Olchanski | Forum | test |
test of Roody forum email notification. K.O. |
62
|
30 Sep 2004 |
Matthias Schneebeli | Bug Report | anoncvs account not working anymore |
anoncvs account is not working anymore.
Please fix that.
Thanks
Matthias |
63
|
30 Sep 2004 |
Pierre-André Amaudruz | Bug Report | anoncvs account not working anymore |
Access to Roody from anonymous is restored:
cvs -e ssh -d anoncvs@midas.triumf.ca:/usr/local/cvsroot checkout roody
pwd: anoncvs |
64
|
30 Sep 2004 |
Konstantin Olchanski | Bug Report | anoncvs account not working anymore |
> Access to Roody from anonymous is restored:
> cvs -e ssh -d anoncvs@midas.triumf.ca:/usr/local/cvsroot checkout roody
> pwd: anoncvs
What was the fix? I do not think it was ever broken, except for the name change from "miroodas" to "roody", which I could not document until Pierre restored this Elog forum
a few hours ago. K.O. |
101
|
27 Oct 2005 |
Stefan Ritt | Bug Report | Various item when installing ROODY |
Hi,
I tried to compile ROODY, and got following problems/issues:
- I see ROODY requires root V3.10.02, ROME requires root >=4, so I will never be able to compile the two packages together with one root installation. Is that true? Since we are already at root 5.04, it might be time to migrate ROODY to newer versions of ROOT...
- The Makefile.win is under roody/, Makefile is under roody/src, not very consistent, there is no "INSTALL" or "COPYING" file which is kind of GNU standard
- I tried to compile ROODY under windows, after having installed root 3.10, but it misses the libxml/ subtree
- For the non-expert users it would be good to supply a windows executable of roody, this way the don't have to bother with compiling
Best regards,
Stefan |
108
|
19 Dec 2005 |
Konstantin Olchanski | Bug Report | reconnect after midas analyzer is restarted? |
When I restart the MIDAS analyzer, it looks like ROODY detects that the connection is broken, but does not reestablish it. Can somebody look into this? K.O. |
112
|
16 Mar 2006 |
Matthias Schneebeli | Bug Report | Compiling under windows |
Hi,
when I try to compile roody under windows I get following errors.
c:\roody>nmake -f Makefile.win
Microsoft (R) Program Maintenance Utility, Version 7.00.9466
Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.
cl /D "OS_WINNT" /GX /GR /Ic:\roody\include /Ic:\roody\..\mxml /IC:\ROOT\include /I. /c /Foobj/Roody.obj src/Roody.cxx
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 12.00.8804 for 80x86
Copyright (C) Microsoft Corp 1984-1998. All rights reserved.
Roody.cxx
c:\roody\include\Roody.h(388) : error C2039: 'size_t' : is not a member of 'std'
c:\roody\include\Roody.h(391) : error C2039: 'size_t' : is not a member of 'std'
c:\roody\include\Roody.h(396) : error C2039: 'clear' : is not a member of 'basic_string<char,struct std::char_traits<char>,class std::allocator<char> >'
src/Roody.cxx(754) : error C2061: syntax error : identifier 'xml'
src/Roody.cxx(755) : error C2228: left of '.rdstate' must have class/struct/union type
src/Roody.cxx(762) : error C2296: '<<' : illegal, left operand has type 'class std::basic_ofstream<char,struct std::char_traits<char> > &(__cdecl *)(void)'
src/Roody.cxx(762) : error C2297: '<<' : illegal, right operand has type 'char [9]'
src/Roody.cxx(768) : error C2296: '<<' : illegal, left operand has type 'class std::basic_ofstream<char,struct std::char_traits<char> > &(__cdecl *)(void)'
src/Roody.cxx(768) : error C2297: '<<' : illegal, right operand has type 'char [12]'
src/Roody.cxx(769) : error C2296: '<<' : illegal, left operand has type 'class std::basic_ofstream<char,struct std::char_traits<char> > &(__cdecl *)(void)'
src/Roody.cxx(769) : error C2297: '<<' : illegal, right operand has type 'char [11]'
src/Roody.cxx(770) : error C2296: '<<' : illegal, left operand has type 'class std::basic_ofstream<char,struct std::char_traits<char> > &(__cdecl *)(void)'
src/Roody.cxx(770) : error C2297: '<<' : illegal, right operand has type 'char [11]'
src/Roody.cxx(771) : error C2296: '<<' : illegal, left operand has type 'class std::basic_ofstream<char,struct std::char_traits<char> > &(__cdecl *)(void)' |
133
|
18 Feb 2008 |
Jimmy Ngai | Bug Report | Roody kills MIDAS Analyzer |
Hi All,
I'm running Roody with MIDAS 2.0.0 and ROOT 5.14e on Scientific Linux 4.4.
When Roody is monitoring the online histograms on Localhost, there are two
possibilities that Roody will kill the MIDAS Analyzer:
1) quiting Roody
2) unzoom a histogram when auto-refresh is on
Any ideas?
Best Regards,
Jimmy |
134
|
02 Mar 2008 |
Exaos Lee | Bug Report | ROODY kills analyzer too!! |
I compiled roody svn231 with ROOT 5.18.00 and gcc 4.1 on Debain Linux 4.0 (AMD64).
I tested the roody with the "examples/experiment" in MIDAS svn4124 and
encountered the following error:
Error in <TFile::TFile>: file /last.root does not exist
*** Break *** segmentation violation
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1090525536 (LWP 17985)]
0x00000000004114e6 in root_server_thread (arg=<value optimized out>) at src/mana.c:5333
Current language: auto; currently c++
(gdb) next
[midas.c:2416:bm_validate_client_index,ERROR] Invalid client index 1 in buffer 'SYSMSG'. Client name '', pid 0 should be 17973
0x00002b800b8a5460 in sighandler () from /opt/ROOT/Versions/Current/lib/libCore.so.5.18
(gdb) next
Single stepping until exit from function _Z10sighandleri,
which has no line number information.
Cannot remove breakpoints because program is no longer writable.
It might be running in another process.
Further execution is probably impossible.
0x00002b800b8a546e in sighandler () from /opt/ROOT/Versions/Current/lib/libCore.so.5.18
ptrace: 娌℃湁閭d釜杩涚▼.
(gdb) next
Single stepping until exit from function _Z10sighandleri,
which has no line number information.
Cannot remove breakpoints because program is no longer writable.
It might be running in another process.
Further execution is probably impossible.
0x00002b800b8a546e in sighandler () from /opt/ROOT/Versions/Current/lib/libCore.so.5.18
ptrace: 娌℃湁閭d釜杩涚▼.
(gdb) next
Single stepping until exit from function _Z10sighandleri,
which has no line number information.
Cannot remove breakpoints because program is no longer writable.
It might be running in another process.
Further execution is probably impossible.
0x00002b800b8a546e in sighandler () from /opt/ROOT/Versions/Current/lib/libCore.so.5.18
The system information is as the following:
$ uname -a
Linux daq-heg 2.6.18-5-amd64 #1 SMP Sat Dec 22 20:43:59 UTC 2007 x86_64 GNU/Linux
$ gcc -v
Using built-in specs.
Target: x86_64-linux-gnu
Configured with: ../src/configure -v
--enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr
--enable-shared --with-system-zlib --libexecdir=/usr/lib
--without-included-gettext --enable-threads=posix --enable-nls
--program-suffix=-4.1 --enable-__cxa_atexit --enable-clocale=gnu
--enable-libstdcxx-debug --enable-mpfr --enable-checking=release
x86_64-linux-gnu
Thread model: posix
gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)
$ root-config --config
linuxx8664gcc --prefix=/opt/ROOT/Versions/5.18.00-gcc
--datadir=/opt/ROOT/Versions/5.18.00-gcc/share
--docdir=/opt/ROOT/Versions/5.18.00-gcc/doc
--incdir=/opt/ROOT/Versions/5.18.00-gcc/include
--libdir=/opt/ROOT/Versions/5.18.00-gcc/lib
--etcdir=/opt/ROOT/Versions/5.18.00-gcc/etc
--elispdir=/opt/ROOT/Versions/5.18.00-gcc/share/emacs/site-lisp --enable-cern
--with-cern-libdir=/usr/lib --enable-fftw3 --enable-gdml --enable-mathcore
--enable-mathmore --enable-opengl --enable-python --enable-qt --enable-roofit
--enable-ruby --enable-shared --enable-soversion --enable-ssl --enable-xml
--enable-xft --enable-xrootd --enable-g4root
--with-g4-incdir=/opt/GEANT4/Versions/9.0.p01/include
--with-g4-libdir=/opt/GEANT4/Versions/9.0.p01/lib/Linux-g++
Any idea to fix this problem? |
135
|
03 Mar 2008 |
Randolf Pohl | Bug Report | ROODY kills analyzer too!! |
Hi,
I had the very same problem last summer during our beam time. Don't know the revision, but it was the tarball I downloaded around mid-July.
Symptom: The MIDAS (online) analyzer crashed as soon as roody was started. Started, i.e. before any user interaction became even possible. And the crash happened always. 100.0%.
My workaround was: Use roody rev. 220.
No crashes, beam time saved.
I attach 2 outputs I saved at that time.
Oh, yes: I still have the sources and such. Last modified date is July 9 and earlier (see attachment 3). I can send them around if you want to find the revision and bracket the offending commits. (I wish you were using "git". Ever read about git-bisect?)
Cheers,
Randolf
PS: Konstantin, I had promised you to try and pin down the problem after the run. Obviously I forgot, sorry. Please tell me if I can be of any help now. |
137
|
04 Mar 2008 |
Exaos Lee | Bug Report | Revision 221 works! But not remotely. |
I recompiled the roody of revision 221 and found this revision works. But when I run roody remotely, it still keeps killing the analyzer 100%.
Hope somebody can fix it. |
138
|
07 Mar 2008 |
Randolf Pohl | Bug Report | Revision 221 works! But not remotely. |
Hi,
Exaos Lee wrote: | I recompiled the roody of revision 221 and found this revision works. But when I run roody remotely, it still keeps killing the analyzer 100%.
|
We used 220 (not 221) successfully, but only locally.
Now that you say it I think I recall I could not get roody to run remotely. Don't remember the exact reasons, though.
What I did then was to "ssh -X" from the remote machine into the backend and start roody there (Actually a button with a beautiful picture enabled the users to do so).
Just an idea: Are all necessary ports open on the receiving machine? Maybe the analyzer is just collateral damage, in reality roody commits suicide because the firewall is nasty to him?
I don't have my machines set up at the moment. One of the machines stayed in a box at PSI. So I can't really help you, I am sorry. I think it's time for the specialists now. Anybody there???!?!
Good luck,
Randolf |