The LOAD_CELL_REPORT_PERIOD is 10 and this function gets called every 10ms - so this function produces and broadcasts a new set of averaged load cell weights every 100ms based on last 10 samples. This is what we talked about, but it took me a while to convince myself ot that. And if the priority task timing changes it will all fall apart. There is a TASK_PRIORITY_INTERVAL defined in TaskPriority.h as 10 (10ms interval) - if the task timing changes, this definition would also be changed. I would define LOAD_CELL_REPORT_PERIOD as ( 100 / TASK_PRIORITY_INTERVAL ) to couple it with task timing and clarify the desired report period is 100ms. I would also make a separate #define LOAD_CELL_SAMPLES_TO_AVERAGE and define it to be same as LOAD_CELL_REPORT_PERIOD just to clarify its other purpose (used in SensorProcess.h where it's folded into conversion factor).
Some of the comments about the spacing are in our c coding standards and not in our C++ coding standard. From the beginning we discussed that these may/should be different.
uint QVariant::toUInt(bool *ok = nullptr) const Returns the variant as an unsigned int if the variant has userType() QMetaType::UInt, QMetaType::Bool, QMetaType::QByteArray, QMetaType::QChar, QMetaType::Double, QMetaType::Int, QMetaType::LongLong, QMetaType::QString, or QMetaType::ULongLong; otherwise returns 0.
Files has been modified many times manuallu on my branch as you asked a week or toow before 2020 and by Dara's script on master on 2019 and 2020. It might be me merging files from my branch to master with 2019, since I think his script is running only on master branches.
Files has been modified many times manuallu on my branch as you asked a week or toow before 2020 and by Dara's script on master on 2019 and 2020. It might be me merging files from my branch to master with 2019, since I think his script is running only on master branches.
These are necessary QTest methods that I don't have any implementation for them yet. I didn't like the fact that although I don't have anything implemented, it's still counts as a successful test, so I comment them out for now until I have an implementation for them. In general I prefer not to remove thme to keep them as part of the standard QtTest class.
