Difference between revisions of "HanProgressReportAugust08"
From Immersive Visualization Lab Wiki
(→TODO) |
|||
| Line 15: | Line 15: | ||
* measuring performance for each step | * measuring performance for each step | ||
- find bottlenecks | - find bottlenecks | ||
| − | |||
* prefetching next frames (check libc max filedes) | * prefetching next frames (check libc max filedes) | ||
- frame window: [x-5, x+20] | - frame window: [x-5, x+20] | ||
| Line 23: | Line 22: | ||
* limiting # of bricks loaded at each frame | * limiting # of bricks loaded at each frame | ||
* prefetching bricks? | * prefetching bricks? | ||
| + | |||
| + | === 12 Tues === | ||
| + | ---- | ||
| + | * we can control the quality of image rendered | ||
| + | ** parameterize voxel to pixel ratio | ||
| + | ** parameterize the total number of bricks loaded at each frame | ||
| + | * need more performance measurements... | ||
=== 10 Sun === | === 10 Sun === | ||
Revision as of 19:50, 12 August 2008
Contents |
Deadline
- Aug/11/2008
- new class restructuring
- Sep/22/2008
- deadline
TODO
- multi-volume support
* mesh generation - generating a mesh for multivolumes under one constraint - memory size
* rendering - multi-volume rendering
o new rendering algorithm: need to manage multi bricks overlaps with several bricks!
* time-series multivolume rendering - need to handle multi timesteps
- mipmapped video support
* measuring performance for each step
- find bottlenecks
* prefetching next frames (check libc max filedes)
- frame window: [x-5, x+20]
- open new frame files
- close old frame files
* point of interest (check paper again)
* limiting # of bricks loaded at each frame
* prefetching bricks?
12 Tues
- we can control the quality of image rendered
- parameterize voxel to pixel ratio
- parameterize the total number of bricks loaded at each frame
- need more performance measurements...
10 Sun
- reimplemented covise plugin with the new MipMapVideoLib
- tested on covise
- 30 fps when cached
- below 10 fps when first played
09 Sat
- tested with 750 frames
- 2M pixel screen
- horrible performance 3~5 fps without caching
- second run (with cache) achieves around 30~50 frames per second
08 Fri
- debugged the bug
- tested with 200 tornado data frames and it plays interactively
- nearest neighbor interpolation causes lots of aliasing especially on lines and edges
- no prefetching or asynchronous I/O was used
- trying to come up with an algorithm that limits the total number of bricks loaded at each frame
- heuristic. there can be a smarter algorithm than one in octreemizer..
- don't know how much this would impact the overall performance
- generating 600 frames
07 Thur
- refine and debug frame window
- debugging frame window..
- data isn't changing...
06 Weds
Done
- generated tornado tiff data sets
- implemented frame window - need test!!!!!
- opening next 10 frames
- closing previous 10 frames
- activating/deactivating BrickReaders
- grpof to find bottlenecks
- no bad calls, which means my system is IO bounded. =(
August/05/2008 (Tu)
- multi-volume support
* user interface - need to be able to manipulate one volume at a time * new class structures? like in virvo/multirend
- dynamic change in volume control UI
- hide/show according to volume selection
August/01/2008 (Fri)
Done
- finalized the interface between MipMapVideo library and GUI part
