leahi-common

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
LDT-3505: Removed TREATMENT_PARAM_HEPARIN_STOP_TIME

Ya agreed. for the time being keeping it , we can later remove it after feature development complete

Ya agreed. for the time being keeping it , we can later remove it after feature development complete

LDT-1195: Renamed balancing chamber start state to idle state.

in other files when they use string and/or math headers they had specified a comment describing which functions are used from the headers.

in other files when they use string and/or math headers they had specified a comment describing which functions are used from the headers.

I am resolving it, but according to Sean, if we have a state which is just asking it to go to the next state, we might not need the state to be declared.

I am resolving it, but according to Sean, if we have a state which is just asking it to go to the next state, we might not need the state to be declared.

it is used for publish function in the bottom of this function publishAirPumpData();

it is used for publish function in the bottom of this function publishAirPumpData();

fixed

fixed

LEAHI-DD-FIRMWARE-LDT-1195_DD: Request for a variable for balancing chamber switching to be active (T/F)
LEAHI-DD-FIRMWARE-LDT-1195_DD: Request for a variable for balancing chamber switching to be active (T/F)
LDT-1195: Added balancing chamber idle state

its a standard c library , for that no need to comment. using ceil() function

its a standard c library , for that no need to comment. using ceil() function

This is a default framework for all modules, even though there is nothing right now, left it as it is.

This is a default framework for all modules, even though there is nothing right now, left it as it is.

I don't see it being used in this state. Do we need this?

I don't see it being used in this state. Do we need this?

I don't think we need a start state as this state is doing nothing. It is just transitioning to the next state. We can just directly start from the next state.

I don't think we need a start state as this state is doing nothing. It is just transitioning to the next state. We can just directly start from the next state.

I think we have to define macros for magic number.

I think we have to define macros for magic number.

Why NUM_OF_?

Why NUM_OF_?

Variable name suggests it is an action/cmd from UI. Comment suggests it is the number of actions. Which is it? And we should initialize in the init function - not here.

Variable name suggests it is an action/cmd from UI. Comment suggests it is the number of actions. Which is it?
And we should initialize in the init function - not here.

I think we have to include a comment specifying what function is being used from this file.

I think we have to include a comment specifying what function is being used from this file.

Is this really a timer counter? Looks like a flow rate.

Is this really a timer counter? Looks like a flow rate.

Updated

Updated

Added back

Added back

Updated

Updated

LDT-3344 merge Beta2.0 changes to develop

Bamboo Commit: Updated the Copyright section and replaced tabs with 4 spaces

LDT-3344 merge Beta2.0 changes to staging

I don't see why we need the extra precision here. I suspect a 64-bit division is expensive (s/w library implementation instead of co-processor) so I don't like to use doubles unless it is truly nec...

I don't see why we need the extra precision here. I suspect a 64-bit division is expensive (s/w library implementation instead of co-processor) so I don't like to use doubles unless it is truly necessary.