This is a list of all comments for HD-DEN-7395-1. Review Summary: No summary ---------------------------------------- File: firmware/App/Controllers/BloodLeak.c Revision Comment by qnguyen on 15 April 2021, 15:47 https://devapps.diality.us/cru/HD-DEN-7395-1#c9372 Recommend adding _MS to the end to indicate the metric in milliseconds. Reply by pmontazemi on 15 April 2021, 16:06 > Addressed. Reply by qnguyen on 19 April 2021, 10:32 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Dara Navaei on 11 April 2021, 20:48 https://devapps.diality.us/cru/HD-DEN-7395-1#c9161 I think it is a good practice to reset all the important variables that are defined as static in the .c file. Reply by pmontazemi on 12 April 2021, 19:44 > Addressed. Reply by Dara Navaei on 19 October 2023, 08:08 > RESOLVED in CODE WALKTHROUGH Revision Comment by Sean Nash on 11 April 2021, 16:31 https://devapps.diality.us/cru/HD-DEN-7395-1#c9153 Where did zeroBloodLeak() and selfTestBloodLeak() functions go? You have prototypes for them in .h and I think you still need at least one of them. zeroBloodLeak would be called by Pre-Treatment Mode and would tell FPGA to put sensor in zero state and would also put your state machine in zero state. Reply by pmontazemi on 12 April 2021, 19:35 > Addressed. Reply by Sean Nash on 19 April 2021, 10:40 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Dara Navaei on 11 April 2021, 20:50 https://devapps.diality.us/cru/HD-DEN-7395-1#c9162 I suppose this is not the monitor function and it is the exec function? Reply by pmontazemi on 12 April 2021, 10:04 > Addressed. Reply by Dara Navaei on 12 April 2021, 10:54 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Sean Nash on 08 April 2021, 10:31 https://devapps.diality.us/cru/HD-DEN-7395-1#c9082 Preferred architecture is to just set flag here and then let your state machine see the flag and change the state and command the fpga when it next executes. Reply by pmontazemi on 12 April 2021, 19:36 > Addressed. Reply by Sean Nash on 19 April 2021, 10:40 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Sean Nash on 12 April 2021, 10:21 https://devapps.diality.us/cru/HD-DEN-7395-1#c9186 I don't think we should have state as overrideable. Here, you are only looking at non-override version of state, so override would not have any impact anyway. You could have Dialin function force a transition to a given state - I think that would be useful from testing perspective. But transition would need to be more than just setting state - e.g. we would need to put sensor in zero state via FPGA if we wanted to go to the zero state in your state machine. Reply by pmontazemi on 12 April 2021, 19:44 > Addressed. Reply by Sean Nash on 19 April 2021, 10:39 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Sean Nash on 24 March 2021, 09:52 https://devapps.diality.us/cru/HD-DEN-7395-1#c8683 Check should only be done if not doing self-test. If doing self-test, a different (opposite) check should be done (if blood not detected within TBD ms, fault). Reply by pmontazemi on 08 April 2021, 01:55 > Addressed. Reply by Sean Nash on 08 April 2021, 10:36 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Sean Nash on 11 April 2021, 16:23 https://devapps.diality.us/cru/HD-DEN-7395-1#c9152 initBloodLeak() was already called from main in sys_main.c. I don't think we need to keep calling it here. How do we get out of INIT state? Reply by pmontazemi on 12 April 2021, 09:59 > Addressed. Reply by Sean Nash on 12 April 2021, 10:18 > But do we want to jump right into zero state or wait for > pre-treatment to ask for it? Does zero require fluid > (dialysate) to be in the line? Reply by pmontazemi on 12 April 2021, 19:35 > Addressed. Reply by Sean Nash on 19 April 2021, 10:40 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Sean Nash on 24 March 2021, 10:21 https://devapps.diality.us/cru/HD-DEN-7395-1#c8688 Alarm if in patient connected mode/sub-mode, fault if not. Reply by pmontazemi on 08 April 2021, 01:54 > Addressed. Reply by Sean Nash on 12 April 2021, 10:51 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Dara Navaei on 08 April 2021, 09:56 https://devapps.diality.us/cru/HD-DEN-7395-1#c9071 Usually the self tests return SELF_TEST_STATUS_T. Why does this function return a BOOL instead? Reply by Sean Nash on 08 April 2021, 10:19 > This is more of a request to run a self test by a mode > (probably pre-treatment mode), so I think boolean is > appropriate to indicate request was accepted. Reply by pmontazemi on 14 April 2021, 14:59 > No action item. Reply by Dara Navaei on 19 October 2023, 08:08 > RESOLVED in CODE WALKTHROUGH Revision Comment by Sean Nash on 08 April 2021, 10:27 https://devapps.diality.us/cru/HD-DEN-7395-1#c9080 Preferred architecture is to just set a request flag here and then let your state machine see the flag and change the state and command the FPGA action the next time it executes. Reply by pmontazemi on 12 April 2021, 19:36 > Addressed. Reply by Sean Nash on 19 April 2021, 10:41 > RESOLVED in CODE WALKTHROUGH. Revision Comment by qnguyen on 24 March 2021, 10:22 https://devapps.diality.us/cru/HD-DEN-7395-1#c8689 Remove this. No need to add if there are no parameters. Reply by pmontazemi on 25 March 2021, 09:19 > Addressed. Reply by qnguyen on 26 March 2021, 10:34 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Sean Nash on 08 April 2021, 10:29 https://devapps.diality.us/cru/HD-DEN-7395-1#c9081 Need to add state machine in this function. Call state handler functions from a switch statement. Reply by pmontazemi on 10 April 2021, 23:42 > Addressed. Reply by Sean Nash on 12 April 2021, 10:50 > RESOLVED in CODE WALKTHROUGH. Revision Comment by qnguyen on 09 April 2021, 10:31 https://devapps.diality.us/cru/HD-DEN-7395-1#c9108 Need to add call to this function from task priority. Reply by pmontazemi on 10 April 2021, 20:54 > Addressed. Reply by qnguyen on 12 April 2021, 10:57 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Sean Nash on 24 March 2021, 10:22 https://devapps.diality.us/cru/HD-DEN-7395-1#c8690 Do we need a get function for determining if/when zero is done? And another for determining if self-test passed/failed? Reply by pmontazemi on 12 April 2021, 19:37 > Addressed. Reply by Sean Nash on 19 April 2021, 10:42 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Dara Navaei on 13 April 2021, 08:57 https://devapps.diality.us/cru/HD-DEN-7395-1#c9231 Typecasting the variables is not needed here. The macro typecasts them. Reply by pmontazemi on 14 April 2021, 14:54 > Addressed. Reply by Dara Navaei on 19 April 2021, 10:35 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Sean Nash on 11 April 2021, 16:39 https://devapps.diality.us/cru/HD-DEN-7395-1#c9154 I imagine this state would need to look for zero to complete within some time period so we can tell FPGA to put sensor in self-test mode and set your state machine to self-test state. Fault if times out. Reply by pmontazemi on 12 April 2021, 19:35 > Addressed. Reply by Sean Nash on 19 April 2021, 10:40 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Sean Nash on 13 April 2021, 08:29 https://devapps.diality.us/cru/HD-DEN-7395-1#c9219 I would say this function requests that the blood leak detector be zeroed (and self-tested). Zero does not happen right here in this function. Reply by pmontazemi on 15 April 2021, 15:25 > Addressed. Reply by Sean Nash on 19 April 2021, 10:39 > RESOLVED in CODE WALKTHROUGH. Revision Comment by qnguyen on 08 April 2021, 10:27 https://devapps.diality.us/cru/HD-DEN-7395-1#c9079 getCurrentOperationMode() returns the current operation mode (standby, pre-treatment, treatment, post-treatment, etc.), not the sub-mode. Reply by pmontazemi on 12 April 2021, 19:36 > Addressed. Reply by qnguyen on 19 April 2021, 10:31 > RESOLVED in CODE WALKTHROUG Revision Comment by Sean Nash on 11 April 2021, 16:40 https://devapps.diality.us/cru/HD-DEN-7395-1#c9155 I imagine this state should look for self-test to pass (indicate a blood leak) within some time period and then we would tell FPGA to put sensor in normal state and set your state machine to normal state. Fault if times out. Reply by pmontazemi on 12 April 2021, 19:34 > Addressed. Reply by Sean Nash on 19 April 2021, 10:39 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Dara Navaei on 08 April 2021, 09:58 https://devapps.diality.us/cru/HD-DEN-7395-1#c9072 Can these two publish functions be lumped together? Reply by pmontazemi on 08 April 2021, 10:08 > They publish two different values that can be set > independently of each other. Reply by Sean Nash on 08 April 2021, 10:22 > But they could be packaged together into once blood leak > data broadcast message. Reply by pmontazemi on 08 April 2021, 14:59 > Addressed. Reply by Sean Nash on 12 April 2021, 10:51 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Sean Nash on 13 April 2021, 08:34 https://devapps.diality.us/cru/HD-DEN-7395-1#c9220 Consider checking for the Zero each time we execute this state (not just after timeout). Consider moving timeout to the alarm below (give zero time to happen, alarm if timeout). Consider giving alarm a little more than 10 ms (maybe 20 or 30ms) as 10ms is how long it will take to go from init to zero state (i.e. 10ms timeout will occur as soon as we get here). Reply by pmontazemi on 15 April 2021, 14:57 > Addressed. Reply by Sean Nash on 19 April 2021, 10:39 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Sean Nash on 13 April 2021, 08:43 https://devapps.diality.us/cru/HD-DEN-7395-1#c9226 Same comment as above re: timeout. Reply by pmontazemi on 15 April 2021, 14:58 > Addressed. Reply by Sean Nash on 19 April 2021, 10:37 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Sean Nash on 13 April 2021, 08:52 https://devapps.diality.us/cru/HD-DEN-7395-1#c9229 Should probably go to normal state on fail as well - otherwise you get stuck here in self-test state. Reply by pmontazemi on 15 April 2021, 14:58 > Addressed. Reply by Sean Nash on 19 April 2021, 10:37 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Dara Navaei on 13 April 2021, 08:51 https://devapps.diality.us/cru/HD-DEN-7395-1#c9228 Can we clear this alarm when it is raised? If no, do we need this else statement? Because if the alarm has not been raised, we do not need to clear it either. Reply by qnguyen on 13 April 2021, 10:06 > The clearAlarmCondition() function will check if the alarm is > active or not and only clears if the alarm has been raised. Reply by pmontazemi on 15 April 2021, 14:59 > No action item. Reply by Dara Navaei on 19 April 2021, 10:35 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Sean Nash on 13 April 2021, 08:47 https://devapps.diality.us/cru/HD-DEN-7395-1#c9227 I think better to use self test status enum (mentioned in .h comment). This enum will have pass/fail/in progress. I think if we're still in INIT, zero, or self-test state, in-progress is appropriate return value. I think you should have a BOOL variable defined to remember whether self-test passed or failed (instead of inferring from current state). Then if in normal state, return pass if self-test passed, failed if not. Reply by pmontazemi on 15 April 2021, 15:14 > Addressed. Reply by Sean Nash on 19 April 2021, 10:37 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Sean Nash on 09 April 2021, 10:43 https://devapps.diality.us/cru/HD-DEN-7395-1#c9109 So you combined the published data into one message in the publish function above which is correct. But these overrides must be separate. You should only override one thing at a time, so overrides were ok as it was before. Reply by pmontazemi on 09 April 2021, 20:20 > Addressed. Reply by Sean Nash on 12 April 2021, 10:50 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Dara Navaei on 13 April 2021, 08:42 https://devapps.diality.us/cru/HD-DEN-7395-1#c9225 Recommend typecasting bloodLeakState to (U32)bloodLeakState. Outside of this driver the enums are only U32s until they are converted to states again in Dialin. Reply by pmontazemi on 14 April 2021, 15:03 > Addressed. Reply by Dara Navaei on 19 April 2021, 10:36 > RESOLVED in CODE WALKTHROUGH. ---------------------------------------- File: firmware/App/Controllers/BloodLeak.h Revision Comment by Sean Nash on 13 April 2021, 08:25 https://devapps.diality.us/cru/HD-DEN-7395-1#c9218 There is a SELF_TEST_STATUS_T enum (pass/fail) defined in fwcommon Common.h. Consider returning this type instead of BOOL. Reply by pmontazemi on 15 April 2021, 15:03 > Addressed. Reply by Sean Nash on 19 April 2021, 10:39 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Dara Navaei on 11 April 2021, 20:40 https://devapps.diality.us/cru/HD-DEN-7395-1#c9159 The states of the state machine should be private. This enum should be transferred to the .c file. Reply by pmontazemi on 15 April 2021, 15:03 > Addressed. Reply by Dara Navaei on 19 October 2023, 08:09 > RESOLVED in CODE WALKTHROUGH Revision Comment by Dara Navaei on 11 April 2021, 20:42 https://devapps.diality.us/cru/HD-DEN-7395-1#c9160 Maybe I do not quite understand the architecture, but is there any reason that your are returning the state of the blood leak detector state machine? Reply by pmontazemi on 12 April 2021, 10:10 > Yes, Sean and I thought that it would be good for the SWVV, > SYSVV, MFR, and SVC Teams to know via Dialin API which state > the Blood Leak state machine is in. This detector comes with > an independent MCU thqat can be programmed and calibrated via > UART and via HD FPGA including self-test mode and zeroing > mode to zero the sensor when clear dialysate is run through > it. Then a threshold of blood can be set to be detected as > soon as blood gets across the dialyzer from the blood circuit > to the dialysate circuit. Reply by Dara Navaei on 12 April 2021, 10:55 > RESOLVED in CODE WALKTHROUGH. ---------------------------------------- File: firmware/App/Services/FPGA.c Revision Comment by Sean Nash on 24 March 2021, 09:42 https://devapps.diality.us/cru/HD-DEN-7395-1#c8678 Should be 0x1000? And shouldn't we add another mask for blood leak zero state (0x2000)? Reply by pmontazemi on 25 March 2021, 10:51 > Addressed. > > Had this as placeholder before looking at the schematics and > EE HRS/HDD docs. Reply by Sean Nash on 26 March 2021, 10:32 > RESOLVED in CODE WALKTHROUGH. Revision Comment by qnguyen on 24 March 2021, 10:27 https://devapps.diality.us/cru/HD-DEN-7395-1#c8692 This was temporary before a blood leak driver. Delete if not needed. Reply by pmontazemi on 25 March 2021, 16:02 > Deleted. Reply by qnguyen on 26 March 2021, 10:34 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Sean Nash on 01 April 2021, 08:55 https://devapps.diality.us/cru/HD-DEN-7395-1#c8891 Was this function temporary too? Reply by qnguyen on 02 April 2021, 10:36 > Yes. It should be removed or refactored once the actual blood > leak self-test functionality is implemented. Reply by pmontazemi on 12 April 2021, 19:37 > Addressed. Reply by Sean Nash on 19 April 2021, 10:41 > RESOLVED in CODE WALKTHROUGH. Revision Comment by qnguyen on 24 March 2021, 10:27 https://devapps.diality.us/cru/HD-DEN-7395-1#c8693 This was temporary before a blood leak driver. Delete if not needed. Reply by pmontazemi on 25 March 2021, 11:29 > Deleted. Reply by qnguyen on 26 March 2021, 10:33 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Sean Nash on 24 March 2021, 09:44 https://devapps.diality.us/cru/HD-DEN-7395-1#c8679 What about functions for 1) getting zero status, 2) setting sensor config (normal, self-test, zero)? Reply by pmontazemi on 12 April 2021, 19:37 > Addressed. Reply by Sean Nash on 19 April 2021, 10:42 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Sean Nash on 13 April 2021, 08:38 https://devapps.diality.us/cru/HD-DEN-7395-1#c9221 Should OR ( |= instead of = ) this bit into register so we don't interfere with other bits that may have been set by other drivers (e.g. bubble detector). Reply by pmontazemi on 15 April 2021, 15:16 > Addressed. Reply by Sean Nash on 19 April 2021, 10:38 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Sean Nash on 13 April 2021, 08:40 https://devapps.diality.us/cru/HD-DEN-7395-1#c9223 Should AND this bit off from register so we don't interfere with other bits that may have been set by other drivers (e.g. bubble detector). Should be something like fpgaActuatorSetPoints.fpgaSensorTest &= ~FPGA_BLOOD_LEAK_ZERO_CMD; Reply by pmontazemi on 15 April 2021, 15:16 > Addressed. Reply by Sean Nash on 19 April 2021, 10:38 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Sean Nash on 13 April 2021, 08:40 https://devapps.diality.us/cru/HD-DEN-7395-1#c9222 Should OR ( |= instead of = ) this bit into register so we don't interfere with other bits that may have been set by other drivers (e.g. bubble detector). Reply by pmontazemi on 15 April 2021, 15:17 > Addressed. Reply by Sean Nash on 19 April 2021, 10:38 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Sean Nash on 13 April 2021, 08:41 https://devapps.diality.us/cru/HD-DEN-7395-1#c9224 Should AND this bit off from register so we don't interfere with other bits that may have been set by other drivers (e.g. bubble detector). Should be something like fpgaActuatorSetPoints.fpgaSensorTest &= ~FPGA_BLOOD_LEAK_SELF_TEST_CMD; Reply by pmontazemi on 15 April 2021, 15:17 > Addressed. Reply by Sean Nash on 19 April 2021, 10:37 > RESOLVED in CODE WALKTHROUGH. ---------------------------------------- File: firmware/App/Services/SystemCommMessages.c Revision Comment by Sean Nash on 09 April 2021, 10:49 https://devapps.diality.us/cru/HD-DEN-7395-1#c9110 There is only one state in this override message. It can be status or state (depending on message ID), but not both. Whichever it is, you are passing it to a function twice as if it is two different things. You need to revert back to having two override messages and two message handlers - one for status and one for state. Reply by pmontazemi on 09 April 2021, 20:20 > Addressed. Reply by Sean Nash on 12 April 2021, 10:53 > RESOLVED in CODE WALKTHROUGH. ---------------------------------------- File: firmware/App/Services/SystemCommMessages.h Revision Comment by Sean Nash on 24 March 2021, 09:17 https://devapps.diality.us/cru/HD-DEN-7395-1#c8675 These need to be called from switch statement at bottom of SystemComm.c. Reply by pmontazemi on 25 March 2021, 09:42 > Addressed. Reply by Sean Nash on 26 March 2021, 10:32 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Sean Nash on 24 March 2021, 09:18 https://devapps.diality.us/cru/HD-DEN-7395-1#c8676 We should consider adding Dialin options to zero sensor and initiate self-test. Reply by pmontazemi on 12 April 2021, 19:37 > Addressed. Reply by Sean Nash on 19 April 2021, 10:42 > RESOLVED in CODE WALKTHROUGH. ---------------------------------------- File: firmware/source/sys_main.c Revision Comment by Sean Nash on 24 March 2021, 09:15 https://devapps.diality.us/cru/HD-DEN-7395-1#c8674 Move both leak monitors to monitors section above. Reply by pmontazemi on 25 March 2021, 09:29 > Addressed. Reply by Sean Nash on 26 March 2021, 10:32 > RESOLVED in CODE WALKTHROUGH. ---------------------------------------- File: firmware/App/Modes/ModePreTreat.c Revision Comment by Dara Navaei on 08 April 2021, 09:42 https://devapps.diality.us/cru/HD-DEN-7395-1#c9069 Recommend adding #defines for the temperature values. Reply by pmontazemi on 08 April 2021, 09:51 > [~qnguyen] Please address. Reply by qnguyen on 08 April 2021, 10:17 > Temperature values have been extracted out from treatment > parameters in HD-DEN-7091. Reply by Dara Navaei on 08 April 2021, 10:31 > RESOLVED in CODE WALKTHROUGH. ---------------------------------------- File: firmware/App/Modes/SelfTests.c Revision Comment by qnguyen on 15 April 2021, 15:48 https://devapps.diality.us/cru/HD-DEN-7395-1#c9373 This should be compare to SELF_TEST_STATUS_PASSED now. Reply by pmontazemi on 15 April 2021, 16:03 > Addressed. Reply by qnguyen on 19 April 2021, 10:22 > Keep the function and turn TRUE into > SELF_TEST_STATUS_PASSED. Reply by pmontazemi on 19 April 2021, 10:28 > Addressed. Reply by qnguyen on 19 April 2021, 10:34 > RESOLVED in CODE WALKTHROUGH. Revision Comment by qnguyen on 27 March 2021, 18:10 https://devapps.diality.us/cru/HD-DEN-7395-1#c8826 Recommend using the functions from blood leak driver. Reply by pmontazemi on 12 April 2021, 19:37 > Addressed. Reply by qnguyen on 19 April 2021, 10:32 > RESOLVED in CODE WALKTHROUGH. ---------------------------------------- File: firmware/App/Modes/SelfTests.h Revision Comment by qnguyen on 24 March 2021, 10:25 https://devapps.diality.us/cru/HD-DEN-7395-1#c8691 Why this one is deleted? Reply by pmontazemi on 25 March 2021, 16:02 > Addressed. Reply by qnguyen on 26 March 2021, 10:34 > RESOLVED in CODE WALKTHROUGH. ---------------------------------------- File: firmware/App/Modes/Dialysis.c Revision Comment by Sean Nash on 25 March 2021, 10:31 https://devapps.diality.us/cru/HD-DEN-7395-1#c8783 What happened here? Why are these deleted? Looks like a lot of content in this module has been removed. Need to restore. Reply by pmontazemi on 25 March 2021, 10:58 > Addressed. > > Note: I did a git pull on my hdfirmware branch (I should not > have done that). To get my code working, I had to remove. Reply by Sean Nash on 26 March 2021, 10:31 > RESOLVED in CODE WALKTHROUGH. ---------------------------------------- File: firmware/App/Services/SystemComm.c Revision Comment by Dara Navaei on 11 April 2021, 20:30 https://devapps.diality.us/cru/HD-DEN-7395-1#c9156 A break is needed here. Reply by pmontazemi on 12 April 2021, 10:08 > Good catch, addressed. Reply by Dara Navaei on 12 April 2021, 10:57 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Sean Nash on 08 April 2021, 10:13 https://devapps.diality.us/cru/HD-DEN-7395-1#c9074 What is the difference between this interval override and the one below? If monitor is broadcasting 2 different messages, why? Recommend combining published blood leak data into one message. Reply by pmontazemi on 08 April 2021, 10:23 > One is for the Blood Leak Detector status (blood leaked or > blood not leaked), and the other one is for the Blood Leak > Detector state of its state machine. This is just in case we > wanted to have independent control over these time constants. Reply by pmontazemi on 08 April 2021, 15:01 > Addressed. Reply by Sean Nash on 19 April 2021, 10:41 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Dara Navaei on 11 April 2021, 20:30 https://devapps.diality.us/cru/HD-DEN-7395-1#c9157 A break is needed here. Reply by pmontazemi on 12 April 2021, 10:08 > Good catch, addressed. Reply by Dara Navaei on 12 April 2021, 10:56 > RESOLVED in CODE WALKTHROUGH. Revision Comment by Dara Navaei on 11 April 2021, 20:31 https://devapps.diality.us/cru/HD-DEN-7395-1#c9158 A break is needed here. Reply by pmontazemi on 12 April 2021, 10:08 > Good catch, addressed. Reply by Dara Navaei on 12 April 2021, 10:56 > RESOLVED in CODE WALKTHROUGH. --- ID: HD-DEN-7395-1 https://devapps.diality.us/cru/HD-DEN-7395-1 Title: HD-DEN-7395_HD Blood Leak Detector Statement of Objectives: State: Closed Summary: Author: pmontazemi Moderator: pmontazemi Reviewers: (0 active, 3 completed*) qnguyen (*) Sean Nash (*) Dara Navaei (*)