Improve map rendering #3
Conversation
|
A value of 1.0 causes a noticeable hit in performance. Perhaps the recommended value of 1.33 would be better as recommended in the issue you linked, as well as a related issue. |
|
@ckoval7 Aha, I have not noticed any regressions on my average Intel NUC, but perhaps lower power hardware might straggle a bit indeed. Perhaps a better idea is to add checkbox that toggles higher quality map rendering as I did in my latest commit? |
|
@ckoval7 I might forgot to mention, but when I force pushed I added the button I've mentioned. My bet, should not force push ever) Anyway, that's how it looks like: |
|
I am going to implement this a little differently. It'll be entirely in the browser, not having to touch the python side of things. |
|
Sure, I am not an expert in web development at all, just mimicked how other buttons were implemented) does not make sense to have a state for such thing on the server side. |
|
With a little extra leg work, it's possible to run offline maps w/ DFA. I just need a little help to make the process easier. Here's the current process, just replace PhotonMap w/ DFA. |
by making Cesium fetch higher resolution tiles more aggressively as suggested in CesiumGS/cesium#3279 (comment)
Instead keep the last know measurement and plot corresponding lob in gray color to alert operator. This change is suggested to be used together with krakenrf/krakensdr_doa#72 .
The description could be viewed in InfoBox for operator's convenience.
Also redraw map every 1s instead of 2.5s.
Which includes ADC overdrive, low SNR or signal correlation.
|
Hi! Will these changes be included in the main branch? I want to try them at work. |
by making Cesium fetch higher resolution tiles more aggressively as
suggested in CesiumGS/cesium#3279 (comment)