Skip to content

Feature/issue 544, 577, 578, 255 Weather Conditions #582

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

Closed
wants to merge 9 commits into from
Closed

Conversation

m-pauly
Copy link

@m-pauly m-pauly commented Sep 21, 2021

Signed-off-by: Markus Waldmann markus.waldmann@stud.hs-kempten.de & Markus Pauly markus.pauly@stud.hs-kempten.de

Reference to a related issue in the repository

#544
#577
#578
#255

Description

Introduction of the use of continuous values instead of enums for several weather-values.
More Information: See description in the several Issues.

@0815-code 0815-code linked an issue Sep 21, 2021 that may be closed by this pull request
@thomassedlmayer thomassedlmayer changed the base branch from feature/sm/environment-conditions-update to master September 21, 2021 14:52
Copy link
Contributor

@caspar-ai caspar-ai left a comment

Choose a reason for hiding this comment

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

In general, I wonder if this PR is trying to tackle too much at once.

There are some uncontroversial additions within this PR, specifically the new data such as Wind, CloudState, and Sun. Perhaps it would be beneficial to split those into a separate PR which can get merged more easily into master and then create new PR which addresses the more controversial issue of how to extend what are currently single fields. In particular, that may require separate PRs to get merged into a 3.x and 4.x release stream if breaking changes are desirable in the long-term.

//
// \note Defines the cloud states according to OpenScenario 1.1
//
optional CloudState cloud_state = 10;
Copy link
Contributor

Choose a reason for hiding this comment

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

I would suggest CloudState should be a message which contains the current CloudState enum.

It isn't required now but is more robust to wanting to extend how cloud state is described in future. (if all the other fields in this structure had done that originally this PR probably wouldn't exist 🙂)

//
// \note Describes the wind speed and direction from OpenScenario 1.1
//
message Wind
Copy link
Contributor

Choose a reason for hiding this comment

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

This Wind message is never used anywhere, should there be an optional field referencing it above?

@caspar-ai
Copy link
Contributor

I should also say, I'm happy to help with making those changes and PRs, but I didn't want to step on anyone's toes, if it would be helpful though, let me know.

@jdsika
Copy link
Contributor

jdsika commented Oct 13, 2021

Is this planned to be done in 4.0? Maybe have a clean breaking change then extending strangely in order to align with OpenSCEANRIO 1.x and OpenLABEL? Is there already a decision here?

@caspar-ai
Copy link
Contributor

@jdsika I would agree with that suggestion. There are some completely new parts that I think we could safely and sensibly include in 3.x, but I would agree that it would make more sense to make a breaking change to do this "properly" for the existing fields in 4.0.

@jdsika
Copy link
Contributor

jdsika commented Oct 13, 2021

So I would leave out "XY Extended" and add the easy ones from OSC1.X. Is it "sun" e.g.? What is the status of the debate regarding "cloudState"?

Could you remove the ones we agree to propose for 3.X here, clean it up (there are some errors from deleting and adding the same messages -> rebase completely), create a draft with tag 4.0 from this one and add the others to a separate PR, please?

@jdsika jdsika added this to the V4.0.0 milestone Oct 13, 2021
@jdsika jdsika added the Concept An issue that is being detailed out through expert discussion and offline work label Oct 13, 2021
@jdsika
Copy link
Contributor

jdsika commented Oct 13, 2021

@kmeids do you think my proposal is agreeable? I think we should also have a quick look in the compatibility with the tag list from OpenLABEL Public Review here as well. The goal should be a harmonized feature set which is not necessaryly loss free transformable (not needed IMO) but compatible in a sense like "sun from the front of the car" is able to be derived from "sun angles and ego vehicle position".

@kmeids
Copy link

kmeids commented Oct 13, 2021

Hello everyone,
@jdsika we have already discussed this topic in the SM group and did an alignment with open scenario and open ontology.
Eventually we did come up with a proposal that @jruebsam is still working on finalizing it.
@m-pauly, we have a SM meeting this Friday at 9:00 I'll forward you the invitation and hopefully @jruebsam will also be available with his proposal to discuss.

Changed the sun to a StationaryObject
Update after meeting and new input given of the Sensor Group
message Precipitation
{
// The intensity of the precipitation (valid for all precipitation types). Unit [mm/h]. Range [0...inf[
// According to OpenScenario 1.1 and according to the context of ISO 2315
Copy link
Contributor

Choose a reason for hiding this comment

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

23150 ? Missing 0

//
AMBIENT_ILLUMINATION_LEVEL4 = 5;
CLOUD_STATE_SLIGHTLYCLOUDY = 5;
Copy link
Contributor

Choose a reason for hiding this comment

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

I think should be CLOUD_STATE_SLIGHTLY_CLOUDY

@ThomasNaderBMW
Copy link
Contributor

Waiting for 4.0 may make sense.
From content view I left some comments and also forwarded to colleagues that need such extensions.
Let's see what will come back, but I think it goes into the right direction!

@stmswald
Copy link

We will now create two new PR. One for the Issue #544 with wind, sun and cloud state with tag V3.4.0. And one PR for #577 and #578 with tag for V4.0.0 with no more enum values for the fog, precipitation and illumination.

@jdsika
Copy link
Contributor

jdsika commented Oct 20, 2021

We will now create two new PR. One for the Issue #544 with wind, sun and cloud state with tag V3.4.0. And one PR for #577 and #578 with tag for V4.0.0 with no more enum values for the fog, precipitation and illumination.

I recommend to leave the ENUMS in the v4.0.0 and add a DEPRICATED comment above. I think it is better to evaluate with user behavior if the new description is accepted. The only important point is a note that both fields should be set and you need a transformation rule. But I think this is easily done.

@jdsika
Copy link
Contributor

jdsika commented Oct 20, 2021

@kmeids feel free to hand out my email for someone to discuss this in depth as I am not available on Fridays (part time currently).

@stmswald
Copy link

We will now create two new PR. One for the Issue #544 with wind, sun and cloud state with tag V3.4.0. And one PR for #577 and #578 with tag for V4.0.0 with no more enum values for the fog, precipitation and illumination.

I recommend to leave the ENUMS in the v4.0.0 and add a DEPRICATED comment above. I think it is better to evaluate with user behavior if the new description is accepted. The only important point is a note that both fields should be set and you need a transformation rule. But I think this is easily done.

Sure, for the first draft for V4.0.0. we can add the idea of @jruebsam from issue #255:

precipitation.label -> Enum
precipitation.state -> Double

and keep the idea of enums and double values?

@stmswald
Copy link

@thomassedlmayer this PR can be closed and not merged. The new PR for V3.4.0 is now PR #593. The PR for V4.0.0 will follow in within the next week

@m-pauly m-pauly closed this Oct 20, 2021
@m-pauly
Copy link
Author

m-pauly commented Oct 20, 2021

@stmswald PR should be closed now.

@PhRosenberger PhRosenberger self-assigned this Mar 1, 2023
@PhRosenberger PhRosenberger changed the title Feature/issue 544, 577, 578 Weather Conditions Feature/issue 544, 577, 578, 255 Weather Conditions Mar 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Concept An issue that is being detailed out through expert discussion and offline work
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Environmental Conditions
7 participants