Project

General

Profile

Feature #8297

RF parameters table

Added by Kyle Hazelwood over 4 years ago. Updated over 4 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
-
Start date:
04/09/2015
Due date:
% Done:

0%

Estimated time:
4.00 h
Duration:

Description

There currently is no way aside from searching the APPDB Sybase transaction logs to determine the last time any of the MI RF base parameters are altered. And even if you could find the time the parameters were altered the previous values are now gone.

The current scheme for saving these parameters is to maintain one row in appdb.wu.i3_parameters with all of these values. There are date_sent and date_updated columns in this table presumably to save this information but the values are not sent to the db correctly and always read 0. Each time changes are made, I3 deletes the current row and replaces it with a new row in [table.cpp > par_rec_w()]

Suggested changes:
  • Never erase any of the parameter data rows
  • Properly set the date column values
  • Retrieve the active row by selecting the row with the most recent date_sent value (like R2 does)
  • Post a message to the program log when the change is made, currently a message only goes out if the write fails

Related issues

Related to Main Injector RF Control Application (PA1677, I3) - Bug #8298: Inconsistent behavior when setting anode program past "Max HV"New04/10/2015

History

#1 Updated by Kyle Hazelwood over 4 years ago

appdb.wu.i3_parameters select privileges should also be set to "public" so I don't have to log in in as wu to read from the table.

#2 Updated by Kyle Hazelwood over 4 years ago

  • Subject changed from RF parameters tables to RF parameters table

#3 Updated by Kyle Hazelwood over 4 years ago

  • Related to Bug #8298: Inconsistent behavior when setting anode program past "Max HV" added


Also available in: Atom PDF