1. Intersecting UK Grid & EGEE/LCG/GridPP Activities Applications & Requirements Mark Hayes, Technical Director, CeSC

2. What does the eScience Grid currently look like? Globus v2 installed at all regional eScience centres. Heterogenous resources (linux clusters, SGI O2/3000, SMP Sun machines) eScience certificate authority Operational & network monitoring Virtual organisation management

3. Applications on the eScience Grid E-Minerals - Monte Carlo simulations of radiation damage to crystal structures (Condor-G & home-grown shell scripts) Geodise - genetic algorithm for optimisation of satellite truss design (Java COG plugins in Matlab) GENIE - ocean-atmosphere modelling (flocked Condor pools) Other tools in use: HPCPortal, InfoPortal, Nimrod/G, SunDCG

4. GridPP & EDG Dedicated linux clusters running EDG middleware (globus++) Very homogenous resources Resource broker (based on Condor) LDAP based VO management

5. Particle Physics Applications e.g.ATLAS data challenge - monte carlo event generation, tracking & reconstruction Large FORTAN/C++ codes, optimised for Linux (and packaged as RPMs) Runs scripted using EDG job submit tools GUIs under development (e..g GANGA)

6. Questions Could I run an ATLAS data challenge on the eScience Grid? Could I run an e-Minerals monte carlo run on the EDG? EDG has few standard user interfaces: EDG UI/Ganga etc. eScience Grid relies on lower-level Globus protocols only. Do we rely on leaving Globus gatekeepers/MDS/etc exposed or develop common user interfaces?