In the excitement of supporting DC2 and Instrument integration, we have somewhat neglected our infrastructure.
What are the elements?
What |
Description |
Person Responsible |
|---|---|---|
CMT |
Code management tool (Orsay) |
? |
MRvcmt |
gui for CMT |
Riccardo |
Gaudi |
C++ framework (LHCB/ATLAS) |
? |
GEANT4 |
simulation package |
Francesco, Tracy |
Root |
Persistent store; analysis |
Heather, David |
sundry extlibs |
a bunch of other libs |
sundry |
Release Manager |
automated code builder |
Navid |
Installer |
C++ code installer; gui/linemode |
Navid, Tony |
FRED |
Event display |
Riccardo |
gcc compiler |
linux compiler |
? |
end user scripts SciTools |
avoid CMT scripts |
Navid |
external tools on windows |
ds9, fv, xspec, etc |
? |
We are several versions behind current in CMT, Gaudi and gcc, with no resources available to apply to understanding the needed transitions. We are in better shape with GEANT4 and Root, where we are not so far behind and have mechanisms in place for upgrades.
Windows support
In particular we are short on support for Windows - those who develop on Windows do not do infrastructure support, except Toby who is trying to phase it out of his activities.
Our prime Windows users are Bill, Tracy, Leon, Toby, Zach, Sasha and Riccardo; the main advantage is the Visual Studio environment, and primarily the debugger.
Future MAC support
This topic looms on the horizon. A potentially interesting aspect is that Visual Studio is available on the MAC.