Olena-patches October 2009

olena-patches@lrde.epita.fr

7 participants
111 discussions

[Olena] #208: Fix dependencies of the HTML documentation generation?

by Olena Trac

#208: Fix dependencies of the HTML documentation generation? ----------------------+----------------------------------------------------- Reporter: levill_r | Owner: Olena Team Type: defect | Status: new Priority: minor | Milestone: Olena 1.1 Component: Milena | Version: 1.0 Keywords: doc | ----------------------+----------------------------------------------------- The generation of the HTML documentation requires a file named `html.sty`, which is not provided by HeVeA, but by latex2html. Is that right? I thought we only had a dependency on the former, not the latter. -- Ticket URL: <https://trac.lrde.org/olena/ticket/208> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image processing library.

11 years, 5 months

[Olena] #219: Add \internal in the documentation of internal code

by Olena Trac

#219: Add \internal in the documentation of internal code ---------------------+------------------------------------------------------ Reporter: lazzara | Owner: Olena Team Type: defect | Status: new Priority: major | Milestone: Olena 1.1 Component: Milena | Version: 1.0 Keywords: | ---------------------+------------------------------------------------------ Currently, in order to not expose the internal code in the user documentation, everything in the internal and trait namespaces is ignored during the doc generation. The main issue is that inherited members are not shown in the documentation of the classes exposed to the user. The only way to ask Doxygen to show inherited members and not to show internal documentation is to add \internal in the documentation of internal code. -- Ticket URL: <https://trac.lrde.org/olena/ticket/219> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image processing library.

11 years, 5 months

[Olena] #172: Experiment SCOOP 1.5/2 with C++0x concepts

by Olena

#172: Experiment SCOOP 1.5/2 with C++0x concepts -------------------------+-------------------------------------------------- Reporter: levill_r | Owner: Olena Team Type: enhancement | Status: new Priority: trivial | Milestone: Olena 2.0 Component: Olena-NG | Version: 2.0 Keywords: | -------------------------+-------------------------------------------------- What I call SCOOP 1.5 is the paradigm currently used in Milena 1.0 (as of Nov. 2008), and SCOOP 2 the paradigm described in the MPOOL'08 paper (used in Olena-NG). -- Ticket URL: <https://trac.lrde.org/olena/ticket/172> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image processing library.

12 years, 9 months

[Olena] #210: Check ImageMagick save() routine

by Olena Trac

#210: Check ImageMagick save() routine ---------------------+------------------------------------------------------ Reporter: freling | Owner: freling Type: defect | Status: new Priority: minor | Milestone: Olena 1.1 Component: Milena | Version: 1.0 Keywords: io | ---------------------+------------------------------------------------------ The save() routine located in mln/io/magick/save.hh has a weird behavior. We have to do a strange affectation (IM_value = 256 - MLN_value) but we don't really know why. -- Ticket URL: <https://trac.lrde.org/olena/ticket/210> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image processing library.

13 years, 9 months

[Olena] #148: Missing files in the distribution of Olena 0.11

by Olena

#148: Missing files in the distribution of Olena 0.11 ------------------------+--------------------------------------------------- Reporter: levill_r | Owner: Olena Team Type: defect | Status: new Priority: trivial | Milestone: Olena 0.11.1 Component: Milena | Version: 0.11 Keywords: EXTRA_DIST | ------------------------+--------------------------------------------------- Reported by Théo, relaunching `bootstrap.sh` from a distributed tarball of Olena 0.11: {{{ este% ./bootstrap.sh sh: Can't open ./cleanup.sh sh: Can't open ./gen_filelists.sh }}} -- Ticket URL: <https://trac.lrde.org/olena/ticket/148> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image processing library.

13 years, 12 months

[Olena] #217: Nasty bug in mln::data::impl::in memcpy_ with g++ 4.2 on Debian GNU/Linux on IA-32

by Olena Trac

#217: Nasty bug in mln::data::impl::in memcpy_ with g++ 4.2 on Debian GNU/Linux on IA-32 ----------------------+----------------------------------------------------- Reporter: levill_r | Owner: Olena Team Type: defect | Status: new Priority: critical | Milestone: Olena 1.1 Component: Milena | Version: 1.0 Keywords: | ----------------------+----------------------------------------------------- Running the following test exhibits this issue: {{{ make -C milena/apps/graph-morpho CXX="ccache g++-4.2" checkTESTS=samples- image2d TESTS_ENVIRONMENT="valgrind" }}} This seems to be a bug (or a weird implementation-defined behavior) in Debian's `g++` 4.2 on IA-32, due to some strict-aliasing rule not respected in Milena's code. I added a `#warning` in `memcpy_.hh` in r4608. But the thing is, `g++` 4.2 is the main compiler in Debian GNU/Linux 5.0, which is used on most GCC-based Olena buildbots, meaning we won't get a successful build on these hosts until we circumvent this bug. That's bad. -- Ticket URL: <https://trac.lrde.org/olena/ticket/217> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image processing library.

