CAUTION
This is not an ATLAS official page.
Any information on this page is not guaranteed by ATLAS.
Please have a look in the official page concerning computing operations
http://cern.ch/atlas-computing/operations/operations.php
for the official information.
Your contribution is welcome to add, correct and update the contents.
General Information
Information concerning the ATLAS Computing Operations will be found
at
and ATLAS Computing Resources at
You can see which sites are available for the productions at
Some communications will be made in;
Requirements
for a LCG site to join the ATLAS productions:
Tier0 test
DDM Functional Test
October test
September test
SC4
Calibration Data Challenge
LCG
The current recommended release is gLite-3.0, especially for SC4
- LCG 2_7_0 is also usable, but many improvements/bug fixes are included in gLite-3.0
- LCG 2_6_0 has some problems.
- We will have to upgrade to LCG 2.7.0 while minimizing the interference to our on-going productions. ( 7 Feb 2006, Zhongliang Ren)
VO Box
Publishing Information
- GlueHostMainMemoryRAMSize
Known Problems
- gLite-3.0
- a bug found in FTS. fix should be included in the next release. (21 July 2006
- 2_6_0
Atlas Software
This is done by the deployment team (see
AtlasSoftOnLCG2 and also the talks by A.DS
comp-opr 15.dec.2006,
at SW week 12.sep.2006). The current deployment status can also be seen by following the link there.
In case the necessary atlas software release is not installed in a site,
a request should be made following the instructions there.
The releases currently used in productions;
- 11.0.X (tasks)
- 12.0.X tasks
- 12.0.31 (tasks)
- 12.0.31.8: 1mm range cut since 12.0.31.4
- 12.0.5 (status) (tasks)
- 12.0.5.3: The final patched version id 12.0.5.3. This is being rebuilt as 12.0.6
- 12.0.6 (status) (tasks) - The clean bug fixed version of 12.0.5. To be used for CSC reconstruction and pileup
- 12.0.6.5 (status)
Calibration constants used in ALL 12.0.6.1 reconstruction were obtained for "30 microns"
Large scale atlfast (12.0.6.2)
SAN/Tag/DPD (12.0.6.2) needed in part for computing model test
Releases in validation on grids;
Coming releases;
Previous releases;
- Cronus is being tested with 12.3.0 validation jobs
- 12.0.4 Waiting for transformation
- 12.0.31
- 12.0.3 expected to be the production release (2006.08.11)
- 12.0.2 Release 12.0.2 validation started yesterday (25 August 2006) Release available today – installation starting (18 August 2006), Release is expected early next week (11 August 2006)
- 12.0.1 Very high failure rate on all grids – many bugs found (2006.08.11) released tuesday, July 11th. Installation in progress (2006.07.14. report from A.DS and K.D at comp-oper meeting)
Expected early next week for grid - still under validation (2006.06.30.)
- 12.0.0
- 11.5.0 Not tested yet. Kit has been available since May 9th, and installed in many places, but no transformation kit ready. (26.May.2006)
- 11.3.0 tasks failed on all grids (26.May.2006)
- 11.0.42 Production with 11.0.42 started since the April 2006 SW&C workshop after the G4 bug was fixed hopefully! (21 Apr. 2006)
- 11.0.41 for reconstruction
- 11.0.4 for simulation and digitization (bug found in simulation; see 11.0.42)
DDM (Distributed Data Management)
- Useful stuff
- Stephane's script for removing files from a DPM SE (written as to work at LAPP and for French T2's. You need to modify to work at other sites.) /afs/cern.ch/user/j/jezequel/public/dq_off/delete_dpm.sh
Conditions Database
- Options for Tier-2s (from the presentation at the Tier2 workshop):
- Access Oracle server of nearest Tier-1
- OK for small scale access, limited by network latencies and load on Tier-1 server
- Extract needed COOL data into an SQLite file (tools exist)
- A "one shot" replication, only practical for a subset of data (e.g. for simulation use case)
- Maintain a "live" database copy in MySQL - run a local MySQL condDB server
- Tool being developed to synchronise two COOL databases and copy recent updates
- Will probably be needed for sites doing significant calibration work
- Again, only practical for subsets of the full conditions database
- Use of Oracle is not excluded, but a lot of work would be needed to maintain it.
Resources Requirements
CPU
Memory
Storage
- Installation of Atlas Software requires at least 10 GB of shared filesystem among WNs.
Tier2
Links
created -- iueda - 09 Mar 2006
last update -- Main.iueda - 30 May 2007