Difference: TestFileDB (1 vs. 17)

Revision 172019-07-17 - ChristopheHaen

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

TestFileDB, a database of test files for use in automated software tests

Line: 156 to 156
  You can copy the files directly to CERN-SWTEST, by using the following commands: %SYNTAX{ syntax="sh"}%
Changed:
<
<
lb-run -c best LHCbDirac bash lhcb-proxy-init
>
>
lb-run -c best LHCbDirac/prod bash --norc lhcb-proxy-init -g lhcb_prmgr
 dirac-dms-add-file /lhcb/swtest//myfile myfile CERN-SWTEST %ENDSYNTAX%

- Commit and use in nightlies

Revision 162018-08-20 - PaulSeyfert

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

TestFileDB, a database of test files for use in automated software tests

Line: 81 to 81
  This obviously depends where (in which project) you're planning on adding the tests. The example below is for Moore, replace with your version.%SYNTAX{ syntax="sh"}% lb-dev Moore/latest
Added:
>
>
cd MooreDev_HEAD
 git lb-clone-pkg PRConfig make %ENDSYNTAX%

Revision 152018-01-15 - BenjaminCouturier

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

TestFileDB, a database of test files for use in automated software tests

Line: 16 to 16
 

Where is it?

TestFileDB lives under PRConfig, the DBASE package designed to hold options files and tests for the LHCb Performance and Regressions testing system.

Changed:
<
<
>
>
 
Line: 41 to 41
 

- How can I browse what's there?

Either:

Changed:
<
<
  1. Read through the python module in SVN: https://svnweb.cern.ch/trac/lhcb/browser/DBASE/trunk/PRConfig/python/PRConfig/TestFileDB.py
>
>
  1. Read through the python module in SVN: https://gitlab.cern.ch/lhcb-datapkg/PRConfig/blob/master/PRConfig/python/PRConfig/TestFileDB.py
 
  1. Browse through the entries in TestFileDB as shown above
  2. Browse through using the browsing script $PRCONFIGROOT/scripts/BrowseTestFiles.py The inbuilt browser works like browsing a directory structure where files are separated into "directories" based on their metadata.
  3. Browse manually with the low-level helper commands. This is the basic part that is wrapped in the BrowseTestFiles.py script. %SYNTAX{ syntax="python"}%
Line: 61 to 61
 TestFileDB.test_file_db["2012_raw_default"].run(configurable=Moore()) %ENDSYNTAX%
  • This procedure will add the test files through IOHelper, and configure the configurable Moore with the database tags stored in the test file metadata, and simulation True/False flag.
Changed:
<
<
>
>
 

- How can I use it in my project?

Line: 80 to 80
 

- Obtaining a local copy for editing

This obviously depends where (in which project) you're planning on adding the tests. The example below is for Moore, replace with your version.%SYNTAX{ syntax="sh"}%

Changed:
<
<
SetupProject Moore v21r0 --build-env getpack PRConfig head
>
>
lb-dev Moore/latest git lb-clone-pkg PRConfig
 make
Deleted:
<
<
SetupProject Moore v21r0 #next line not always required, depends on the intricacies of cmt cd PRConfig/cmt source setup.csh
  %ENDSYNTAX%

Edit, commit with release notes.

Line: 98 to 94
 
  • You can access the files without needing a grid certificate.
  • The files listed are PFNs.
  • You have added as much information as possible to the metadata of the files.
Changed:
<
<
>
>
  Remember that this is a full python module, so any valid python to create the entries in the database is allowed, even something procedural.
Line: 112 to 108
 

- Automatic scripts for adding to the database:

If you already have a python file which adds test files through IOHelper or EventSelector there is a script which will copy this to the TestFileDB and ask you for the metadata.

Changed:
<
<
>
>
  To use this:
  1. Prepare local copy as above.
Line: 123 to 119
 
    • ./AddToTestFilesDB.py --help
    • ./AddToTestFilesDB.py someoptsfile_or_a_PFN
Changed:
<
<
You can then check the files are readable for you with the script TestReadable.py: https://svnweb.cern.ch/trac/lhcb/browser/DBASE/trunk/PRConfig/scripts/TestReadable.py
>
>
You can then check the files are readable for you with the script TestReadable.py: https://gitlab.cern.ch/lhcb-datapkg/PRConfig/blob/master/scripts/TestReadable.py
 

