Skip to content

Ping Info Update - #39

Open
CaptKrasno wants to merge 2 commits into
apl-ocean-engineering:ros2from
USF-COMIT:ros2
Open

Ping Info Update#39
CaptKrasno wants to merge 2 commits into
apl-ocean-engineering:ros2from
USF-COMIT:ros2

Conversation

@CaptKrasno

Copy link
Copy Markdown
Collaborator

I have made the changes discussed in issues #38 #35 #33 #24

I want to do a more thorough documentation review before we merge this pull request but I figured I would post it so you @lauralindzey @rolker could take a look. No sense documenting things if we're going to change them.

I have not added steering geometry discussed in #36 to this pull request, Instead focusing on the changes to PingInfo

@CaptKrasno
CaptKrasno requested a review from lauralindzey March 10, 2023 21:43
@CaptKrasno CaptKrasno self-assigned this Mar 10, 2023

# the ping number reported by the sonar.
# useful for matching multiple message types for a given ping
uint64 ping_no

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd prefer to spell out "number"

# if the image is not reported at the full resolution
# ping_info.sample_rate != image_sample_rate
# for a given sample:
# 2-way travel time = image_sample_rate*(sample_no+sample0)

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This equation doesn't match how I expect "rate" to be used -- here, image_sample_rate has units of seconds, so I'd have expected it to be called "sampling period".

can we change this to be (sample_number + sample0) / image_sample_rate?

@lauralindzey

Copy link
Copy Markdown
Collaborator

@CaptKrasno -- mostly looks good to me, and I appreciate the clear comments describing the rationale for each field =)

  • I added a few comments about nomenclature
  • 'you'll need to fix a few spelling issues that the CI caught.
  • Can you also add a bag migration rule? I have a lot of bagfiles that I need to keep using, so being able to run rosbag fix has become pretty important.

I think we should try to get this in (along with a few others) before we make an official v2 release and resubmit to rosdistro.

@lauralindzey

Copy link
Copy Markdown
Collaborator

I have made the changes discussed in issues #38 #35 #33 #24

I don't see the changes associated with #38? Did you forget to add that file?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants