-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modeled coverage #344
Modeled coverage #344
Conversation
message radio_hex_signal_level { | ||
uint64 hex_id = 1; | ||
signal_level signal_level = 2; | ||
double signal_power = 3; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
comment with type info?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
dBm, apparently
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we use a u32 or something like we do with IoT PoC and use ddbm? trying to avoid floats since they're massive and terrible language support
string location = 1; | ||
signal_level signal_level = 2; | ||
// Signal power of the radio in dBm (decibel-milliwatts) | ||
double signal_power = 3; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i see a resolved comment but no explanation? don't we typically have this type of field as uint32
or uint64
with the ddBm scale comment?
No description provided.