mirror of https://github.com/davisking/dlib.git
clarified spec
This commit is contained in:
parent
311075a74f
commit
94b0344532
|
@ -67,7 +67,7 @@ namespace dlib
|
|||
- Let M denote the dimensionality of the vectors output by Feature_extractor_type
|
||||
objects.
|
||||
- Let F(i) == the M dimensional vector which is the sum of all vectors
|
||||
given by our Feature_extractor_type object inside the ith feature extraction
|
||||
given by our Feature_extractor_type object inside the i-th feature extraction
|
||||
zone.
|
||||
- Then the feature vector for a sliding window is an M*N dimensional vector
|
||||
[F(1) F(2) F(3) ... F(N)] (i.e. it is a concatenation of the N vectors).
|
||||
|
@ -202,7 +202,7 @@ namespace dlib
|
|||
- The order of rectangles in stationary_feature_extraction_regions and
|
||||
movable_feature_extraction_regions matters. Recall that each rectangle
|
||||
gets its own set of features. So given two different templates, their
|
||||
ith rectangles will both share the same part of the weight vector (i.e. the w
|
||||
i-th rectangles will both share the same part of the weight vector (i.e. the w
|
||||
supplied to detect()). So there should be some reasonable correspondence
|
||||
between the rectangle ordering in different detection templates. For,
|
||||
example, different detection templates should place corresponding feature
|
||||
|
|
Loading…
Reference in New Issue