-
Notifications
You must be signed in to change notification settings - Fork 131
Introducing emitting objects #472
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
Conversation
Tagging the related issue: Fixes #455 |
osi_object.proto
Outdated
// Distribution of the emitted electromagnetic wave's intensity based on the intensity_per_wavelength as | ||
// maximum value. | ||
// | ||
repeated IntensityDistribution emitted_intensity_distribution = 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.
Output from CCB 09.06.2021
- Since this message defines the "FoV" of the emitting object and not the actual distribution of each "ray" a better name should be suggested (including the word Spatial either in the message name or in the definition).
- A note to be added describing the fact the number of emitted_intensity_distribution should be equal to the number of samples defined in the WavelengthData.
osi_object.proto
Outdated
// | ||
// Unit: W/m^2 | ||
// | ||
// \note max_intensity_per_wavelength.size() = WavelengthData.samples_number.size() |
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.
Output from CCB 09.06.2021
A none "equation" based definition to be added describing the fact the number of max_intensity_per_wavelength should be equal to the number of samples defined in the WavelengthData.
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.
Please check comments and suggestions.
osi_object.proto
Outdated
// | ||
message EmittingStructureAttribute | ||
{ | ||
// This message determines the range of the wavelength and its |
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.
Add relationship to normal, i.e. angle is symmetrical across the normal, which is defined by the mounting position...
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.
Looking good to me.
osi_object.proto
Outdated
// \brief Definition of a spatial intensity distribution with a horizontal and a vertical angle | ||
// and the corresponding intensity related to a maximum intensity. | ||
// | ||
message SpatialIntensity |
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.
@LukasElster
Please move the message SpatialIntensity
to osi_common.proto.
It is rather generic and will be used in the SETLevel project e.g. in the LidarSensorViewConfiguration to describe the lidar signal emission there (will be used e.g. for ray tracer config).
Moving it now will avoid the effort to move it later ;-)
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.
Actually, @ClemensLinnhoff and I discussed this today and we strongly believe that a signal strength in dBm would fit best here (intensity is rather a power distribution in watts per square metre (W/m2)).
We expect that using a logarithmic unit will be better for high difference btw. emision and reception compared to simple %.
It would mean to get rid of the maximum intensity as well, which is on the pro-side, as well, I guess.
Therefore, we recommend the following for osi_common:
//
// \brief Definition of a spatial signal strength distribution
// for an emitting / transmitting / receiving entity
// with a horizontal and a vertical angle
// and the corresponding signal strength in dBm (decibels per milliwatt).
//
message SpatialSignalStrength
{
// Horizontal angle (azimuth) of emission / transmission / reception
// in the entity's coordinate system.
//
// Unit: rad
//
optional double horizontal_angle = 1;
// Vertical angle (elevation) of emission / transmission / reception
// in the entity's coordinate system.
//
// Unit: rad
//
optional double vertical_angle = 2;
// Emitted / transmitted /received signal strength
// of the emitting / transmitting / receiving entity
// at the previously defined horizontal and
// vertical angle for one specific wavelength.
// The value for the signal strength
// is given in dBm (decibels per milliwatt).
//
// Unit: dBm
//
optional double signal_strength = 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.
@PhRosenberger I integrated your recommendations
CCB Output 21.07.2021
|
Signed-off-by: @lukas.elster <[email protected]>
Signed-off-by: @lukas.elster <[email protected]>
…n in the SensorModeling Bi-Weekly on 05.02.21. Signed-off-by: @lukas.elster <[email protected]>
… e.g. radar antenna pattern and changed osi_object.proto accordingly. Signed-off-by: @lukas.elster <[email protected]>
Signed-off-by: @lukas.elster <[email protected]>
…cify emitting objects. Signed-off-by: @lukas.elster <[email protected]>
Signed-off-by: @lukas.elster <[email protected]>
Signed-off-by: @lukas.elster <[email protected]>
…ntensity based on the recommendations of Philipp Rosenberger Signed-off-by: @lukas.elster <[email protected]>
1d9e91c
to
75e73ea
Compare
Branch rebased to master with @kmeids @LukasElster. |
Reference to a related issue in the repository
#455
Add a description
As street lights and other emitting structures of electromagnetic waves is not part of the actual definition of stationary object this PR introduces it.
Mention a member
Result of the discussion with @PhRosenberger and @kmeids
Check the checklist