An example how to upload a stave config from Python

Adding an option to create a runkey Stave node from a dictionary which contains an "unpacked" YARR connectivity file: connectivity and chip configs in one file as:

$ head examples/sr1-barrel-st-4staves/CERNSR1_stave2_testing_setup_full.json
{
  "chipType": "Star_vH1A1",
  "chips": [
    {
      "config": {
        "name": "Stave2_PPB_hcc0",
        "HCC": {
          "ID": 2,
          "fuse_id": "400949",
          "regs": {
...

You can build a stave node from such a dictionary:

import functions_configDB as fxt
a_stave_runkey = fxt.build_stave_node_from_dict(stave_name, stave_cfg)

And then a standard upload procedure follows:

scripts/test_upload_a_stave.py

The upload should be simplified.

modified:   .gitlab-ci.yml
new file:   examples/sr1-barrel-st-4staves/CERNSR1_stave2_testing_setup_full.json
new file:   scripts/test_upload_a_stave.py

added 1 commit

• 8cf51dca - UP corrections

Compare with previous version

added 1 commit

• 18945e65 - Getting around to get the itsdaq number from HCC config

Compare with previous version

added 1 commit

• 6bda3c86 - Correct --translate option

Compare with previous version

added 1 commit

• 3652a3c6 - CI doesn't find the Root node

Compare with previous version

added 1 commit

• c672ae34 - What on Earth

Compare with previous version

added 1 commit

• 4717c684 - UP uploading runkey_root instead of the full runkey

Compare with previous version

added 1 commit

• cfdfeb13 - UP small examples to not trash CI log

Compare with previous version

added 1 commit

• fdd46e78 - Upload a blank template as a starting point for CI

Compare with previous version

added 1 commit

• 2166b23f - Fix the options that create their own runkey

Compare with previous version

added 1 commit

• 9e1c5c3b - You cannot re-upload a runkey from ConfigDB

Compare with previous version

added 1 commit

• dd748540 - UP the Python example

Compare with previous version

added 1 commit

• 1af6f463 - Avoid clashing on the configDBname

Compare with previous version

added 1 commit

• e87a4e3f - Fix

Compare with previous version

added 1 commit

• 44e26218 - To not clash on configDBname

Compare with previous version

There is a problem because you cannot re-upload to ConfigDB a recently downloaded runkey. The downloaded runkey contains more fields than what we typically upload. And it is simply not uploadable. It fails on some random stuff, with errors like "missing required field".

Which is crucial in this exercise: we download a runkey, modify it, and re-upload.

In the basic SR1 example, we just dump the runkey into files, and build a new one from the files, which results in an uploadable dictionary. But currently we cannot dump a temporary runkey into files. Because the SR1 procedure is hard-coded. The SR1 connectivity and stave names are hardcoded. And we have not broken it up into elementary procedures.

So, in --upload-stave I just create a blank runkey from a template, add a new stave node to it, and upload that.

We need both things fixed:

• ConfigDB must be able to receive a just downloaded runkey
• we should break up the SR1 example into elementary procedures

merged

mentioned in commit fa9ee04b