David Dubois wrote:
>
>
> Bonjour,
>
>
>
> J’ai lu un rapport comme quoi FLLT (fast level line transform) était ou
> devrait être intégré à Milena. J’ai téléchargé le code source d’Olena
> 1.0 et je ne trouve rien qui ressemble à FLLT.
Bonjour,
Pour l'instant, une implémentation naïve, "relativement" lisible et
sans optimisation, est dispo dans un bac à sable :
http://www.google.com/codesearch/p?hl=fr#IGThQjJ7Cjg/milena/sandbox/garrigu…
Elle correspond à l'algo de Monasse et Guichard.
> Merci de bien vouloir m’indiquer si cet algorithme est bel et bien inclus.
On va en effet intégrer une FLLT dans la bibliothèque l'an prochain
(2011). Si ça vous intéresse avant -> mail privé.
> Cordialement,
>
>
>
> David Dubois
Cdlt,
TG
Bonjour,
J'ai lu un rapport comme quoi FLLT (fast level line transform) était ou devrait être intégré à Milena. J'ai téléchargé le code source d'Olena 1.0 et je ne trouve rien qui ressemble à FLLT.
Merci de bien vouloir m'indiquer si cet algorithme est bel et bien inclus.
Cordialement,
David Dubois
Il est peut etre interessant d'inscrire la bibliotheque olena sur ce
site qui regroupe plusieurs outils autour du traitement des images.
www.ComputerVisionOnline.com
Date: Sun, 8 Aug 2010 23:08:52 -0400
From: amin sarafraz <sarafraz(a)gmail.com>
Subject: [Imageworld] Computer Vision Online website
To: imageworld(a)diku.dk
Message-ID:
<AANLkTikLMoBh3WMPniDA_x3iJacCa=0NPtSDHt6SNSDY(a)mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Dear Imageworld, could you please distribute this email, thanks
-------------------------------------------------------------------------------------------------------
Computer Vision Online is your gateway to the computer vision world
If you are looking for:
- Source codes or softwares to resolve your computer vision problems
- Other groups who might work in your field of interest
- Datasets to test your algorithms
- Contributing to an online book about computer vision
go to www.ComputerVisionOnline.com
Also, if you want to promote your source code/ software/ hardware/ dataset
leave a message for us.
Regards
BuildBot has been producing snapshots for a while (long before we
switched from Subversion to Git), which were compiled from the main
development tree (SVN's trunk at the time), and uploaded here:
http://www.lrde.epita.fr/dload/olena/snapshots/
However, now that we use Git, it seemed pointless to keep the same
mechanism: each commit in /any/ branch ending in a successful build
would produce a tarball overwriting the previous snapshot, whatever
branch were used in the production of the later.
So I adjusted the lrde-build.sh script used by BuildBot to
1. Filter the branches producing a snapshot after a build successfully
completed. Currently, these branches are `master', `next' and
`swilena'. Ask me if you want to add more branches to this set.
2. Have snapshot be stored in a subdirectory of the previous URL, e.g.
http://www.lrde.epita.fr/dload/olena/snapshots/next/http://www.lrde.epita.fr/dload/olena/snapshots/swilena/
...
This way BuildBot won't overwrite a snapshot with changes on Scribo
with, e.g., a snapshot with changes changes on Swilena.
The generated documentation is also stored in the subdirectory, as
usual.
The names used for the tarballs are a bit lengthy, but this removes any
ambiguity as for their content IMHO.
I now automatically generate some stats from the Olena repository using
GitStats [1] (not to be confused with GitStat) every night. They are
published here:
http://www.lrde.epita.fr/~levill_r/olena/stats/
Currently, only the `master', `next' and `prcs-olena' branches are
tracked.
These stats are also accessible from the side bar and from the
development page [2] of the project's Web site.
Notes:
[1] http://gitstats.sourceforge.net/
[2] http://olena.lrde.epita.fr/Development
Olena's BuildBot is up and running since April 8, 2010.
Yesterday we had our first successful automated builds in months since
the migration to Git! Two of the build slaves successfully went through
configuration, compilation, tests and distchecking for branch `next':
https://buildfarm.lrde.org/buildfarm/oln/waterfall?branch=next&reload=none
* i486-linux-gnu-gcc-4.1
* i486-linux-gnu-icc-11.0
The other builds have failed for various reasons:
1. powerpc-apple-darwin8-gcc-4.0.1: Host is offline.
2. i486-linux-gnu-gcc-3.3: Compilation failure (to be addressed).
3. i486-linux-gnu-gcc-4.2: Known weird behavior/bug of g++ 4.2.
4. i486-linux-gnu-icc-10.1: Compiler suddenly no longer working (weird).
5. x86-64-linux-gnu-gcc-4.1: Build host in bad condition.
Cases #1 and #5 are hardware issues. Problem #2 needs some examination.
I know how to work around issue #3. Case #4 is weird: previous builds
of `next' never exhibited such a compiler issue.
I'll try to fix #2 then #3. And I'll try to diagnose #4. We need to
work on #1 and #5 with Geoffroy.
Please do not send patches into `next' until we have fixed all builds.
TIA.
I think we also need to set up more build hosts. For instance, I'd like
to have builds
* using g++ 4.4 on GNU/Linux
* using g++ 4.3 on GNU/Linux
* on Cygwin (either using g++ 3.4 or g++ 4.x)
* possibly with MinGW
* possibly using gcc-snapshot (the future g++ 4.5)
* possibly on Mac OS X 10.5 or 10.6
Hi there,
I'm trying to install swilena, however I'm facing many problems...
After ./configure --enable-swilena... everything seems to be ok.. No
dependencies problem (Configure result attached)
But during Make... I've got many errors like this one:
----
if -Wall -c++ -python -I../../../milena -MD -MF ".deps/config-wrap.Tcc" -o
config-wrap.cc ../../../swilena/config.i; then \
mv -f ".deps/config-wrap.Tcc" ".deps/config-wrap.Pcc";\
else \
rm -f ".deps/config-wrap.Tcc"; exit 1;\
fi
---
That error I've mentioned before is related to SWIG field. For some reason,
the SWIG and many other fields were blank.
After reading the Makefile (/opt/olena-1.0/build/swilena/python/Makefile),
I've noticed that It failed to fill some configuration commands... most of
them related to python..
I have to fill those blanks by myself:
SWIG = swig
pyexecdir = /opt/olena-1.0/build/swilena/python/
pythondir = /usr/local/lib/python2.6/
PYTHON = /usr/lib/python2.6/
PYTHONINC = /usr/include/python2.6
After that, I thought the installation was about to finish successfully, but
I got this error after "make install":
test -z "/usr/local/lib/python2.6/" || /bin/mkdir -p
"/usr/local/lib/python2.6/"
/usr/bin/install -c -m 644 config.py point2d.py dpoint2d.py box2d.py
box2d_piter.py int_u8.py int_u32.py neighb2d.py window2d.py image2d_int.py
image2d_int_u8.py dynamic_image2d.py '/usr/local/lib/python2.6/'
../../../build-aux/py-compile: 119: /usr/lib/python2.6/: Permission
denied
make[3]: ** [install-nodist_pythonPYTHON] Erro
126
make[3]: Saindo do diretório
`/opt/olena-1.0/build/swilena/python'
make[2]: ** [install-am] Erro
2
make[2]: Saindo do diretório
`/opt/olena-1.0/build/swilena/python'
make[1]: ** [install-recursive] Erro
1
make[1]: Saindo do diretório
`/opt/olena-1.0/build/swilena'
make: ** [install-recursive] Erro 1
Yes. I'm root :-) I don't know what is the cause of this permission denied
Still, I changed to /opt/olena-1.0/swilena/python and tried to run what swig
has created...
but...
samuel@beaver:/opt/olena-1.0/swilena/python$ python swilena.py
Traceback (most recent call last):
File "swilena.py", line 24, in <module>
import config
File "/usr/lib/python2.6/ihooks.py", line 406, in import_module
q, tail = self.find_head_package(parent, str(name))
File "/usr/lib/python2.6/ihooks.py", line 449, in find_head_package
raise ImportError, "No module named " + qname
ImportError: No module named config
I checked the generated files and there is no config.py available..
I guess there is something missing in the Makefile... not sure...
Anyone can help me out?
merci,
--
Samuel Félix
Computer Science M.Sc. Candidate at Federal University of Minas Gerais
Computer Science B.Sc. at Federal University of Pará
Hi Pierre,
PierreL wrote:
> I don't see scribo in the tar packages http://www.lrde.epita.fr/cgi-bin/twiki/view/Olena/Olena100
>
> Is this a mistake?
Actually, this is not. We would like Scribo to be an optional module and
be available in a distinct tarball.
One of the reasons is that we may want to release new versions of Scribo
independently from Olena.
> Where should I get scribo?
Currently, Scribo is not packaged yet but is available in the SVN
repository : https://svn.lrde.epita.fr/svn/oln/trunk/scribo
Regards,
Guillaume
The Olena Team is proud to announce the release of Olena 1.0.
Olena is a platform dedicated to image processing and pattern
recognition. Its core component is a generic and efficient C++
library called Milena. Milena provides a framework to implement
simple, fast, safe, reusable and extensible image processing tool
chains. The library provides many ready-to-use image data structures
(regular 1D, 2D, 3D images, graph-based images, etc.) and algorithms.
Milena's algorithms are built upon classical entities from the image
processing field (images, points/sites, domains, neighborhoods, etc.).
This design allows image processing developers and practitioners to
easily understand, modify, develop and extend new algorithms while
retaining the core traits of Milena: genericity and efficiency.
The package also features Swilena, an optional component exposing
Milena to other languages thanks to the Simplified Wrapper and
Interface Generator (SWIG). For the moment, only some Python bindings
are provided.
The Olena platform is Free Software. It is distributed under the
conditions of the GNU General Public License (GPL) version 2. See the
file COPYING shipped with the Olena distribution.
Release notes are available at:
http://olena.lrde.epita.fr/Olena100
You can download packages of the Olena 1.0 distribution here:
http://www.lrde.epita.fr/dload/olena/1.0/olena-1.0.tar.gz (25MB)
http://www.lrde.epita.fr/dload/olena/1.0/olena-1.0.tar.bz2 (21MB)
The SHA1 digests of theses packages are:
33fc3a327db3f4f68c882d3b2462b83841425628 olena-1.0.tar.gz
2c6ba36d4a156156f7d5ea8f2e1f02bbec9c9098 olena-1.0.tar.bz2
Here is a list of major changes since Olena 0.11:
* The core C++ library, renamed to Milena, has been rewritten from
scratch and features numerous additions over the past releases.
Some features have also been dropped or disabled, and some of them
will be reintegrated in future releases. The programming
interface has changed from previous versions, but most programs
using Olena 0.11 can be adapted to the Olena 1.0 API.
* Milena uses a simplified version of the SCOOP 2 paradigm
(informally called SCOOP 1.5), to improve the speed of compilation
and make developing easier while still providing very good
run-time performances.
* A first (re)implementation of Swilena featuring Python wrappers
for a very small subset of Milena is available. The bundled
Swilena Python Shell (sps) allows interactive Olena sessions.
* A reference documentation including a tutorial and a quick
reference guide have been started. They do not cover the whole
Milena library yet.
* Olena includes some demos and applications using Milena.
The file NEWS, included in the archive, contains a more complete list
of user-visible changes.
Please report any problem by mail to <olena-bugs(a)lrde.epita.fr>.
--
Roland Levillain - LRDE/EPITA - A3SI/ESIEE/IGM/UMLV-Paris Est
EPITA Research and Development Laboratory (LRDE)
14-16, rue Voltaire - FR-94276 Le Kremlin-Bicêtre Cedex - France
Phone: +33 1 53 14 59 45 - Fax: +33 1 53 14 59 22 - www.lrde.epita.fr
