Dashboard

Looks the fields are empty and misaligned. fill as needed.

Looks the fields are empty and misaligned. fill as needed.

removed

removed

updated

updated

LDT-3418 HDF - SW - 01 - Main-Tx HDF Tab - Graph - R&I - 05: DEV - Feature Implementation

address cr comments

    • -2
    • +1
    /sources/gui/qml/components/BaseChart.qml
    • -1
    • +0
    /sources/gui/qml/components/HeaderBar.qml
Merge remote-tracking branch 'origin/staging' into feature/LDT-3413-hdf-main-tx-hdf-graph

    • -10
    • +3
    /sources/gui/qml/components/HeaderBar.qml
source removed

source removed

LDT-3579 Misc SW Enhancements - SW - 01 - General Aesthetics - 02-S24 - R&I - 05: DEV - Feature Implementation

    • -32
    • +12
    /sources/gui/qml/pages/treatment/TreatmentHome.qml
LDT-3103 updated fill timeout alarm logic and handling

LEAHI-DIALIN-LDT-1394_Blood Flow Rate - TD - 04: DEV - Feature Implementation
LEAHI-DIALIN-LDT-1394_Blood Flow Rate - TD - 04: DEV - Feature Implementation
LDT-1394 fixed the equation based on Nick's updated co-eff's

    • -72
    • +92
    /firmware/App/Controllers/BloodFlow.c
LDT-1394 updated override request for stroke volume

LDT-1394 updated override function for stroke volume

    • -14
    • +14
    /leahi_dialin/td/modules/blood_flow.py
LDT-1195: Updated function comments and requestBalChamberSwitching

    • -2
    • +0
    /firmware/App/Modes/ModeGenDialysate.c
Remove extra blank line.

Remove extra blank line.

Should we create a structure for these moving average filters and make an array of them based on enum of temp sensors? It looks kind of messy having separate handling for each sensor - can we conso...

Should we create a structure for these moving average filters and make an array of them based on enum of temp sensors?
It looks kind of messy having separate handling for each sensor - can we consolidate some of this code?

Should we maybe just have a constant array of sample counts based on enum of temp sensors?

Should we maybe just have a constant array of sample counts based on enum of temp sensors?

Should min and max be properties of the controller instead of global (assumes all controllers will want same min/max)? Controller properties already include a min and max field - can we use those?

Should min and max be properties of the controller instead of global (assumes all controllers will want same min/max)?
Controller properties already include a min and max field - can we use those?

Remove blank line.

Remove blank line.

LDT-3223-dialysate-flow-rate---dd---mode-tel-dev-test : Added testcases for TemperatureSensors file

LDT-3223-dialysate-flow-rate---dd---mode-tel-dev-test : Added test cases for Heaters.c file

LDT-3223-dialysate-flow-rate---dd---mode-tel-dev-test : Added test cases for InternalADC.c file

LDT-3122 Blood Prime - SW - 02 - Q&R - 15: SIT - Software Integration Tests - Squish Qt

LDT-3122 Blood Prime - SW - 02 - Q&R - 15: SIT - Software Integration Tests - Squish Qt

LDT - 2953 Rinseback - SW - 02 - Q&R - 15: SIT - Software Integration Tests - Squish Qt

    • -19
    • +17
    /suite_leahi/shared/scripts/names.py
    • -21
    • +27
    /suite_leahi/tst_rinseback/test.py
LDT-3122 Blood Prime - SW - 02 - Q&R - 15: SIT - Software Integration Tests - Squish Qt

    • -0
    • +10
    /suite_leahi/shared/scripts/names.py
    • -0
    • +476
    /suite_leahi/tst_blood_prime/test.py