Database integration in gScript

[cfangmeier]

Over in the pixel-gantry-extra there has been some work to create an interface for talking to the TFPX module tracking database. This is now tested and working. What remains to be done is to implement the Labview wrappers and the gScript commands to use them. I currently foresee 3 new commands that I'll describe below.

• DBLOGIN. This will present the user with a pop-up where they can enter in their username/password. These will be checked against the information in the database to verify the user. This will also open a connection to the database that will be kept open in the case of a successful login.
• DBFINDCOMP. This will open a window that will show a table of all constituent components (ie CROCs, RD53A's, or whatever is specified) that are located at the current assembly site. The user will then select items from the table and assign them positions that map to where they are physically located on the gantry table.
• DBSAVEASSEMBLY. This is run after completing an assembly and will
  1. Create a new "Assembled Module" component in the database
  2. Update the previously selected constituents to associate them with the assembled module
  3. Serialize and save any relevant assembly data to the tests table.

[cfangmeier]

The text blob that the DB uploads should be modified to fit the following template:

Test: Assembly Accuracy
Part: ZH0018
Date: 08/09/2022 03:53:42 PM
======================
ROC0 / Bottom Left
ROC0 Opening Angle: -7 um
ROC0 Slide: -50 um
-------------------
ROC1 / Top Left
ROC1 Opening Angle: -3 um
ROC1 Slide: 113 um
-------------------
ROC2 / Top Right
ROC2 Opening Angle: 23 um
ROC2 Slide: 92 um
-------------------
ROC3 / Bottom Right
ROC3 Opening Angle: 1 um
ROC3 Slide: -74 um
======================

[cfangmeier]

This implementation has been removed in 2.6 and will be replaced with a more generic interface that will work for both TFPX and ETL.