leahi-dialin / leahi_dialin / td / modules

blood_flow.py

Clone Tools

Stats

Commits this week: 0
Total Committers: 5
Last Commit: 09:54
Commits this week: 0

Lines of code count not available

Commit Activity

Commits By Day In Week
52 week commits volume
Commits By Day In Week
Commits by day
Commits By Day In Week
Commits by hour
Commits By Hour In Day
Commit calendar
 

Most active committers (90 days)

loading
loading
  • last updated a few seconds ago
All Commits Reviews
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Tuesday 09 Dec
2:27 pm

Sean Nash

Why do we have an "ro" and an "fp" folder? Is "ro" folder obsolete (replaced by "fp")?

Why do we have an "ro" and an "fp" folder? Is "ro" folder obsolete (replaced by "fp")?

2:18 pm

Sean Nash

Isn't timestamp typically first (or last) in publish list?

Isn't timestamp typically first (or last) in publish list?

Monday 08 Dec
8:15 am

Dara Navaei

LEAHI-DIALIN-LDT-2655_Cannot override conductivity sensor temperature from the conductivity module
LEAHI-DIALIN-LDT-2655_Cannot override conductivity sensor temperature from the conductivity module
Wednesday 12 Nov
11:13 am

Dara Navaei

10:46 am

Behrouz NematiPour

Monday 10 Nov
9:54 am

Sean Nash

Saturday 08 Nov
4:58 pm

Dara Navaei

Done

Done

4:58 pm

Dara Navaei

Done

Done

4:29 pm

Dara Navaei

LDT-1886 added baro pressure sensor and replace the blood flow's current field with torque

Options
    • -5
    • +2
    ./blood_flow.py
  2. … 2 more files in changeset.
Friday 07 Nov
9:26 am

Dara Navaei

Tuesday 21 Oct
11:04 am

Sean Nash

Monday 20 Oct
4:54 pm

Dara Navaei

Thursday 16 Oct
12:55 pm

Sean Nash

I don't think we have motor current. We're getting torque instead. Just replace current with torque.

I don't think we have motor current. We're getting torque instead. Just replace current with torque.

12:54 pm

Sean Nash

I think we should replace motor current with torque instead of adding torque as new field.

I think we should replace motor current with torque instead of adding torque as new field.

Wednesday 15 Oct
5:15 pm

Dara Navaei

LEAHI-DIALIN-LDT-1886_Blood Set Auto-Load and Auto-Eject - TD
LEAHI-DIALIN-LDT-1886_Blood Set Auto-Load and Auto-Eject - TD
5:10 pm

Dara Navaei

LDT-1886 added blood pump torque

Options
    • -1
    • +4
    ./blood_flow.py
  2. … 1 more file in changeset.
Wednesday 08 Oct
2:49 pm

Michael Garthwaite and jpaguio  (deleted user)

2:36 pm

Sean Nash

Merged staging to LDT-2199.

Options
    • -3
    • +3
    ./blood_flow.py
  2. … 1 more file in changeset.
Thursday 25 Sep
2:42 pm

jpaguio  (deleted user)

2:35 pm

Dara Navaei and Sean Nash

2:32 pm

Dara Navaei

LDT-2199 added a command to hard stop the TD blood pump

Options
    • -0
    • +24
    ./blood_flow.py
  2. … 1 more file in changeset.
12:57 pm

Jonny Paguio <jpaguio@diality.com>

LDT-2300: Resolved code review comments

Options
    • -1
    • +1
    ./blood_flow.py
  2. … 40 more files in changeset.
12:16 pm

jpaguio  (deleted user)

Done - timestamps added to DD, FP, and TD

Done - timestamps added to DD, FP, and TD

12:13 pm

jpaguio  (deleted user)

Done

Done

12:12 pm

jpaguio  (deleted user)

Done

Done

12:11 pm

jpaguio  (deleted user)

Done

Done

Monday 22 Sep
2:26 pm

jpaguio  (deleted user)

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.

9:48 am

Sean Nash

No timestamp?

No timestamp?

9:45 am

Sean Nash

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

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

9:44 am

Sean Nash

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.