I would add 2 spaces after single digit numbers, 1 space after double digit numbers, and no space after triple digit numbers. This will make them all align.
It's just a placeholder for now. It's currently set so that a 0 to 600 mL/min ramp will take 1 second. For the moment it's fixed. Blaine said he may fix it in the motor controller once we understand our needs better so firmware may not have to worry about it in the end anyway.
U32 is unsigned 32 bit integer. S32 is signed 32 bit integer. F32 is float. These are possible types of data that we might want to log with the triggering of an alarm (e.g. if we get a high pressure alarm, what was the pressure that triggered it?).
I'm ok with sleep generally, but not sure it's appropriate here as it is currently implemented. Here, it appears we're pacing ourselves at no more than 1000 (packets or messages?) per second. Maybe ok over time or maybe not - what if we're publishing more than 1000 packets per second when all is said and done? But even if we're not publishing that many packets, I imagine data may come in spurts that will exceed this pace. Is there a buffer holding received packets until this loop "receives" them? If so, how deep is the buffer? If not, I fear we may drop some packets.
Behrouz, If you are suggesting a change wrt PEP8 coding standard, that is fine. But, you will also need to make that change to our Python coding standard, which is currently an exact copy of the PEP8 coding standard for Python. What is the decision?
