Signal cutoff to improve retrieval for Raman method #317
Conversation
This file contains hidden or 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
|
Hi @yZenox , your "patch" has severe implication for all lidars. Also I think the statement that the first 10 bins are unphysical is not valid. THus, we need to disucss about it. Currently I would not like to merge it in dev. |
|
@ulysses78 @martin-rdz What do you think? I guess we cannot do it in such a hard coded way, right? Maybe to use the config file instead? E.g. starting with range bin 262 and then allocating height 41.25 m to it? |
|
Yes, those cutoffs definitly have to be added to the config file for the single polly-device, not in the python file itself. |
added 4 commits
October 6, 2025 09:59
…ut partial bins. "slope" parameter should be tested. This replaces the default "smooth" function. Behaviour should get tested besides the pollyFernald module.
… data. flag387OC/flag607OC is missing. Much repetetive copy-pasted code, which eventually should get replaced by loops.
…ut files. The run is splitted into calibrated and uncalibrated mode (=usage of mean lidar constants). The parameter should be put into config file. Run_picasso_test can probably be replaced by an extended picassoProcTodolist.
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.
The signal data in the first bins behaves unusual / non physical. This affects smoothing and differentiation for the Raman retrieval methods. So the first 10 bins are set equal to the value at the 10th bin. This is done for 532 and 1064nm. For 355nm this might be beneficial as well.