---
milena/ChangeLog | 5 +++++
milena/doc/ref-guide.tex | 37 ++++++++++++++++++++++++-------------
2 files changed, 29 insertions(+), 13 deletions(-)
diff --git a/milena/ChangeLog b/milena/ChangeLog
index 31c5566..c18309f 100644
--- a/milena/ChangeLog
+++ b/milena/ChangeLog
@@ -1,5 +1,10 @@
2013-05-13 Guillaume Lazzara <z(a)lrde.epita.fr>
+ * doc/ref-guide.tex: Mention *_without_localization routines in
+ reference guide.
+
+2013-05-13 Guillaume Lazzara <z(a)lrde.epita.fr>
+
Document sub_image morpher.
* doc/examples-outputs.mk,
diff --git a/milena/doc/ref-guide.tex b/milena/doc/ref-guide.tex
index b26929a..86b9b05 100644
--- a/milena/doc/ref-guide.tex
+++ b/milena/doc/ref-guide.tex
@@ -1312,27 +1312,34 @@ logical::not\_inplace() & Point-wise "logical not" \\
First, create an image:
\doxycode[1]{fill-call-1}
-Memory has been allocated so data can be stored but site values
-have not been initialized yet. So we fill \var{imga} with the value 'a':
+Memory has been allocated so data can be stored but site values have
+not been initialized yet. So we fill \var{imga} with the value 'a':
\doxycode[2]{fill-call-1}
-The \code{fill()} algorithm is located in the sub-namespace "\namespace{mln::data}" since this
-algorithm deals with the site values.
+data::fill() always preserves the location of the values while filling
+an image with another. If location does not matter, see
+data::fill\_without\_localization.
-The full name of this routine is \code{mln::data::fill()}.
-To access to a particular algorithm, the proper file shall be included.
-The file names of algorithms strictly map their C++ name; so
+The \code{fill()} algorithm is located in the sub-namespace
+"\namespace{mln::data}" since this algorithm deals with the site
+values.
+
+The full name of this routine is \code{mln::data::fill()}. To access
+to a particular algorithm, the proper file shall be included. The
+file names of algorithms strictly map their C++ name; so
\namespace{mln::data::fill} is defined in the file \header{mln/data/fill.hh}.
%----------------
\subsection*{Note}
-Most algorithms in Olena are constructed following the classical scheme: "output
-algo(input)", where the input image is only read. However some few algorithms
-take an input image in order to modify it. To enforce this particular feature,
-the user shall explicitly state that the image is provided so that its data is
-modified "read/write". The algorithm call shall be \code{data::fill(ima.rw(),
-val)}. When forgetting the \code{rw()} call, it does not compile.
+Most algorithms in Olena are constructed following the classical
+scheme: "output algo(input)", where the input image is only
+read. However some few algorithms take an input image in order to
+modify it. To enforce this particular feature, the user shall
+explicitly state that the image is provided so that its data is
+modified "read/write". The algorithm call shall be
+\code{data::fill(ima.rw(), val)}. When forgetting the \code{rw()}
+call, it does not compile.
\doxycode[3]{fill-call-1}
@@ -1345,6 +1352,10 @@ data for the sites (5, 5) to (14, 14) (so it has 100 sites).
Output:
\doxyoutput{paste-call-1}
+data::paste() always preserves the location of the values while
+pasting an image into another. If location does not matter, see
+data::paste\_without\_localization.
+
%Before pasting, the couple of images looked like:
%FIXME : ajouter des zolies zimages.
--
1.7.2.5
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Olena, a generic and efficient image processing platform".
The branch exp/upscale has been updated
via 19441a466fb310216378df22991de802e2d93dc5 (commit)
from 9ab50d8e723ac787402dd898ecf3c33a02332bd5 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
No new revisions were added by this update.
-----------------------------------------------------------------------
Summary of changes:
milena/mln/upscaling/upscaling_bicubic_2x.hh | 25 +++++++++++++------------
1 files changed, 13 insertions(+), 12 deletions(-)
hooks/post-receive
--
Olena, a generic and efficient image processing platform
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Olena, a generic and efficient image processing platform".
The branch exp/TL has been updated
via 57e5da750504563b272d09e46958d139abbd66fe (commit)
via 605d7143a0a888c09b51519aae4cae138bdb0b91 (commit)
via 19441a466fb310216378df22991de802e2d93dc5 (commit)
via e7c6040cc2a05d4393803aea488c258558001297 (commit)
via 9ab50d8e723ac787402dd898ecf3c33a02332bd5 (commit)
from 8b003049116ad7ea9e544118feb81b82b576b029 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
57e5da7 milena/mln/binarization/tmms_hysteresis.hh: Temporary definition of tmms hysteresis.
605d714 Merge branch 'exp/upscale' into exp/TL
e7c6040 milena/mln/upscaling/upscaling_bicubic_2x.hh: Add function to upscale x2 with bicubic interpolation.
-----------------------------------------------------------------------
Summary of changes:
milena/mln/binarization/tmms_hysteresis.hh | 518 ++++++++++++++------------
milena/mln/upscaling/upscaling_bicubic_2x.hh | 149 ++++++++
2 files changed, 433 insertions(+), 234 deletions(-)
create mode 100644 milena/mln/upscaling/upscaling_bicubic_2x.hh
hooks/post-receive
--
Olena, a generic and efficient image processing platform
------------------ Début de Rapport SpamAssassin ---------------------
Ce message est probablement du SPAM (message non sollicité envoyé en
masse, publicité, escroquerie...).
Cette notice a été ajoutée par le système d'analyse "SpamAssassin" sur
votre serveur de courrier "goa.lrde.epita.fr", pour vous
aider à identifier ce type de messages.
Le système SpamAssassin ajoute un en-tête "X-Spam-Flag: YES" aux
messages qu'il considère comme étant probablement du Spam.
Vous pouvez si vous le souhaitez utiliser cette caractéristique
pour régler un filtre dans votre logiciel de lecture de courrier,
afin de détruire ou de classer à part ce type de message.
Si ce robot a classifié incorrectement un message qui vous était
destiné, ou pour toute question, veuillez contacter l'administrateur
du système par e-mail à the administrator of that system .
Voir http://spamassassin.apache.org/tag/ pour plus de détails (en anglais).
Détails de l'analyse du message: (15.8 points, 5.0 requis)
3.3 RCVD_IN_PBL RBL: Received via a relay in Spamhaus PBL
[81.148.233.229 listed in zen.spamhaus.org]
1.7 URIBL_BLACK Contains an URL listed in the URIBL blacklist
[URIs: googlejob-france.com]
1.7 URIBL_DBL_SPAM Contains an URL listed in the DBL blocklist
[URIs: googlejob-france.com]
1.6 URIBL_WS_SURBL Contains an URL listed in the WS SURBL blocklist
[URIs: googlejob-france.com]
3.5 BAYES_99 BODY: L'algorithme Bayésien a évalué la probabilité de spam
entre 99 et 100%
[score: 1.0000]
1.7 HELO_LH_HOME HELO_LH_HOME
0.0 HTML_MESSAGE BODY: HTML inclus dans le message
0.7 MIME_HTML_ONLY BODY: Le message possède uniquement des parties MIME
text/html
1.0 RDNS_DYNAMIC Delivered to internal network by host with
dynamic-looking rDNS
0.5 MISSING_MID Missing Message-Id: header
0.0 TO_EQ_FM_HTML_ONLY To == From and HTML only
-------------------- Fin de Rapport SpamAssassin ---------------------
Le message original n'étant pas au format text brut, il est peut-être
dangereux de l'ouvrir avec votre logiciel e-mail ; en particulier il
pourrait contenir un virus, ou confirmer à l'expéditeur que votre
adresse e-mail est active, et peut recevoir du spam. Si vous voulez
lire ce message, et n'êtes pas certain de la sécurité de votre logiciel
e-mail, il est plus prudent d'enregistrer ce message sur votre disque
dur, et de l'afficher ensuite avec un éditeur de texte.
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Olena, a generic and efficient image processing platform".
The branch exp/newdoc has been updated
discards c55a823794f4f0cfaebd3e53911be7e8216e98fb (commit)
discards 83bbddc126e6e94226cf51f60361baef1cfcdf0b (commit)
via 81f1b95ffa4a93800125ac751de2086893bf4f0d (commit)
via 0a09504ba4f2512f8c82cd73b954d97f859da57f (commit)
via 38c46783a22cddd8b99524d1979c48f33e4de6d7 (commit)
via 6850b80deff3dbc90abd13f8923f182a1ea201ac (commit)
via 75a0e90175493882bd06f42658528143b5788129 (commit)
This update added new revisions after undoing existing revisions. That is
to say, the old revision is not a strict subset of the new revision. This
situation occurs when you --force push a change and generate a repository
containing something like this:
* -- * -- B -- O -- O -- O (c55a823794f4f0cfaebd3e53911be7e8216e98fb)
\
N -- N -- N (81f1b95ffa4a93800125ac751de2086893bf4f0d)
When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
81f1b95 mln/core/routine/duplicate.hh: Document this routine.
0a09504 Small fixes in documentation.
38c4678 Improve documentation of several macros.
6850b80 Fix missing parts of mln::box interface in documentation.
75a0e90 mln/core/var.hh: Document mln_VAR().
-----------------------------------------------------------------------
Summary of changes:
milena/ChangeLog | 35 +++-
milena/doc/mln/core/alias/box1d.dox | 4 +-
milena/doc/mln/core/alias/box2d.dox | 4 +-
milena/doc/mln/core/alias/box2d_h.dox | 4 +-
milena/doc/mln/core/alias/box3d.dox | 4 +-
milena/doc/mln/core/image/morphers.dox | 9 +-
milena/mln/core/concept/iterator.hh | 17 ++-
milena/mln/core/macros.hh | 363 ++++++++++++++++++++------------
milena/mln/core/pixter1d.hh | 2 -
milena/mln/core/routine/duplicate.hh | 24 ++-
milena/mln/core/var.hh | 6 +-
milena/mln/data/transform.hh | 51 +++--
milena/mln/debug/trace.hh | 18 ++
milena/mln/io/pdf/load.hh | 12 +-
milena/mln/trait/value_.hh | 87 +++++++-
15 files changed, 442 insertions(+), 198 deletions(-)
hooks/post-receive
--
Olena, a generic and efficient image processing platform
---
milena/ChangeLog | 4 ++++
milena/mln/core/routine/duplicate.hh | 24 ++++++++++++++++--------
2 files changed, 20 insertions(+), 8 deletions(-)
diff --git a/milena/ChangeLog b/milena/ChangeLog
index d5b38b1..039f880 100644
--- a/milena/ChangeLog
+++ b/milena/ChangeLog
@@ -1,5 +1,9 @@
2013-04-30 Guillaume Lazzara <z(a)lrde.epita.fr>
+ * mln/core/routine/duplicate.hh: Document this routine.
+
+2013-04-30 Guillaume Lazzara <z(a)lrde.epita.fr>
+
Small fixes in documentation.
* doc/mln/core/image/morphers.dox: Add a reference to duplicate().
diff --git a/milena/mln/core/routine/duplicate.hh b/milena/mln/core/routine/duplicate.hh
index fb79569..fe814c5 100644
--- a/milena/mln/core/routine/duplicate.hh
+++ b/milena/mln/core/routine/duplicate.hh
@@ -1,4 +1,5 @@
-// Copyright (C) 2007, 2008, 2009 EPITA Research and Development Laboratory (LRDE)
+// Copyright (C) 2007, 2008, 2009, 2013 EPITA Research and Development
+// Laboratory (LRDE)
//
// This file is part of Olena.
//
@@ -38,13 +39,20 @@
namespace mln
{
- /// Duplicate the image \p model with the values of the image \p
- /// data.
- ///
- /// \param[in] model The image to be duplicated.
- /// \result The duplicate.
- ///
- /// \pre model.is_valid
+ /*!
+ \brief Duplicate the image \p model with the values of the image
+ \p data.
+
+ \param[in] model The image to be duplicated.
+ \result The duplicate.
+
+ This routine performs a deep copy (create new data) of an image.
+ It can be used to copy an image or to create a concrete image
+ (\ref modimageconcrete) from a morphed image (\ref
+ modimagemorpher).
+
+ \pre model.is_valid
+ */
template <typename I>
mln_concrete(I) duplicate(const Image<I>& model);
--
1.7.2.5