Package qa.database

Class QASoundLogging


public class QASoundLogging extends BufferedSQLLogging
SIDE logging class is going to have to do something a bit fancy to work out which sounds have been detected and by which detectors. Since these may include manually marking on displays, it's possible that detection data may only be available a long time after a sound has been generated. Will have to do something fancy such as keep a sound in a memory buffer for a fair old while, then log it anyway and be prepared to update it if another detector updates it.
Author:
dg50
  • Constructor Details

  • Method Details

    • setTableData

      public void setTableData(SQLTypes sqlTypes, PamDataUnit pamDataUnit)
      Description copied from class: SQLLogging
      Callback function when new data are created that allows the user to set the data for each column. Columns that have data which can be filled automatically (counters, primary keys and columns cross referenced to data in other tables) are filled automatically in fillTableData()
      Specified by:
      setTableData in class SQLLogging
    • checkDetectorList

      public void checkDetectorList(ArrayList<PamDataBlock> allDetectors)
      Check that all detectors have got a column in the database.
      Parameters:
      allDetectors -
    • logData

      public boolean logData(PamConnection con, PamDataUnit dataUnit, PamDataUnit superDetection)
      Description copied from class: SQLLogging
      Called when a new PamDataUnit is added to a PamDataBlock to write those data to the database. Functionality moved down to PamCursor so that exact writing method can become database specific if necessary.
      Overrides:
      logData in class BufferedSQLLogging
      Parameters:
      con - Database Connection
      dataUnit - Pamguard Data unit.
      superDetection - reference to a super detection so additional cross referencing can be filled
      Returns:
      true if written and new index of dataUnit retrieved OK
      See Also: