TWiki
>
Main Web
>
CMSUserSupport
>
CMSUserSupportNewsForManagement
>
CMSUserSupportNews05Mar07
(2007-03-05,
CMSUserSupport
)
(raw view)
E
dit
A
ttach
P
DF
---+ User Support News 05 March 2007 The items from which I expect feed-back are marked in %RED%red%ENDCOLOR% and the items which I propose as action items in the JOC meeting are marked in %RED% __bold red__ %ENDCOLOR%. %TOC% ---++ Tutorials ---+++ CMS week tutorial The !CMSSW tutorial on parallel with other sessions during the CMS week caused some negative feedback. %RED% __Offline, computing and physics managements to agree a time slot during CMS and Physics/Trigger weeks which does not overlap with the physics groups sessions__ %ENDCOLOR% ---+++ Scheduled tutorials A list of scheduled tutorials can be seen in [[https://twiki.cern.ch/twiki/bin/view/CMS/Tutorials][the tutorial page]], basically each CMS or Physics/Trigger week. A visualization tutorial by Yana Osborne is scheduled for April. %RED% Other suggestions? %ENDCOLOR% ---++ Documentation Reminder: * [[https://twiki.cern.ch/twiki/bin/view/CMS/WorkBook][WorkBook]]: to get started and up to first analysis * [[http://cmsdoc.cern.ch/cms/cpt/Software/html/General/gendoxy-doc.php][Reference Manual]]: brief description of content and purpose of *each* package * [[https://twiki.cern.ch/twiki/bin/view/CMS/SWGuide][CMS Offline Guide]]: * description of algorithms * usage and "how-to" documents which are too detailed for the !WorkBook * gathers information currently spread in numerous wiki pages to a single structure. ---+++ !WorkBook Moving to !CMSSW_1_2_0 in the !WorkBook, see [[https://hypernews.cern.ch/HyperNews/CMS/get/workbook/128.html]]. This means that all the tutorials in the !WorkBook should use 1_2_0 or a more recent version. ---+++ CMS Offline Guide Work in progress: I'm waiting feedback from * %RED%Tommaso and Shahram on [[https://twiki.cern.ch/twiki/bin/view/CMS/SWGuideReco]] * Luca and Oliver on how to proceed with [[https://twiki.cern.ch/twiki/bin/view/CMS/CalAliDB]] * DPG coordinators on HCAL and local muon pages %ENDCOLOR% ---+++ Reference Manual The release for which all the subsystem and packages are required to have a documentation page in the reference manual is 1_4_0. The announcement sent to the software development HN forum: https://hypernews.cern.ch/HyperNews/CMS/get/swDevelopment/858.html and a reminder about the cvs links in https://hypernews.cern.ch/HyperNews/CMS/get/swDevelopment/868/1.html %RED% __The offline conveners should remind the developers of this milestone in their meetings__ %ENDCOLOR% The release notes summary should be added to the Reference Manual. I've contacted reco, sim and phys tools conveners to get started with these three main areas. More items can be added. ---++ Getting help ---+++ Problem reporting channel for data/computing issues I have proposed to have a "computing front end" person (or a rotating task) to monitor and follow the different channels used in reporting computing problems (HN, ggus, savannah). I have discussed this with Christoph and Peter Kreuzer and they will figure out a list or persons who can participate to this effort. There's a clear consensus that the user questions should be directed to [[https://savannah.cern.ch/support/?func=additem&group=cmssw][savannah]] rather that the HN discussion lists to free the discussion lists for the technical discussions and to assure that the questions get answered. This will be announced to the wide public when the persons participating and modus operandi have been defined. ---+++ Problem reporting channel for software issues Most of the user support comes is de facto provided in the HN discussion lists. We also provide the [[https://savannah.cern.ch/support/?func=additem&group=cmssw][savannah]] interface (same link as for the computing questions above, interface offers different categories corresponding software and computing issues) to give a single entry point for the user questions. To have the savannah problem reporting work efficiently, we need to * define the who is responsible assigning a task to a developer * make it clear for users that finally the question very likely goes to the same developers as the ones on HN lists, i.e. it is useless first to discuss an issue on HN lists and then address the same question to savannah (unless no reply was obtained from HN) * have a trouble shooter who would first make sure that the reported problem is reproducible before assigning it to anyone making sure that all the necessary information is available (version, config files, private libraries). This can be discusses in a JOC meeting when I've discussed with the catA person who can potentially participate to this. ---+++ EGEE User Support Workshop I've assisted to the [[http://indico.cern.ch/conferenceOtherViews.py?view=standard&confId=11905][EGEE User Support Workshop]]. EGEE provides ggus - global grid user support - and the goal of the meeting was to understand how and in which cases we could profit from this service. My [[%ATTACHURL%/karlsruhe010307.ppt][slides]] are attached to this page. Our interest would be to use this service when it offers the most direct way to the problem solution. In most cases ggus users would not be cms end-users but rather cms computing experts. I have discussed and I will discuss this further with Peter Kreuzer for the data production team and with the people providing feedback to CRAB. It was suggested in this workshop that - for example - the data production would form a "user support unit" (in ggus terminology) - not to provide user support but to get it from ggus. If a question would come from this "unit" it would be clear for ggus support personnel that this comes from a big client and requires immediate feedback. ---++ Account registration Martti Pimiä takes care of the afs accounts and afs disk space for cms users. Werner Jank, Nick Sinanis and Gilles Raymond have done this in his absence. Werner is now retiring and we need to have someone (CERN staff as this is about CERN computing resources) to take care of this when Martti is absent. -- Main.CMSUserSupport - 05 Mar 2007
Attachments
Attachments
Topic attachments
I
Attachment
History
Action
Size
Date
Who
Comment
ppt
karlsruhe010307.ppt
r1
manage
4877.0 K
2007-03-05 - 15:56
CMSUserSupport
E
dit
|
A
ttach
|
Watch
|
P
rint version
|
H
istory
: r2
<
r1
|
B
acklinks
|
V
iew topic
|
WYSIWYG
|
M
ore topic actions
Topic revision: r2 - 2007-03-05
-
CMSUserSupport
Log In
Main
Home
Index
Search
User Search
Changes
Notifications
RSS Feed
Documentation
Support
Webs
Main
Main Archive
Plugins
Sandbox for tests
Public webs
Public webs
ABATBEA
ACPP
ADCgroup
AEGIS
AfricaMap
AgileInfrastructure
ALICE
AliceEbyE
AliceSPD
AliceSSD
AliceTOF
AliFemto
ALPHA
ArdaGrid
ASACUSA
AthenaFCalTBAna
Atlas
AtlasLBNL
AXIALPET
CAE
CALICE
CDS
CENF
CERNSearch
CLIC
Cloud
CloudServices
CMS
Controls
CTA
CvmFS
DB
DefaultWeb
DESgroup
DPHEP
DM-LHC
DSSGroup
EGEE
EgeePtf
ELFms
EMI
ETICS
FIOgroup
FlukaTeam
Frontier
Gaudi
GeneratorServices
GuidesInfo
HardwareLabs
HCC
HEPIX
ILCBDSColl
ILCTPC
IMWG
Inspire
IPv6
IT
ItCommTeam
ITCoord
ITdeptTechForum
ITDRP
ITGT
ITSDC
LAr
LCG
LCGAAWorkbook
Leade
LHCAccess
LHCAtHome
LHCb
LHCgas
LHCONE
LHCOPN
LinuxSupport
Main
Medipix
Messaging
MPGD
NA49
NA61
NA62
NTOF
Openlab
PDBService
Persistency
PESgroup
Plugins
PSAccess
PSBUpgrade
R2Eproject
RCTF
RD42
RFCond12
RFLowLevel
ROXIE
Sandbox
SocialActivities
SPI
SRMDev
SSM
Student
SuperComputing
Support
SwfCatalogue
TMVA
TOTEM
TWiki
UNOSAT
Virtualization
VOBox
WITCH
XTCA
Welcome Guest
Login
or
Register
Cern Search
TWiki Search
Google Search
Main
All webs
Copyright &© 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use
Discourse
or
Send feedback