reverted back
fixed
RESOLVED
This value should come from configuration.
I don't think these coefficient access functions need to be public. Consider making them private.
fix the comment (x67).
Added before the pre treatment page
corrected the invalid syntax and added the space between the function
Add a comment: result already FALSE - do nothing more for modes that do not support jump to sub-mode.
Are these coming back? If so, add TODO comment to restore later. If not, delete them.
Remove this.
Add blank line after declarations.
updated.
Done.
Just following the current style of code implementation to keep it uniform. These defines are temporary and will be removed.
Updated.
I believe we will want BC control during ISO UF state.
This will be implemented in a subsequent story.
Align "="
Verified that placement is correct.
added existing objects to names.py file.
Nicholas Ramirez Could you please recheck, I don't see the updated change.
updated
Remove blank line.
are we using this variable, if not, can we remove across the file?
RESOLVED.
Fix alignment of "=".
Close start on confirm to go back to main treatment.
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?
done.
Added
I think we should just have == here so that we only warn them once.
Name in brief doesn't match function name.
The configuration is from Denali. Please lets port in what we are using into a new one as part of this test suite
This is a structure, not an enumeration.
is this a python lib or is this made by us?
Remove spaces before "=" or align "=".
Added new configuration file utility.py for Leahi.
Please make keep all existing object as they are required for the other test cases.
align each parameter as well please
remove duplicate import
Remove this import as its not being used
update all temp -> tmp and Temperature - > Trancememberance
in_range_color and out_of_range_color are not being used so please remove
Got a suggestion or an issue? Discuss it on the Atlassian Community or visit Atlassian Support for other options.
