Difference: DecfilesReleases (19 vs. 20)

Revision 202018-02-13 - MichalKreps

Line: 1 to 1
 
META TOPICPARENT name="LHCbSimulation"

Preparing a release of DecFiles

Line: 122 to 122
 

Announce the availability of the pre-release for final checks

You should also send a mail to lhcb-mc-production@cernNOSPAMPLEASE.ch and when there are many changes to gauss@cernNOSPAMPLEASE.ch announcing that the pre-release of DecFiles vXrY (e.g. v27r15) is available and will be picked up by the Gauss nightly builds in the lhcb-branches slot and the list of decay files produced is on the web at http://lhcb-release-area.web.cern.ch/LHCb-release-area/DOC/decfiles/releases/dev/table_evttype.php.
Deleted:
<
<

Prepare the tag collector for the next release

Note: Only Gloria and Patrick have the privilege to do so at the moment. Ask one of them to do it, if not already done.
Go to the tag collector and Click on New Project'. Enter 'DecFiles' as name of the project and the next version. Add the explanation on how to add a new change in the tag collector (you can cut and paste the one of the previous version). Once the new DecFiles (e.g. v27r16) is listed in the tag collector, edit the generic entry GSDCTNXU, myDecayFile and click on Show/Hide of Extra associated project. Click on new version of DecFiles and de-select the old version. The entry should now appear in the new DecFiles v27r16.
 

Request the deployment

After at least one successful use of the new version in the nightly you can ask for the deployement in the release area and on the grid. Go to savannah (https://sft.its.cern.ch/jira/browse/LHCBDEP) and once you logged-in submit a new task. Put the name and version in the subjects, choose the package and ask for a grid deployment. Also put Gloria.Corti@cernNOSPAMPLEASE.ch, Patrick.Robbe@cernNOSPAMPLEASE.ch, Tomas.Pilar@cernNOSPAMPLEASE.ch in the cc at the bottom. When asking for a deployment of two parallel releases, specify to run the bookkeeping update only for one (for example, for v26 but not for v25).
Added:
>
>

Update bookkeeping

From lxplus, once the changes on CVMFS have been propagated (check with ls /cvmfs/lhcb.cern.ch/lib/lhcb/DBASE/Gen/DecFiles), you have to update the bookkeeping.

  • Get a valid Grid proxy
    lhcb-proxy-init
    
  • Update the bookkeeping
    cd /cvmfs/lhcb.cern.ch/lib/lhcb/DBASE/Gen/DecFiles/<version>
    lb-run -c best LHCbDirac dirac-bookkeeping-eventtype-mgt-insert doc/table_event.sql
    lb-run -c best LHCbDirac dirac-bookkeeping-eventtype-mgt-update doc/table_event.sql
    lb-run -c best LHCbDirac dirac-bookkeeping-eventtype-mgt-update doc/table_obsolete.sql
    

The dirac-bookkeeping-eventtype-mgt-insert command will produce many errors like

{'EVTTYPEID': '12165431', 'DESCRIPTION': 'Bu_D02pi+pi-,K+pi-pi0=PHSP,DecProdCut', 'PRIMARY': '[B+ -> pi+ pi+ pi- (D0bar -> K+ pi- pi0)]cc'} : Excution failed.: ( ORA-00001: unique constraint (LHCB_DIRACBOOKKEEPING.SYS_C00302542) violated
ORA-06512: at "LHCB_DIRACBOOKKEEPING.BOOKKEEPINGORACLEDB", line 1131
ORA-06512: at line 1
 ) 
This is normal as most event types already exist in the Oracle table. Things are OK if the last line is like
The following event types are inserted: ['42102201', '42102200', '42163203', '42102221', '42102220', '15104451', '42100210', '42100211', '42100230', '42100231', '42142201', '42142200', '42102210', '42102211', '42162203', '42162202', '15574100', '42100221', '42100220', '12163436', '12163437', '42102601', '42102600', '12163236', '42163202', '12163235', '42112200', '42112201'] 
 

Update the documentation for the release and announce it

Once you receive the notification that DecFiles has been deployed on the grid, you should update the documentation: go to $LHCBDOC/decfiles and type
Line: 148 to 168
 
Finally send an announcement to the lhcb-gauss@cernNOSPAMPLEASE.ch & lhcb-mc-production@cernNOSPAMPLEASE.ch mailing lists with a short explanation.
Deleted:
<
<

Set the version as released in the tag collector

The very last thing to do is to go to the tag collector and hide the DecFiles v27r15 version. When asked if you want to declare the project released answer yes.
 

-- GloriaCorti - 14-Nov-2011 \ No newline at end of file

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback