Custom Query (432 matches)
Results (85 - 87 of 432)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#119 | fixed | Difference between Azspec and Caligeo processed Hawk data | benj | benj |
Description |
Split off from ticket #113. Hawk data processed with Azspec and Caligeo shows a gap between the two, particularly at the short-wave end of the spectrum. Over land the two are very close at the longer-wave end, over water Caligeo is consistently higher than Azspec (though the gap is larger at the short-wave end). Azspec data looks more plausible but Hawk needs calibrating to check which (if either) is correct. |
|||
#327 | fixed | distance and colour scales | emca | chrfi |
Description |
it would be good to add a scale for the distance on screen and the colour by height to lag. prefereably these would be in the main viewing window in one corner floating above the opengl drawn flight line. they need to be togglable and easy to read against the black background and most of the colours the flightlines can be. |
|||
#311 | fixed | drawing the flight lines increases main memory usage | emca | chrfi |
Description |
to reproduce load several flight lines that will not fit within the given cache. these will load normally with the ram usage being capped at the cache limit. when the image is first drawn the amount of ram being used by the program will increase. This increase seems to be linked to the size of the flight lines. subsequent redraws increase the ram usage slightly but i think this is the same problem being caused by drawing areas that were in cache the first time but now have to be loaded. once each part of the image has been drawn and loaded out of secondary memory once the increase stops. This at first seems to point to a problem in the caching code and therefore i have used my test bed to perform unit tests on the quadtree and caching classes. These tests showed that without the gui loading and then pulling points out of uncached buckets has no effect on the ram usage of the program. so far the only theory is that it is caused by an overflow from the graphics card ram. |