OXFORD|
City|
Life|
University|
Club|
Gazette |
Glossary
Directions:| Physics Dept| Denys Wilkinson| UOxfordMap | from railway station
Home | Database | Luminosity | Trigger | VB |
| ||
previous links:
Elizabeth Gallas, Applications Physicist with the FermiLab Computing Division on the DØ Experiment | |||
other:
google(US/UK) |
wikipedia |
wiktionary |
AngloGeneva
ebay(US/UK) | W(Oxford| Geneva ms u| WAurora) | |
ORCiD in INSPIRE record ...ATLAS members who do not yet have an ORCiD number are invited to proceed with the following steps:
Old ATLAS Membership Database interface
https://atglance.web.cern.ch/atglance/membership/main.php
will be fully retired on Oct 27.
Collaborators are kindly asked to use the new ATLAS Membership Database interface
https://glance.cern.ch/atlas/membership/.
DBAs can use the Oracle Enterprise Manager (OEM), but most developers don't have access to OEM.
Database Domain and Metadata related JIRA:
ConditionsDB | LS1ConditionsDB
AtlasDBIssues
DataBasesPortal - placeholder
DatabaseProject - needs to be updated
ITnews
|
IT Service Status Board
|
Interventions
CERN Web Services Portal (manage your CERN websites)
Service Level Status Overview:
https://sls.cern.ch/
|
ITCoord/WebHome
|
ITCoordExperimentContacts
CERN_Computing_Seminars
|
ITUM (IT Technical Users Meeting):
Home
|
Agendas
Each SW release contains a default DB Release in the distribution kit (containing Geometry DB for Real AND Simulation processing and containing Conditions DB for Simulation processing, the latter so that simulation jobs do not need to connect to the database). The SW Release -- default DB Release mapping is at AtlasDBRelease#S_W_release_vs_DB_Release. A DB Release is generally built for each Software Release (Status). Intermediate DB Releases are built if problems are found (bug or new data). There are DB Release notes here: AtlasDBReleaseNotes The Geometry DB tags contents can be found here: AtlasGeomDBTags#ATLAS_Geom_DB_Tag_contents. The Geometry DB tags mapping to Software Release here: AtlasGeomDBTags#ATLAS_Geom_DB_Tags_and_Software If a non default DB Release is needed, instructions for Distribution and Installation can be found here: AtlasDBRelease#Distribution_Installation. After installation, to use the new DB Release, point the runtime environment to it. See AtlasDBRelease#Using_non_default_DB_Releases Details of building a DB Release and it's components (Geometry, Trigger, Conditions) were discussed at the Database Meeting on April 12, 2010 including the newly implemented "current DB Release" which proposes that jobOptions can specify DBRelease=current would automatically pick up the latest DB Release.
Other Frontier/Squid links:
-- put p12 file in .globus subdirectory cd mv junk/cert_file4.p12 .globus dir -rlt .globus -rw-r--r-- 1 gallas atlas 5158 Aug 2 13:41 cert_file4.p12 -- use p12 to create pem files cd .globus PK12_FILE="${HOME}/.globus/cert_file4.p12" openssl pkcs12 -in ${PK12_FILE} -clcerts -nokeys -out usercert.pem Enter Import Password: MAC verified OK openssl pkcs12 -in ${PK12_FILE} -nocerts -out userkey.pem Enter Import Password: MAC verified OK Enter PEM pass phrase: Verifying - Enter PEM pass phrase: -- give the correct permissions to the files (chmod) chmod 400 userkey.pem chmod 444 usercert.pem -- Issue the command (you need to issue this every time you login to use the Grid): source /afs/cern.ch/project/gd/LCG-share/current/etc/profile.d/grid_env.sh voms-proxy-init -voms atlas Enter GRID pass phrase: Your identity: /C=UK/O=eScience/OU=Oxford/L=OeSC/CN=elizabeth gallas Creating temporary proxy .......................................................... Done Contacting vo.racf.bnl.gov:15003 [/DC=org/DC=doegrids/OU=Services/CN=vo.racf.bnl.gov] "atlas" Done Creating proxy ....................................... Done Your proxy is valid until Wed Nov 23 23:58:11 2011
Notes from Fabian: "voms-proxy-init -voms atlas" is good "voms-proxy-init" is bad "voms-proxy-init -voms atlas -rfc" is bad source /afs/cern.ch/project/gd/LCG-share/current/etc/profile.d/grid_env.sh voms-proxy-init --voms atlas export AtlasSetup=/afs/cern.ch/atlas/software/dist/AtlasSetup alias asetup='source $AtlasSetup/scripts/asetup.sh' asetup 17.0.5.4 amiCommand GetRunsForDataPeriod -period=N2 -projectName=data11_hiSVN pyAMI-- old tags (03-05-04 and earlier)
-------------------------------------------------------------- Collection list: NAME: TAGtest.pool TYPE: RootCollection NFRAG: 1 -------------------------------------------------------------- Number of Tokens is: 3 Tokens are: NAME: StreamAOD_ref TYPE: Token INFO: NAME: StreamESD_ref TYPE: Token INFO: NAME: StreamRAW_ref TYPE: Token INFO: -------------------------------------------------------------- Number of Attributes is: 314 Attributes are: NAME: RunNumber TYPE: unsigned int INFO: UNIT=NUMBER;GRP=TIME; NAME: EventNumber TYPE: unsigned int INFO: UNIT=NUMBER;GRP=TIME; NAME: EventTime TYPE: unsigned int INFO: UNIT=NUMBER;GRP=TIME; NAME: EventTimeNanoSec TYPE: unsigned int INFO: UNIT=NUMBER;GRP=TIME; NAME: LumiBlockN TYPE: unsigned int INFO: UNIT=NUMBER;GRP=TIME; ... NAME: TauIdWord TYPE: unsigned int INFO: UNIT=BITMASK;GRP=QUALITY_PHYSICS; NAME: TopWord TYPE: unsigned int INFO: UNIT=BITMASK;GRP=QUALITY_PHYSICS; ---------------------------------------------------------