- Automatic scripts for adding files to CERN-SWTEST/EOS:

ACTION RESTRICTED TO RELEASE MANAGERS

For files actually used in our automated nightly tests, especially centrally produced files we need to make sure they are not tied to the validity of a specific user account or production obsoletion cycle. So, please upload your files to the CERN-SWTEST element using the script provided:

Changed:
<
<
>
>
  To use this:
  1. Prepare local copy as above.
Line: 152 to 148
 
    • ../scripts/MigrateToSWTEST.py --help
    • ../scripts/MigrateToSWTEST.py
Changed:
<
<
You can then check the files are readable for you with the script TestReadable.py: https://svnweb.cern.ch/trac/lhcb/browser/DBASE/trunk/PRConfig/scripts/TestReadable.py
>
>
You can then check the files are readable for you with the script TestReadable.py: https://gitlab.cern.ch/lhcb-datapkg/PRConfig/blob/master/scripts/TestReadable.py
 

Copying files directly to CERN-SWTEST

You can copy the files directly to CERN-SWTEST, by using the following commands: %SYNTAX{ syntax="sh"}%

Changed:
<
<
lb-run LHCbDirac bash
>
>
lb-run -c best LHCbDirac bash
 lhcb-proxy-init dirac-dms-add-file /lhcb/swtest//myfile myfile CERN-SWTEST %ENDSYNTAX%

Revision 142017-11-15 - MarcoCattaneo

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

TestFileDB, a database of test files for use in automated software tests

Line: 145 to 145
  %ENDSYNTAX%
  1. Obtain a grid proxy:
    • lhcb_user: you will be able to migrate user files but not existing production files to CERN_SWTEST
Changed:
<
<
    • lhcb_prod: you will be able to migrate existing production files but not user files to CERN_SWTEST%SYNTAX{ syntax="sh"}%
lhcb-proxy-init --group=lhcb_prod
>
>
    • lhcb_prmgr: you will be able to migrate existing production files but not user files to CERN_SWTEST%SYNTAX{ syntax="sh"}%
lhcb-proxy-init --group=lhcb_prmgr
  %ENDSYNTAX%
  1. Execute the script:
    • ../scripts/MigrateToSWTEST.py --help

Revision 132017-03-10 - PaulSeyfert

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

TestFileDB, a database of test files for use in automated software tests

Line: 27 to 27
  TestFileDB is a full python module including inbuilt help. The actual database is stored in a simple python dictionary within the module, called test_file_db. Try:%SYNTAX{ syntax="sh"}% SetupProject LHCb --use PRConfig
Changed:
<
<
python %ENDSYNTAX% %SYNTAX{ syntax="python"}%
>
>
python %ENDSYNTAX% or
<!-- SyntaxHighlightingPlugin -->
lb-run --use=PRConfig LHCb/v42r1 python 
<!-- end SyntaxHighlightingPlugin -->
and then in python: %SYNTAX{ syntax="python"}%
 from PRConfig import TestFileDB help(TestFileDB) print TestFileDB.test_file_db.keys()
Line: 62 to 66
 

- How can I use it in my project?

Changed:
<
<
PRConfig should be available in all LHCb applications. If not you may need to explicitly include it in your lb-run statement:
<!-- SyntaxHighlightingPlugin -->
lb-run SomeProject vXrY --use PRConfig 
<!-- end SyntaxHighlightingPlugin -->
>
>
PRConfig should be available in all LHCb applications. If not you may need to explicitly include it in your lb-run statement:
<!-- SyntaxHighlightingPlugin -->
lb-run --use=PRConfig SomeProject/vXrY 
<!-- end SyntaxHighlightingPlugin -->
 

- Can I maintain my own list of files in this way even if they are not for general consumption?

Revision 122017-03-07 - MarcoCattaneo

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

TestFileDB, a database of test files for use in automated software tests

Line: 62 to 62
 

- How can I use it in my project?

Changed:
<
<
PRConfig should be available in all LHCb applications. If not you may need to explicitly include it in your SetupProject statement:
<!-- SyntaxHighlightingPlugin -->
SetupProject SomeProject vXrY --use PRConfig 
<!-- end SyntaxHighlightingPlugin -->
>
>
PRConfig should be available in all LHCb applications. If not you may need to explicitly include it in your lb-run statement:
<!-- SyntaxHighlightingPlugin -->
lb-run SomeProject vXrY --use PRConfig 
<!-- end SyntaxHighlightingPlugin -->
 
