If you look in the full source for this file, there are probably more than 10 of these Q_ASSERT(UAVO obj). Just fixing one of them in this file will look sloppy and not help us establish best practices, as anyone unfamiliar will wonder why there's an asymmetry between this Q_ASSERT(attitudeSettings) and the two other Q_ASSERT(attitudeSettings) calls. I would rather fix them all at once, based on the conclusion of https://github.com/TauLabs/TauLabs/issues/223.