/usr/include/visp/vpMomentDatabase.h is in libvisp-dev 2.8.0-4.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 | /****************************************************************************
*
* $Id: vpMomentDatabase.h 4056 2013-01-05 13:04:42Z fspindle $
*
* This file is part of the ViSP software.
* Copyright (C) 2005 - 2013 by INRIA. All rights reserved.
*
* This software is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License
* ("GPL") version 2 as published by the Free Software Foundation.
* See the file LICENSE.txt at the root directory of this source
* distribution for additional information about the GNU GPL.
*
* For using ViSP with software that can not be combined with the GNU
* GPL, please contact INRIA about acquiring a ViSP Professional
* Edition License.
*
* See http://www.irisa.fr/lagadic/visp/visp.html for more information.
*
* This software was developed at:
* INRIA Rennes - Bretagne Atlantique
* Campus Universitaire de Beaulieu
* 35042 Rennes Cedex
* France
* http://www.irisa.fr/lagadic
*
* If you have questions regarding the use of this file, please contact
* INRIA at visp@inria.fr
*
* This file is provided AS IS with NO WARRANTY OF ANY KIND, INCLUDING THE
* WARRANTY OF DESIGN, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
*
*
* Description:
* Pseudo-database used to handle dependencies between moments
*
* Authors:
* Filip Novotny
*
*****************************************************************************/
/*!
\file vpMomentDatabase.h
\brief Pseudo-database used to handle dependencies between moments.
*/
#ifndef __MOMENTDATABASE_H__
#define __MOMENTDATABASE_H__
#include <visp/vpImage.h>
#include <map>
#include <iostream>
#include <cstring>
class vpMoment;
class vpMomentObject;
/*!
\class vpMomentDatabase
\ingroup TrackingMoments
\brief This class allows to register all vpMoments so they can access each other according to their dependencies.
Sometimes, a moment needs to have access to other moment's values to be computed.
For example vpMomentCentered needs additionnal information about the gravity center vpMomentGravityCenter in order to compute the moment's value from a vpMomentObject.
This gravity center should be stored in a vpMomentDatabase where it can be accessed.
All moments in a database can access each other freely at any time. They can also verify if a moment is present in the database or not.
Here is a example of a dependency between two moments using a vpMomentDatabase:
\code
#include <visp/vpMomentObject.h>
#include <visp/vpPoint.h>
#include <visp/vpMomentGravityCenter.h>
#include <visp/vpMomentDatabase.h>
#include <visp/vpMomentCentered.h>
#include <iostream>
int main()
{
vpPoint p;
std::vector<vpPoint> vec_p; // vector that contains the vertices of the contour polygon
p.set_x(1); p.set_y(1); // coordinates in meters in the image plane (vertex 1)
vec_p.push_back(p);
p.set_x(2); p.set_y(2); // coordinates in meters in the image plane (vertex 2)
vec_p.push_back(p);
vpMomentObject obj(1); // Create an image moment object with 1 as
// maximum order (sufficient for gravity center)
obj.setType(vpMomentObject::DISCRETE); // The object is defined by
// two discrete points
obj.fromVector(vec_p); // Init the dense object with the polygon
vpMomentDatabase db;
vpMomentGravityCenter g; // declaration of gravity center
vpMomentCentered mc; // mc containts centered moments
g.linkTo(db); //add gravity center to database
mc.linkTo(db); //centered moments depend on gravity, add them to the
//database to grant access
db.updateAll(obj); // All of the moments must be updated, not just mc
//There is no global compute method since the order of compute calls
//depends on the implementation
g.compute(); // compute the moment
mc.compute(); //compute centered moments AFTER gravity center
std::cout << "Gravity center: " << g << std:: endl; // print gravity center moment
std::cout << "Centered moments: " << mc << std:: endl; // print centered moment
return 0;
}
\endcode
The following code outputs:
\code
Gravity center:
Xg=1.5, Yg=1.5
Centered moments:
2 0
0 x
\endcode
A moment is identified in the database by it's vpMoment::name method. Consequently, a database can contain at most one moment of each type.
Often it is useful to update all moments with the same object. Shortcuts (vpMomentDatabase::updateAll) are provided for that matter.
*/
class VISP_EXPORT vpMomentDatabase{
private:
#ifndef DOXYGEN_SHOULD_SKIP_THIS
struct cmp_str {
bool operator()(char const *a, char const *b) const{
return std::strcmp(a, b) < 0;
}
};
#endif
std::map<const char*,vpMoment*,cmp_str> moments;
void add(vpMoment& moment, const char* name);
public:
virtual ~vpMomentDatabase() {}
vpMoment& get(const char* type, bool& found);
/*!
Get the first element in the database.
May be useful in case an unnamed object is present but is the only element in the database.
\return the first element in the database.
*/
vpMoment& get_first(){return *(moments.begin()->second);}
virtual void updateAll(vpMomentObject& object);
friend VISP_EXPORT std::ostream & operator<<(std::ostream & os, const vpMomentDatabase& v);
friend class vpMoment;
};
#endif
|