Deleted:
<
<
If this does not work, please contact Marco Clemencic

- How can I use it in my package?

PRConfig should be available in all LHCb applications, but to access it during the qmtests in a given package you will need to declare it explicitly at run time, with a private cmt use statment in the requirements file.

<!-- SyntaxHighlightingPlugin -->
private
  use PRConfig v*
end_private 
<!-- end SyntaxHighlightingPlugin -->

If this does not work, please contact Marco Clemencic

 

- Can I maintain my own list of files in this way even if they are not for general consumption?

Revision 112017-03-03 - MarcoCattaneo

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

TestFileDB, a database of test files for use in automated software tests

Line: 165 to 165
  You can copy the files directly to CERN-SWTEST, by using the following commands: %SYNTAX{ syntax="sh"}%
Changed:
<
<
SetupProject LHCbDirac
>
>
lb-run LHCbDirac bash
 lhcb-proxy-init dirac-dms-add-file /lhcb/swtest//myfile myfile CERN-SWTEST %ENDSYNTAX%

Revision 102016-06-20 - MarcoCattaneo

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

TestFileDB, a database of test files for use in automated software tests

Line: 167 to 167
 %SYNTAX{ syntax="sh"}% SetupProject LHCbDirac lhcb-proxy-init
Changed:
<
<
dirac-dms-add-file /lhcb/swtest/myfile myfile CERN-SWTEST
>
>
dirac-dms-add-file /lhcb/swtest//myfile myfile CERN-SWTEST
  %ENDSYNTAX%

- Commit and use in nightlies

Revision 92015-02-04 - BenjaminCouturier

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

TestFileDB, a database of test files for use in automated software tests

Line: 167 to 167
 %SYNTAX{ syntax="sh"}% SetupProject LHCbDirac lhcb-proxy-init
Changed:
<
<
dirac-dms-add-file /lhcb/grid/prod/lhcb/swtest/lhcb/swtest/myfile myfile CERN-SWTEST
>
>
dirac-dms-add-file /lhcb/swtest/myfile myfile CERN-SWTEST
  %ENDSYNTAX%

- Commit and use in nightlies

Revision 82015-02-04 - BenjaminCouturier

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

TestFileDB, a database of test files for use in automated software tests

Line: 160 to 160
  You can then check the files are readable for you with the script TestReadable.py: https://svnweb.cern.ch/trac/lhcb/browser/DBASE/trunk/PRConfig/scripts/TestReadable.py
Added:
>
>

Copying files directly to CERN-SWTEST

You can copy the files directly to CERN-SWTEST, by using the following commands:

<!-- SyntaxHighlightingPlugin -->
SetupProject LHCbDirac
lhcb-proxy-init
dirac-dms-add-file /lhcb/grid/prod/lhcb/swtest/lhcb/swtest/myfile myfile CERN-SWTEST
 
<!-- end SyntaxHighlightingPlugin -->
 

- Commit and use in nightlies

Don't forget to edit the release notes before you commit! Contact Marco Cattaneo and Marco Clemencic if you want these files to be immediately accessible in the nightlies, and/or request a release of PRConfig by contacting Ben Couturier and Marco Clemencic.

Revision 72014-06-20 - MarcoCattaneo

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

TestFileDB, a database of test files for use in automated software tests

Line: 9 to 9
 

Why should I use it?

Changed:
<
<
  1. Invoilability. The database refers to files by a logical dataset name, or a qmtest name. This allows for an extra layer of obfuscation whereby new files can be chosen or files can be moved to different locations without the test authors needing to change a single line of tests.
>
>
  1. Inviolability. The database refers to files by a logical dataset name, or a qmtest name. This allows for an extra layer of obfuscation whereby new files can be chosen or files can be moved to different locations without the test authors needing to change a single line of tests.
 
  1. Accountability. Not only does TestFileDB keep the PFNs, but also a whole host of file metadata about who produced it, why, and under which conditions. This vastly simplifies management of test files and debugging.
  2. Usability. TestFileDB comes with a framework of useful and extensible features since it is a full python module. Migration of files to the standard test element is simplified, inclusion of a file into a qmtest or an options file is simplified, etc. see below.
