Monitors

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
I thought Eliza said they wanted to do blood sitting timer even if blood was rinsed back (still a little blood in line).

I thought Eliza said they wanted to do blood sitting timer even if blood was rinsed back (still a little blood in line).

Why are we changing the rank of an existing alarm?

Why are we changing the rank of an existing alarm?

These new functions should be above the test functions. Please align with the Messaging.c file. It looks correct in the Messaging.c file.

These new functions should be above the test functions.

Please align with the Messaging.c file.
It looks correct in the Messaging.c file.

Move this above the test functions.

Move this above the test functions.

What is the use case of this header include?

What is the use case of this header include?

add space in [ ]

add space in [ ]

align comments

align comments

Should these three alarms be moved after alarm 852? It looks like 999 is currently placed before 852.

Should these three alarms be moved after alarm 852?

It looks like 999 is currently placed before 852.

break this line

break this line

Add @message id MSG_ID_TD_UI_GENERIC_CONFIRMATION_REQUEST

Add @message id MSG_ID_TD_UI_GENERIC_CONFIRMATION_REQUEST

break this line

break this line

break this line

break this line

Update function name: handleRinsebackAdditionalState

Update function name: handleRinsebackAdditionalState

Thank you for clarifying!

Thank you for clarifying!

Thank you for clarifying!

Thank you for clarifying!

Add cumulativeBloodPrimeVolume_mL to ouputs. Optional: While you are updating, can you please also add bloodPrimeRampFlowRate_mL_min and bloodPrimeState to the inputs?

Add cumulativeBloodPrimeVolume_mL to ouputs.

Optional: While you are updating, can you please also add bloodPrimeRampFlowRate_mL_min and bloodPrimeState to the inputs?

Add recircAllowed to outputs.

Add recircAllowed to outputs.

Thank you for clarifying!

Thank you for clarifying!

What if we're in paused state (because your alarm has stop property set)? Should we return TRUE here if in paused state and interrupted state was the await syringe load confirmation state?

What if we're in paused state (because your alarm has stop property set)? Should we return TRUE here if in paused state and interrupted state was the await syringe load confirmation state?

Right now, the load syringe alarm indicates stop so we will go to paused state. Is that what we want to do? Don't we want to stay in this state and wait for confirmation?

Right now, the load syringe alarm indicates stop so we will go to paused state. Is that what we want to do? Don't we want to stay in this state and wait for confirmation?

Should this alarm have stop property set to FALSE?

Should this alarm have stop property set to FALSE?

initialized using resetRinsebackFlags()

initialized using resetRinsebackFlags()

those are initialized in resetTreatmentRecircFlags() and that is called in init

those are initialized in resetTreatmentRecircFlags() and that is called in init

align comment

align comment

use FALSE

use FALSE

use FALSE

use FALSE

It looks like the rows may be misaligned with the alarm ID declarations. For example, ALARM_ID_TD_BATTERY_CHARGER_ERROR_DETECTED is declared as 204.

It looks like the rows may be misaligned with the alarm ID declarations.
For example, ALARM_ID_TD_BATTERY_CHARGER_ERROR_DETECTED is declared as 204.