Skip to content

Commit

Permalink
more text
Browse files Browse the repository at this point in the history
  • Loading branch information
cloude123 committed Apr 10, 2015
1 parent c13c4a4 commit 0c979b8
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions README.txt
Original file line number Diff line number Diff line change
Expand Up @@ -154,15 +154,15 @@ Basic usage:

7. The behaviour of other parameters are analyzed in [3].

8. Why does a function loadXXX for your data by written by yourself and called
in line 213 of run_pwrs_red.m?
8. Why does a function loadXXX for your data be written by yourself and called
in line 213 of run_pwrs_red.m instead of me providing it?
The problem is that the code does assume a certain frame numbering, by scene
and by frame within the scene. Also calibration matrices are required, which
must be provided by you. Furthermore the code needs to load
(if 3 frames are used) also the past frame of both cameras along.
When reasoning is done over multiple frames the code assumes that data from
the per segment solution of the previous frame
is available. To that end the scene-number and the frame-number is used,
thus these must be provided by you. You can use the function loadKittiFlow.m
the per-segment solution of the previous frame is available.
To that end the scene-number and the frame-number is used,
thus these must be provided by you. You can use the function loadKittiFlow.m
in the folder io as a guideline to create your read procedure for your data.

0 comments on commit 0c979b8

Please sign in to comment.