Line: 92 to 92
 SetupProject Moore v21r0 #next line not always required, depends on the intricacies of cmt cd PRConfig/cmt
Changed:
<
<
source setup.sh
>
>
source setup.csh
  %ENDSYNTAX%

Edit, commit with release notes.

Line: 147 to 147
 SetupProject Moore v21r0 --use PRConfig --use AppConfig #next line not always required, depends on the intricacies of cmt cd PRConfig/cmt
Changed:
<
<
source setup.sh
>
>
source setup.ssh
  %ENDSYNTAX%
  1. Obtain a grid proxy:
    • lhcb_user: you will be able to migrate user files but not existing production files to CERN_SWTEST
Line: 155 to 155
 lhcb-proxy-init --group=lhcb_prod %ENDSYNTAX%
  1. Execute the script:
Changed:
<
<
    • ./MigrateToSWTEST.py --help
    • ./MigrateToSWTEST.py
>
>
    • ../scripts/MigrateToSWTEST.py --help
    • ../scripts/MigrateToSWTEST.py
  You can then check the files are readable for you with the script TestReadable.py: https://svnweb.cern.ch/trac/lhcb/browser/DBASE/trunk/PRConfig/scripts/TestReadable.py

Revision 62014-06-19 - MarcoCattaneo

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

TestFileDB, a database of test files for use in automated software tests

Line: 162 to 162
 

- Commit and use in nightlies

Changed:
<
<
Don't forget to edit the release notes before you commit! Contact Marco Cattaneo and Rob Lambert if you want these files to be immediately accessible in the nightlies, and/or request a release of PRConfig by contacting Ben Couturier and Marco Clemencic.
>
>
Don't forget to edit the release notes before you commit! Contact Marco Cattaneo and Marco Clemencic if you want these files to be immediately accessible in the nightlies, and/or request a release of PRConfig by contacting Ben Couturier and Marco Clemencic.
 

Revision 52014-02-17 - RobLambert

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

TestFileDB, a database of test files for use in automated software tests

Line: 39 to 39
 Either:
  1. Read through the python module in SVN: https://svnweb.cern.ch/trac/lhcb/browser/DBASE/trunk/PRConfig/python/PRConfig/TestFileDB.py
  2. Browse through the entries in TestFileDB as shown above
Changed:
<
<
  1. Browse using the inbuilt browser. The inbuilt browser works like browsing a directory structure where files are separated into "directories" based on their metadata:%SYNTAX{ syntax="python"}%
>
>
  1. Browse through using the browsing script $PRCONFIGROOT/scripts/BrowseTestFiles.py The inbuilt browser works like browsing a directory structure where files are separated into "directories" based on their metadata.
  2. Browse manually with the low-level helper commands. This is the basic part that is wrapped in the BrowseTestFiles.py script. %SYNTAX{ syntax="python"}%
 from PRConfig import TestFileDB help(TestFileDB) from PRConfig import TestFileUtils

Revision 42014-01-22 - RobLambert

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

TestFileDB, a database of test files for use in automated software tests

Line: 149 to 149
 source setup.sh %ENDSYNTAX%
  1. Obtain a grid proxy:
Changed:
<
<
    • lhcb_user: you will not be able to migrate existing production files to CERN_SWTEST
    • lhcb_prod: you can migrate any files at all%SYNTAX{ syntax="sh"}%
>
>
    • lhcb_user: you will be able to migrate user files but not existing production files to CERN_SWTEST
    • lhcb_prod: you will be able to migrate existing production files but not user files to CERN_SWTEST%SYNTAX{ syntax="sh"}%
 lhcb-proxy-init --group=lhcb_prod %ENDSYNTAX%
  1. Execute the script:

Revision 32014-01-21 - MarcoCattaneo

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

TestFileDB, a database of test files for use in automated software tests

Line: 151 to 151
 
  1. Obtain a grid proxy:
    • lhcb_user: you will not be able to migrate existing production files to CERN_SWTEST
    • lhcb_prod: you can migrate any files at all%SYNTAX{ syntax="sh"}%
Changed:
<
<
lhcb-proxy-init --group=lhcb-prod
>
>
lhcb-proxy-init --group=lhcb_prod
  %ENDSYNTAX%
  1. Execute the script:
    • ./MigrateToSWTEST.py --help

