Services

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Uncommented

Uncommented

Remove extra blank line.

Remove extra blank line.

Why is this service prefixed with "Tx"? Also, Praneeth and I agreed to put these state machine services into a sub-folder of Services. See how he did it and do the same.

Why is this service prefixed with "Tx"?
Also, Praneeth and I agreed to put these state machine services into a sub-folder of Services. See how he did it and do the same.

DrySelfTests unit.

DrySelfTests unit.

DrySelfTests unit initialized.

DrySelfTests unit initialized.

Remove extra blank line.

Remove extra blank line.

.. handles dry self-tests execution for pre-treatment and treatment modes.

.. handles dry self-tests execution for pre-treatment and treatment modes.

Should be in "", not <>. And should be placed alphabetically down before TxParams.h.

Should be in "", not <>. And should be placed alphabetically down before TxParams.h.

Calling signal function here seems circular (that's how we got here in the first place). Shouldn't we set state to the install state here instead?

Calling signal function here seems circular (that's how we got here in the first place).
Shouldn't we set state to the install state here instead?

Put before TxParams.

Put before TxParams.

I think Praneeth created a function for this. Make sure they're identical.

I think Praneeth created a function for this. Make sure they're identical.

Is the folder name necessary?

Is the folder name necessary?

Remove unnecessary spaces before =

Remove unnecessary spaces before =

Align =

Align =

Align =.

Align =.

Align =.

Align =.

We don't have to align =, but if you're going to have all of these spaces before the =, you should align.

We don't have to align =, but if you're going to have all of these spaces before the =, you should align.

Why are we doing this? Having a return here is against our coding standards (it's like a goto).

Why are we doing this?
Having a return here is against our coding standards (it's like a goto).

Describe what kind of services are being provided.

Describe what kind of services are being provided.

Consider separating the wait for door close to another state.

Consider separating the wait for door close to another state.

Why are we doing this?

Why are we doing this?

Describe what kind of services being provided.

Describe what kind of services being provided.

Should not change states in a signal function. Should set a request flag that gets looked at in dry self-tests state handler function which would return install state if the flag is set.

Should not change states in a signal function. Should set a request flag that gets looked at in dry self-tests state handler function which would return install state if the flag is set.

I don't think we should change this.

I don't think we should change this.

Not sure this makes sense. Time is in minutes. min * mL/min = mL (makes sense). min * L/hr = minL/hr (does not make sense). Talk to Raghu about UF rate units and when we should use mL/min vs. L/hr.

Not sure this makes sense. Time is in minutes. min * mL/min = mL (makes sense). min * L/hr = minL/hr (does not make sense).
Talk to Raghu about UF rate units and when we should use mL/min vs. L/hr.

We should just have 1 of these. Let's have TD always working in mL and mL/min, and we'll just convert before sending to UI or after receiving from UI.

We should just have 1 of these. Let's have TD always working in mL and mL/min, and we'll just convert before sending to UI or after receiving from UI.