StateServices

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 doing this in blood prime? Wouldn't it be easier to do this when we're done w/ rinseback & recirc?

Why are we doing this in blood prime? Wouldn't it be easier to do this when we're done w/ rinseback & recirc?

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

While you are updating this file, can please break this line?

While you are updating this file, can please break this line?

Can we align like this result = u32BroadcastIntervalOverride( message, &preTreatmentStatePublishInterval, TASK_GENERAL_INTERVAL );

Can we align like this
result = u32BroadcastIntervalOverride( message,
&preTreatmentStatePublishInterval,
TASK_GENERAL_INTERVAL );

Add to inputs: preTreatmentStatePublishInterval

Add to inputs: preTreatmentStatePublishInterval

Updated to store the result in a local BOOL

Updated to store the result in a local BOOL

Set to local BOOL and then return the BOOL.

Set to local BOOL and then return the BOOL.

Make a #define up top for the 5.

Make a #define up top for the 5.

Initialize this in the init function instead of here.

Initialize this in the init function instead of here.

Yes,I Added the Dial-in override function for the publish interval.

Yes,I Added the Dial-in override function for the publish interval.

Are we going to allow Dialin to override this publish interval?

Are we going to allow Dialin to override this publish interval?

Add a blank line before return statement.

Add a blank line before return statement.