Difference: MCTCK (10 vs. 11)

Revision 112018-09-11 - RosenMatev

Line: 1 to 1
 
META TOPICPARENT name="LHCbTCK"
Changed:
<
<

Making a MC version of a TCK

>
>

Making a MC version of an existing data TCK

 
Changed:
<
<
To make an MC TCK from a pre-existing data TCK, Setup the latest version of Moore (independent of the version corresponding to the TCK you want to make an MC TCK for)

SetupProject Moore vXXX --build-env

Then check out the head of HltTCK:

>
>
First, check out the head of HltTCK, and then run iTCKsh from the prod (or latest) version of Moore (independent of the version corresponding to the TCK you want to make an MC TCK for)
 
getpack TCK/HltTCK head
Changed:
<
<
cd TCK/HltTCK/cmt cmt make
>
>
lb-run Moore iTCKsh --write TCK/HltTCK/config.cdb
 
Changed:
<
<
Then setup this Moore version:
>
>
In TCKsh import the createMCversion module and feed it your data TCK:
 
Changed:
<
<
SetupProject Moore vXXX
>
>
from TCKUtils.createMCversion import createMCversion createMCversion(tck=0x11641724, cas=default_cas)
 
Changed:
<
<
And run TCKsh. In TCKsh import the createMCversion module and feed it your data TCK:
>
>
You'll see it dump the new TCK as well as a diff of the old with the new. If everything worked, the only differences will be AcceptFractions from the prescalers being set to 1 instead of prescaled as in data.
 
Added:
>
>
Check that your new MC TCK appears under the right version of Moore with
 
Changed:
<
<
from TCKUtils.createMCversion import * tck=0x00XXXXXX cas=ConfigCDBAccessSvc(Mode='ReadWrite') createMCversion(tck=tck,cas=cas)
>
>
listConfigurations()
 
Changed:
<
<
You'll see it dump the new TCK as well as a diff of the old with the new. If everything worked, the only differences will be AcceptFractions from the prescalers being set to 1 instead of prescaled as in data. If you then do a listConfigurations() your new MC TCK should appear under the right version of Moore.

Edit the release notes of TCK/HltTCK to reflect the addition of a new MC TCK, then commit:

svn commit -m "added new TCK 0x40XXXXX for whatever reason"

You can now tag the package: Edit the doc/release notes and cmt/requirements with the new package version (increment the revision number) Then:

tag_package TCK/HltTCK vXrYY
>
>

Releasing the MC TCK

 
Added:
>
>
Copy the config.cdb file somewhere and ask Rosen to commit and release it.
 
Changed:
<
<
Once that is done, you need to add it to Appconfig:
>
>
Once that is done, you need to add it to AppConfig:
 
Changed:
<
<
getpack AppConfig head
>
>
git lb-clone-pkg AppConfig
 cd AppConfig/options/Conditions
Changed:
<
<
Copy one of the existing TCK-*.py files over to your TCK's name:
>
>
Copy one of the existing TCK-*.py files over to your TCK's name:
 
cp TCK-0x40YYYYY.py TCK-0x40XXXXX.py
Line: 67 to 47
 Moore().InitialTCK = '0x40XXXXXX'
Changed:
<
<
Finally, svn add this file, change the release notes and commit:
>
>
Finally, commit your change on a new branch, push it and open a merge request
 
Changed:
<
<
svn add TCK-0x40XXXXXX.py vim ../../doc/release.notes svn commit -m "added new TCK 0x40XXXXX for whatever reason"
>
>
git checkout -b add-MC-TCK git commit TCK-0x40YYYYY.py git push -u origin add-MC-TCK
 
Changed:
<
<
And now you need to put it into a release request for TCK/HltTCK You may potentially need to tag and request release of AppConfig - check with the simulation people first to see if they plan to commit other important updates soon.
>
>
And now you need to put it into a release request for TCK/HltTCK You may potentially need to tag and request release of AppConfig - check with the simulation people first to see if they plan to commit other important updates soon.
  Go here:
Changed:
<
<
https://sft.its.cern.ch/jira/browse/LHCBDEP/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel Login, select Create, change the issue to "task", and specify TCK/HltTCK with the right version number. Not every box needs to be filled in. Once the form is filled out click submit.
>
>
https://its.cern.ch/jira/browse/LHCBDEP/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel Login, select Create, change the issue to "task", and specify TCK/HltTCK with the right version number. Not every box needs to be filled in. Once the form is filled out click submit.
 
Changed:
<
<
Lastly, contact the production people so that they know to release a new Appconfig and you're done.
>
>
Lastly, contact the production people so that they know to release a new AppConfig and you're done.
 

Adding TCKs for Moore v14 or older

The config.cdb files did not exist in v14 or older, so the TCKs need to be in the config.tar 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