-
Notifications
You must be signed in to change notification settings - Fork 27
Implement HOGER homogenization #240
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
Changes from 17 commits
d4ec947
86f134a
77d2742
58a4fc5
ab05283
4cbed9c
7a602a0
a897da4
fca8ef6
062e3da
6efad2a
67625b4
c615348
98b0383
7a0ed96
f77aa04
a07a41e
acb1aa7
c5bf57d
b49345c
b09d7af
643d915
9cd058d
214f4ff
98a6656
4a539a3
a47122e
c47984e
4b28fab
597f5ca
c52e4bb
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. All of the examples here use a wind direction that is steadily ramping (with a very small amount of noise added). How difficult/feasible would it to be to move to a more "reasonable" wind direction signal (e.g., a Gaussian wind direction with a standard deviation of, say, 10 degrees and a non-zero mean to provide bias)? I think that could also help make the jump clearer. It could also be interesting to compare the northing calibration procedure before and after the jump is detected by HOGER; i.e., demonstrate that the northing calibration doesn't work well if there is a jump in the bias
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I can for sure change over the yaw from ramping to fixed. That's no problem. Running the calibration procedure twice could be instructive, but at the cost of a much longer notebook, since it generates a lot of text and plots, so I'd vote against that step |
Large diffs are not rendered by default.
Uh oh!
There was an error while loading. Please reload this page.