conductivity_sensors.py

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Dara Navaei I only see this override function for "filtered" temperatures, but according to function name, it only applies to temperatures coming from pressure sensors. Why only pressure based temp...

Dara Navaei I only see this override function for "filtered" temperatures, but according to function name, it only applies to temperatures coming from pressure sensors. Why only pressure based temperatures?

LDT-2655: Updated enumeration references to handle integer arguments

  1. … 1 more file in changeset.
Sean Nash the override functions other than the standard override functions, (e.g. broadcast interval) are implemented as per needed.

Sean Nash the override functions other than the standard override functions, (e.g. broadcast interval) are implemented as per needed.

Dara Navaei please advise

Dara Navaei please advise

Are pressure sensor temperatures the only temperatures that get filtered? Why aren't we filtering all temperatures?

Are pressure sensor temperatures the only temperatures that get filtered? Why aren't we filtering all temperatures?

LDT-2658: Moved conductivity sensor override to DD temperatures module

  1. … 1 more file in changeset.
LDT-2658: Organized temperature functionality to temperatures module for DD and IOFP

  1. … 6 more files in changeset.
LEAHI-DIALIN-LDT-2658_Move IOFP pressure sensor temperature variables and override commands from the temperature module to the pressure module
LEAHI-DIALIN-LDT-2658_Move IOFP pressure sensor temperature variables and override commands from the temperature module to the pressure module
LDT-2300: Resolved code review comments

  1. … 40 more files in changeset.
Done - timestamps added to DD, FP, and TD

Done - timestamps added to DD, FP, and TD

Done

Done

Done

Done

Done

Done

I'm not sure I really understand the question here, but I do know that the DD Heaters data is being published with this handler: I've organized all heater data into a nested dictionary so that only...

I'm not sure I really understand the question here, but I do know that the DD Heaters data is being published with this handler: I've organized all heater data into a nested dictionary so that only one "variable" is being published. The same goes for the other publish functions before each handler. I will reorganize the order of the published variables so that timestamp is listed last.

No timestamp?

No timestamp?

I didn't see dbg variables in the publish list above.

I didn't see dbg variables in the publish list above.

Is msg_id_dd_heaters_data really being published here? Should it be? ** This comment applies to all classes as it appears you've done this everywhere. Also, I think we typically list the timestamp ...

Is msg_id_dd_heaters_data really being published here? Should it be? ** This comment applies to all classes as it appears you've done this everywhere.
Also, I think we typically list the timestamp last.

Replace "dg" with "dd".

Replace "dg" with "dd".

Replace "hd" with "dd".

Replace "hd" with "dd".

LDT-2300: Added message ID to each observer

  1. … 40 more files in changeset.
LEAHI-DIALIN-LDT-2300_Dialin: Add a way for a Dialin user to identify what broadcast message is being received
LEAHI-DIALIN-LDT-2300_Dialin: Add a way for a Dialin user to identify what broadcast message is being received
LDT-2301: Added subsystem to enum names

  1. … 13 more files in changeset.