Is your feature request related to a problem? Please describe.
We need to start using the Central DB to pull module details for testing rather than the Purdue DB.
Describe the solution you'd like
There is a JSON file available online that stores basic information for all modules. There is also a JSON file for each module which stores more detailed information. Here are the steps that I imagine would work:
- Use the serial number of each module to look up basic information in the first JSON file, which is a sort of registry for all modules. There is a registry JSON file for each module type.
For Quad modules it is: https://cms-it-modules-registry.web.cern.ch/IT_Quad_Module.json
For Dual modules it is: https://cms-it-modules-registry.web.cern.ch/IT_Double_Module.json
- From the basic information, you need to get the
NAME_LABEL which is used to find the module-specific JSON file. For example, if we wanted to find the details for module SH0111, we would find it in https://cms-it-modules-registry.web.cern.ch/IT_Quad_Module.json and then pull the NAME_LABEL from it, which for SH0111 is "ITMOD-F34-LFR-007-020".
- Using the
NAME_LABEL from the previous step, we go to the JSON file using the format of https://cms-it-modules-registry.web.cern.ch/<NAME_LABEL>.json so in the case of SH0111 this would be "https://cms-it-modules-registry.web.cern.ch/ITMOD-F34-LFR-004-020.json". From that JSON file we can pull all of the information that we were previously pulling from the Purdue DB. The chip numbers should correspond to the ACROC_SLOT value. So chip 12 should be slot 0, chip 13 should be slot 1, etc.
Is your feature request related to a problem? Please describe.
We need to start using the Central DB to pull module details for testing rather than the Purdue DB.
Describe the solution you'd like
There is a JSON file available online that stores basic information for all modules. There is also a JSON file for each module which stores more detailed information. Here are the steps that I imagine would work:
For Quad modules it is: https://cms-it-modules-registry.web.cern.ch/IT_Quad_Module.json
For Dual modules it is: https://cms-it-modules-registry.web.cern.ch/IT_Double_Module.json
NAME_LABELwhich is used to find the module-specific JSON file. For example, if we wanted to find the details for module SH0111, we would find it in https://cms-it-modules-registry.web.cern.ch/IT_Quad_Module.json and then pull theNAME_LABELfrom it, which for SH0111 is "ITMOD-F34-LFR-007-020".NAME_LABELfrom the previous step, we go to the JSON file using the format of https://cms-it-modules-registry.web.cern.ch/<NAME_LABEL>.json so in the case of SH0111 this would be "https://cms-it-modules-registry.web.cern.ch/ITMOD-F34-LFR-004-020.json". From that JSON file we can pull all of the information that we were previously pulling from the Purdue DB. The chip numbers should correspond to theACROC_SLOTvalue. So chip 12 should be slot 0, chip 13 should be slot 1, etc.