Develop TUM Yaw Loss model in V4 #800
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Wow, you guys are really packing a ton of new features into v4. Looking forward to incorporating all of this in my workflows! |
|
@paulf81 change this to draft (I think perhaps only the creator of the PR can do that)? And then, just to log, this PR will likely not be merged---a separate one will be opened with the TUM model when ready. However, we can leave this open in the mean time as a record. |
Done! |
|
Closing as superseded by #832 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Develop TUM Yaw Loss model in V4
This draft PR/branch is meant to collaboratively develop the TUM yaw loss model into the v4 framework.
The method is outlined here:
https://wes.copernicus.org/preprints/wes-2023-133/
Related issue
Issue #746