Revision 22014-01-21 - RobLambert

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

TestFileDB, a database of test files for use in automated software tests

Line: 107 to 107
  Remember that this is a full python module, so any valid python to create the entries in the database is allowed, even something procedural.
Added:
>
>

- Database tags:

One of the key features of the TestFileDB is that it can store the database tags appropriate for reading the files. This is a very useful feature, since the database tags might sit far outside the standard tags for random test files. Please be mindful of this when filling the database. Please use the following priority to decide which tags to use:

  1. The tags used in creation of the file. If there is any way of you finding this out you are encouraged to do so.
  2. A compatible pair of tags which are necessary updates to the tags used to create the file. In case the original tags are not compatible with current software, small updates may be required.
  3. If all else fails, an appropriate pair of tags that you deem appropriate for running on this file can be entered. In case you really cannot find out what was originally used, or what is originally used is completely so obsolete to be entirely irelevent, then please enter any two compatible tags which you deem appropriate, but only if this is really really necessary.
 

- Automatic scripts for adding to the database:

If you already have a python file which adds test files through IOHelper or EventSelector there is a script which will copy this to the TestFileDB and ask you for the metadata.

Revision 12014-01-20 - RobLambert

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="TestDrivenDevelopment"

TestFileDB, a database of test files for use in automated software tests

The TestFileDB is a small python database of PFNs of files used for automated software tests. The database lives within the existing software structure and can thus be used in any project/package.

Table of Contents

Why should I use it?

  1. Invoilability. The database refers to files by a logical dataset name, or a qmtest name. This allows for an extra layer of obfuscation whereby new files can be chosen or files can be moved to different locations without the test authors needing to change a single line of tests.
  2. Accountability. Not only does TestFileDB keep the PFNs, but also a whole host of file metadata about who produced it, why, and under which conditions. This vastly simplifies management of test files and debugging.
  3. Usability. TestFileDB comes with a framework of useful and extensible features since it is a full python module. Migration of files to the standard test element is simplified, inclusion of a file into a qmtest or an options file is simplified, etc. see below.

Where is it?

TestFileDB lives under PRConfig, the DBASE package designed to hold options files and tests for the LHCb Performance and Regressions testing system.


Using and abusing the package:

- How can I access it?

TestFileDB is a full python module including inbuilt help. The actual database is stored in a simple python dictionary within the module, called test_file_db. Try:

<!-- SyntaxHighlightingPlugin -->
SetupProject LHCb --use PRConfig
python 
<!-- end SyntaxHighlightingPlugin -->
<!-- SyntaxHighlightingPlugin -->
from PRConfig import TestFileDB
help(TestFileDB)
print TestFileDB.test_file_db.keys()
print TestFileDB.test_file_db["2012_raw_default"]
<!-- end SyntaxHighlightingPlugin -->

- How can I browse what's there?

Either:

  1. Read through the python module in SVN: https://svnweb.cern.ch/trac/lhcb/browser/DBASE/trunk/PRConfig/python/PRConfig/TestFileDB.py
  2. Browse through the entries in TestFileDB as shown above
  3. Browse using the inbuilt browser. The inbuilt browser works like browsing a directory structure where files are separated into "directories" based on their metadata:
    <!-- SyntaxHighlightingPlugin -->
from PRConfig import TestFileDB
help(TestFileDB)
from PRConfig import TestFileUtils
help(TestFileUtils)
help(TestFileUtils.browseTestFiles)
TestFileUtils.browseTestFiles(TestFileDB.test_file_db)
<!-- end SyntaxHighlightingPlugin -->

- How can I access it through options?

  • The following is completely valid python options:
    <!-- SyntaxHighlightingPlugin -->
from Configurables import Moore
from PRConfig import TestFileDB
TestFileDB.test_file_db["2012_raw_default"].run(configurable=Moore())
<!-- end SyntaxHighlightingPlugin -->

- How can I use it in my project?

PRConfig should be available in all LHCb applications. If not you may need to explicitly include it in your SetupProject statement:

<!-- SyntaxHighlightingPlugin -->
SetupProject SomeProject vXrY --use PRConfig 
<!-- end SyntaxHighlightingPlugin -->

If this does not work, please contact Marco Clemencic

- How can I use it in my package?

