DBBC3Validation_OCT_D_120 class

class DBBC3Validation_OCT_D_120(dbbc3, ignoreErrors)

Bases: DBBC3ValidationDefault

class with validation methods specific to the OCT_D 120 mode

Parameters
  • dbbc3 (DBBC3) – the active DBBC3 instance

  • ignoreErrors (boolean) – If True do not exit processing in case of validation failures

restoreState()

Restores the state of the DBBC3 according to the state that was previously saved upon initialization

validateBitStatistics(boardNum)

Validate the bit statistics for all samplers of the specified board

Parameters

boardNum (int or str) – the board number (starting at 0=A) or board ID (e.g “A”)

Returns

the validation report

Return type

ValidationReport

validateBitmask(boardNum, bandwidth, exitOnError=True)

Validates the vsi bitmasks for the specified board

Note

valid bandwidth parameter values are 2000,1000,500,250 even though the true filter bandwidths are powers of two (e.g 2048 etc.)

Parameters
  • board (int or str) – the board number (starting at 0=A) or board ID (e.g “A”)

  • bandwidth (int) – the bandwidth of the tap filters in MHz (see note above)

Returns

the report containing the validation results

Return type

ValidationReport

validateFilter(board, filterNum, filterFile, checkBitmask=True, exitOnError=True)

Validate the loaded filter file for the specified board

In case the checkBitmaks parameter is set an additional check is done to validate that the vsi bitmasks match the band widths of the selected filters. Should the band widths of the two OCT filters differ the bit mask is validated to match the bandwidth of the wider of the two filters.

Parameters
  • board (int or str) – the board number (starting at 0=A) or board ID (e.g “A”)

  • filterNum (int) – the filter number (must be 1 or 2)

  • filterFile (str) – the name of the filter file to be validated

  • checkBitmask (boolean) – If true also vallidate that the vsi bitmask matches the filter band width

  • exitOnError (boolean) – if True any error will cause a program exit

Returns

the report containing the validation results

Return type

ValidationReport

validateIFLevel(board, downConversion=True, agc=True)

Performs various validations of the IF power settings as obtained from the dbbcif command:

  • IF power should be within 1000 counts of the target value

  • The attenuation setting should be within 20-40

  • AGC should be switched on (unless disabled by the agc parameter)

  • Downconversion should be switched on (unless check is disabled with the downConversion parameter)

Parameters
  • board (int or str) – the board number (starting at 0=A) or board ID (e.g “A”)

  • downConversion (boolean, optional) – If True validate that downconversion is enabled (default: True)

  • agc (boolean, optional) – If True validate that agc is turned on (default: True)

Returns

the validation report

Return type

ValidationReport

validatePPS(maxDelay=200, exitOnError=True)

Validates the delay between the internally generated and external PPS signals. The validation is carried out for all all active boards of the DBBC3. The validation fails in case any of the PPS delays is exceeding +-maxDelay nanoseconds (configurable).

Parameters
  • board (int or str) – the board number (starting at 0=A) or board ID (e.g “A”)

  • maxDelay (int) – the maximum valid delay in nanoseconds

  • exitOnError (boolean) – if True any error will cause a program exit

Returns

contains the validation report

Return type

ValidationReport

validateSamplerOffsets(board, targetCount=32000)

Validates the sampler offsets

Parameters
  • board (int or str) – the board number (starting at 0=A) or board ID (e.g “A”)

  • targetCount (int, optional) – the total power count at which the validation should be carried out. Defaults to 32000.

Returns

the report containing the validation results

Return type

ValidationReport

validateSamplerPhases()

Validates that all sampler phases for all boards are synchronized

Returns

the validation report

Return type

ValidationReport

validateSamplerPower(boardNum)

Validates the sampler powers (gains)

Parameters

board (int or str) – the board number (starting at 0=A) or board ID (e.g “A”)

Returns

the report containing the validation results

Return type

ValidationReport

validateSynthesizerFreq(board, targetFreq=0.0, exitOnError=True)

Validates the actual tuning frequency of the GCoMo synthesizer serving the given board against the target value as specified by the last synthFreq command or the value in the DBBC3 configuration file.

If the parameter targetFreq is set to a value > 0 an additional check is performed against that frequency.

Parameters
  • board (int or str) – the board number (starting at 0=A) or board ID (e.g “A”)

  • targetFreq (float) – the synthesizer frequency in MHz

  • exitOnError (boolean) – if True any error will cause a program exit

Returns

contains the validation report

Return type

ValidationReport

validateSynthesizerLock(board, exitOnError=True)

Validates that the synthesizer serving the given board is locked

Parameters
  • board (int or str) – the board number (starting at 0=A) or board ID (e.g “A”)

  • exitOnError (boolean) – if True any error will cause a program exit

Returns

contains the validation report

Return type

ValidationReport

validateTimesync(board, exitOnError=True, maxDelay=5)

Validates the time synchronisation of the specified core3h board

Validation fails in case:

  • not valid time stamp could be obtained from the DBBC3

  • the DBBC3 time deveates by more than maxDealy seconds (configurable) from the local NTP time

Failure could indicate that the GPS antenna is not properly connected to the DBBC3 or no GPS satelites were visible on system initialization. Also make sure that the local computer has its time synchonized by NTP.

Parameters
  • board (int or str) – the board number (starting at 0=A) or board ID (e.g “A”)

  • exitOnError (boolean) – if True any error will cause a program exit

  • maxDelay (int) – the maximum valid time delay in seconds

Returns

contains the validation report

Return type

ValidationReport