View source for PV Maintenance Process/Status

Summer of 2020: 

Python scripts: [[File: Python_Materials.zip ]]

Python script was written to compile all PVs from files and then cross reference them with the Software Field Names to identify where each was invoked and which were never invoked.

First script compiles and creates a sheet with the Screen File in Column A and the PVs in Column B.

Next Script reads through the Digitizer Spreadsheet to put on the second sheet the Register Name (sans array) in Column A, Register Name in Column B, EPICS Type in Column C, Software Field Name in Column D, Human Field Name in Column E. 

The process for the third sheet is done for the Master Trigger and the fourth sheet for the Router Trigger.

Afterwards a script goes through to try to match each of the Software Field Names to the PVs in the first sheet. If a match is found, the screen name in it's adjacent column is written in Column F. To gain a better sense of what edits were truly necessary, a line was added in the code to distinguish between written PVs and readback PVs.

When that was done, at times it was necessary to go back manually to see if any PVs were missed from Sheet 1 (most common are substitution PVs in which the path you took to arrive at the PV matters).

Despite this bit of human intervention, a majority of time could still be saved if more PVs need to be sorted in the future with either this code or a modified version of it.

06/25/2020 - Currently the spreadsheets are up to date with identifying which PVs belong on which screens and which are only for Engineers to mess with.