Closed evzayas closed 7 years ago
This is now fixed in the feature/LineFitting branch. I plan to merge this branch into develop at some point soon, so I will not do a hotfix.
Commit is here: dffef85
I will also close the issue once the merge to develop is done, presumably next week.
Branch is now merged into develop. Closing the issue
Currently these are the only two processors with a minimum and maximum frequency that can be determined/set by incoming data (i.e. a track), or by the configuration values
min(max)-frequency
. The former is implemented in a way such that it ignores the latter; for example, I might tell the spectrogram collector to set the minimum frequency 10 MHz below the track starting frequency, and simultaneously specify an overall minimum frequency of 50 MHz:If a track is received with starting frequency 55 MHz, the minimum frequency will be set to 45 MHz even though
min-frequency
has been specified above that. The logic with this should be changed to simply take the greater (lesser) of the two minima (maxima), so that neither bound is violated.