PRConfig should be available in all LHCb applications, but to access it during the qmtests in a given package you will need to declare it explicitly at run time, with a private cmt use statment in the requirements file.

<!-- SyntaxHighlightingPlugin -->
private
  use PRConfig v*
end_private 
<!-- end SyntaxHighlightingPlugin -->

If this does not work, please contact Marco Clemencic

- Can I maintain my own list of files in this way even if they are not for general consumption?

Yes! Please do. You can create a new database starting from a python dictionary and importing the base class object testfiles from TestFileObjects import testfiles.


Editing and adding

- Obtaining a local copy for editing

This obviously depends where (in which project) you're planning on adding the tests. The example below is for Moore, replace with your version.

<!-- SyntaxHighlightingPlugin -->
SetupProject Moore v21r0 --build-env
getpack PRConfig head
make
SetupProject Moore v21r0
#next line not always required, depends on the intricacies of cmt
cd PRConfig/cmt
source setup.sh
 
<!-- end SyntaxHighlightingPlugin -->

Edit, commit with release notes.

- Editing

In general make sure:

  • Your files are accessible for anyone who may run from the database. Usually this means they need to be at CERN on EOS, castor or in some public directory (DEV).
  • You can access the files without needing a grid certificate.
  • The files listed are PFNs.
  • You have added as much information as possible to the metadata of the files.
  • You have not missed any required metadata, the automatic script below will ensure you don't miss anything, or you can check with the TestReadable script: https://svnweb.cern.ch/trac/lhcb/browser/DBASE/trunk/PRConfig/scripts/TestReadable.py

Remember that this is a full python module, so any valid python to create the entries in the database is allowed, even something procedural.

- Automatic scripts for adding to the database:

If you already have a python file which adds test files through IOHelper or EventSelector there is a script which will copy this to the TestFileDB and ask you for the metadata.

To use this:

  1. Prepare local copy as above.
  2. Ensure you know the following information about your files:
    • What database tags were used in their creation? Please do work this out, it is possibly the most valuable piece of metadata about files in TestFileDB.
  3. Convert all LFNs to PFNs
  4. run the script
    • ./AddToTestFilesDB.py --help
    • ./AddToTestFilesDB.py someoptsfile_or_a_PFN

You can then check the files are readable for you with the script TestReadable.py: https://svnweb.cern.ch/trac/lhcb/browser/DBASE/trunk/PRConfig/scripts/TestReadable.py

- Automatic scripts for adding files to CERN-SWTEST/EOS:

ACTION RESTRICTED TO RELEASE MANAGERS

For files actually used in our automated nightly tests, especially centrally produced files we need to make sure they are not tied to the validity of a specific user account or production obsoletion cycle. So, please upload your files to the CERN-SWTEST element using the script provided:

To use this:

  1. Prepare local copy as above.
  2. Insert files into the TestFileDB as above, or manually
  3. Prepare your environment
    • You will need an environment with AppConfig, PRConfig, LHCbDirac and gaudirun.py. Again the example below is if you are using a base project of Moore
      <!-- SyntaxHighlightingPlugin -->
SetupProject LHCbDirac
SetupProject Moore v21r0 --use PRConfig --use AppConfig
#next line not always required, depends on the intricacies of cmt
cd PRConfig/cmt
source setup.sh
 
<!-- end SyntaxHighlightingPlugin -->
  1. Obtain a grid proxy:
    • lhcb_user: you will not be able to migrate existing production files to CERN_SWTEST
    • lhcb_prod: you can migrate any files at all
      <!-- SyntaxHighlightingPlugin -->
lhcb-proxy-init --group=lhcb-prod
 
<!-- end SyntaxHighlightingPlugin -->
  1. Execute the script:
    • ./MigrateToSWTEST.py --help
    • ./MigrateToSWTEST.py

You can then check the files are readable for you with the script TestReadable.py: https://svnweb.cern.ch/trac/lhcb/browser/DBASE/trunk/PRConfig/scripts/TestReadable.py

- Commit and use in nightlies

Don't forget to edit the release notes before you commit! Contact Marco Cattaneo and Rob Lambert if you want these files to be immediately accessible in the nightlies, and/or request a release of PRConfig by contacting Ben Couturier and Marco Clemencic.


-- RobLambert - 20 Jan 2014

 
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