13 years, 12 months

[Olena] #201: Use « olena » instead of « oln » as an identifier

by Olena Trac

#201: Use « olena » instead of « oln » as an identifier ----------------------+----------------------------------------------------- Reporter: levill_r | Owner: Olena Team Type: defect | Status: new Priority: major | Milestone: Component: Olena | Version: 1.0 Keywords: | ----------------------+----------------------------------------------------- We should no longer use « `oln` » ; « `olena` » is much more clearer. * The Subversion repository is called `oln`, because `olena` was already used (arg!); we should not do this mistake again: the future Git repository shall be named `olena`. * Likewise, Olena's build farm URL (https://buildfarm.lrde.org/buildfarm/oln/) should be renamed to `olena`. If you find some other places where the project is called `oln` instead of `olena`, please report them here. TIA. -- Ticket URL: <https://trac.lrde.org/olena/ticket/201> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image processing library.

13 years, 12 months

[Olena] #126: Speed up tests

by Olena

#126: Speed up tests -------------------------+-------------------------------------------------- Reporter: levill_r | Owner: Olena Team Type: enhancement | Status: new Priority: major | Milestone: Olena 1.0ß Component: Milena | Version: 1.0 Keywords: | -------------------------+-------------------------------------------------- Some tests take a very long time to execute. Main causes are: * input image(s) are too big [[BR]] => they should be reduced (sometimes, testing on `lena.pgm` is just too costly); * the default, non-optimized compilation settings (`-O0 -ggdb`) produces very inefficient code for certain algorithms [[BR]] => we should locally increase the level of optimization (e.g., `-O1` or `-O2`) for these tests, and '''document''' this in `Makefile.am` (explain why we made changes in `CXXFLAGS` for a given test). We might want to make a list of lengthy tests here before solving this ticket. -- Ticket URL: <https://trac.lrde.org/olena/ticket/126> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image library.

13 years, 12 months

[Olena] #214: Use Automake 1.11's AM_DEFAULT_SOURCE_EXT

by Olena Trac

#214: Use Automake 1.11's AM_DEFAULT_SOURCE_EXT -------------------------+-------------------------------------------------- Reporter: levill_r | Owner: Olena Team Type: enhancement | Status: new Priority: minor | Milestone: Component: Milena | Version: 1.0 Keywords: Make | -------------------------+-------------------------------------------------- Quoting the [http://www.mail-archive.com/automake@gnu.org/msg15022.html announce of Automake 1.11]: {{{ - The default source file extension (.c) can be overridden with AM_DEFAULT_SOURCE_EXT now. }}} Which allows us to replace {{{ bin_PROGRAMS = foo bar baz foo_SOURCES = foo.cc bar_SOURCES = bar.cc baz_SOURCES = baz.cc }}} with {{{ bin_PROGRAMS = foo bar baz AM_DEFAULT_SOURCE_EXT = .cc }}} (Of course, « `AM_DEFAULT_SOURCE_EXT = .cc` » should be factored in some `common.mk` file.) This just rocks if you consider the tons of `*_SOURCES` lines in the zillions of `tests/*/Makefile.am` files. On the downward side, this change requires Automake 1.11, which is not even in Debian unstable as of July 24, 2009. We might want to wait a little bit before requiring this version. -- Ticket URL: <https://trac.lrde.org/olena/ticket/214> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image processing library.

13 years, 12 months

[Olena] #207: Use Automake 1.11

by Olena Trac

#207: Use Automake 1.11 -------------------------+-------------------------------------------------- Reporter: levill_r | Owner: levill_r Type: enhancement | Status: new Priority: major | Milestone: Olena 1.1 Component: Olena | Version: 1.0 Keywords: | -------------------------+-------------------------------------------------- Automake 1.11 provides a better framework for tests: each test can generate a log file, and the test suite is a mere rule generating a summary log, depending on all these logs. The `check` rule is no longer based on a shell `for` loop, and `make` can truly honors its `-j` (parallel instances) option when testing. Of course, one need to be careful with side effects, notably files created by tests, as one test may overwrite the output(s) of another tests. Akim recommends that test `foo` writes its outputs to `foo.dir`. Moreover, this permits many improvements: * One can generate pretty-printed versions of the tests using, e.g., `rst2html` (if the log contains an RST output) on the logs. * One can have a `recheck` rule reruning only the failed tests, since the first line of the log records the outcome of the test (pass or fail). * Also, provided dependencies are well set, this can probably help one write rules to rerun only the needed tests when a change occurred in the source tree (but I don't know yet how to do this). -- Ticket URL: <https://trac.lrde.org/olena/ticket/207> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image processing library.

13 years, 12 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Olena-patches October 2009