-
Notifications
You must be signed in to change notification settings - Fork 57
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
feat(interaction): Added LidarUpdates interaction and LidarData object #391
Conversation
|
||
import javax.annotation.Nonnull; | ||
|
||
public interface LidarApplication extends Application { |
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.
This class needs to be documented before being merged.
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 think this PR goes in the right direction but needs some further fine-tuning. I left a sloppy initial review with some concerns.
import java.util.List; | ||
import java.util.stream.Collectors; | ||
|
||
public class LidarUpdates extends Interaction { |
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.
This class needs some more documentation before being merged
|
||
|
||
|
||
public LidarUpdates(long time, List<LidarData> updated) { |
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.
For me it isn't clear what exactly the list of updated LidarData
is made-up of.
- Is it lidar data for all ego-vehicles at
time
? - Is it lidar data for one ego-vehicle at
time
?
This kind of stuff should be documented.
As far as I get, each ego-vehicle has a LidarData-Object for each lidar-collection-time, which contains the measured point clouds, right?
private final Object lidarData; | ||
|
||
private final long time; | ||
private final String name; |
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.
Document the fields and maybe rename name
to vehicleId
or something that better describes it.
|
||
public class LidarData implements Serializable { | ||
@JsonAdapter(PolymorphismTypeAdapterFactory.class) | ||
private final Object lidarData; |
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.
Why is this an Object and why is it called lidarData
inside of the LidarData
-class? This adds unnecessary confusion.
Do we not have a class representing the point clouds instead of using a generic object?
…habmacs may be nice
Description
What is this PR about?
Related to
Affected parts of the online documentation
I believe no change in online documentation are required.
Definition of Done
Prerequisites
Required
type(scope): description
(in the style of Conventional Commits)enhancement
, orbugfix
)origin/main
has been merged into your Fork.Requested (can be enforced by maintainers)
Special notes to reviewer