June 2009 - Olena-patches

[Olena] #148: Missing files in the distribution of Olena 0.11
by Olena 04 May '10

04 May '10

#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.

2 1

[Olena] #201: Use « olena » instead of « oln » as an identifier
by Olena Trac 03 May '10

03 May '10

#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.

1 1

[Olena] #126: Speed up tests
by Olena 03 May '10

03 May '10

#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.

2 3

[Olena] #207: Use Automake 1.11
by Olena Trac 03 May '10

03 May '10

#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.

1 2

[Olena] #129: Reintegrate oln.m4 (full or a part of it) into Olena 1.0
by Olena 07 Apr '10

07 Apr '10

#129: Reintegrate oln.m4 (full or a part of it) into Olena 1.0 -----------------------------------+---------------------------------------- Reporter: levill_r | Owner: levill_r Type: enhancement | Status: new Priority: minor | Milestone: Olena 1.0ß Component: Olena | Version: 1.0 Keywords: configure autoconf M4 | -----------------------------------+---------------------------------------- In Olena 0.11, `oln.m4` (which might be renamed to `olena.m4`) provided useful services to both the Olena package (search for libraries, set up flags for tests, etc.) and autoconfiscated packages using Olena, by providing a `--with-oln` (to be renamed to `--with-olena`) flag. We should reintegrate a part of these features, possibly in two M4 macro packages: * one for Olena, * one for Olena-based projects. -- Ticket URL: <https://trac.lrde.org/olena/ticket/129> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image library.

2 2

[Olena] #206: Add the sources of the images of the ISMM 2009 paper to the Olena repository
by Olena Trac 12 Nov '09

12 Nov '09

#206: Add the sources of the images of the ISMM 2009 paper to the Olena repository -----------------------------------+---------------------------------------- Reporter: levill_r | Owner: levill_r Type: enhancement | Status: new Priority: minor | Milestone: Olena 1.1 Component: other | Version: 1.0 Keywords: reproducible research | -----------------------------------+---------------------------------------- Most of the work is already done, since the repository of the ISMM 2009 paper contains the material to automatically generate the images (needs some clean up though). Once moved to the Olena repository, remove the generators from the ISMM 2009 repository and only keep the end products (and possibly add Make rules to automate the update (copy) of the images from the Olena repository). -- Ticket URL: <https://trac.lrde.org/olena/ticket/206> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image processing library.

1 1

[Olena] #173: Complete the graph fusion example started with Géraud Béguin
by Olena 12 Nov '09

12 Nov '09

#173: Complete the graph fusion example started with Géraud Béguin ----------------------+----------------------------------------------------- Reporter: levill_r | Owner: Olena Team Type: task | Status: new Priority: minor | Milestone: Component: other | Version: 1.0 Keywords: IGR | ----------------------+----------------------------------------------------- See: * source:branches/cleanup-2008/milena/sandbox/beguin/irm.cc * source:branches/cleanup-2008/milena/sandbox/beguin/fusion_graph.hh -- Ticket URL: <https://trac.lrde.org/olena/ticket/173> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image processing library.

2 1

[Olena] #132: Use gcov
by Olena 05 Aug '09

05 Aug '09

#132: Use gcov ----------------------+----------------------------------------------------- Reporter: levill_r | Owner: Olena Team Type: task | Status: new Priority: major | Milestone: Olena 1.0ß Component: Milena | Version: 1.0 Keywords: | ----------------------+----------------------------------------------------- 1. Use `gcov` to check which parts of Olena are actually covered (instantiated and checked) by the test suite. 1. Automate with make. 1. Optionally use the LTP GCOV Extension (`lcov`) : http://ltp.sourceforge.net/coverage/lcov.php -- Ticket URL: <https://trac.lrde.org/olena/ticket/132> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image library.

2 3

[Olena] #181: Improve the download page
by Olena 13 Jul '09

13 Jul '09

#181: Improve the download page ----------------------+----------------------------------------------------- Reporter: levill_r | Owner: Olena Team Type: proposal | Status: new Priority: minor | Milestone: Olena 1.0 Component: other | Version: 1.0 Keywords: | ----------------------+----------------------------------------------------- Some Web sites of software projects asks for some (non mandatory) information before proceeding to download. For instance, each download link from the [http://www.itksnap.org/ ITK-SNAP] project redirects to a page similar to this one : http://www.itksnap.org/download/snap/register.php?link=itksnap-1.6.0.1-2008… where the user is invited to give some information (name, company/organization, etc.). The next page offers the user the opportunity to subscribe to one or several of the project's mailing list(s), then starts the download. I (Roland) think this would useful to have something similar on the Olena download page. -- Ticket URL: <https://trac.lrde.org/olena/ticket/181> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image processing library.

2 2

[Olena] #124: Ensure I/O operations on images holding greater-than-8-bit values are robust w.r.t. endianness
by Olena 13 Jul '09

13 Jul '09

#124: Ensure I/O operations on images holding greater-than-8-bit values are robust w.r.t. endianness ----------------------+----------------------------------------------------- Reporter: levill_r | Owner: Olena Team Type: task | Status: new Priority: minor | Milestone: Olena 1.0ß Component: Milena | Version: 1.0 Keywords: | ----------------------+----------------------------------------------------- This might be difficult to check, since it's platform-dependant. At least, we should check this (with the build farm) on a host with an endianness different than IA-32's or Intel 64's (e.g., a SPARC station). According to http://en.wikipedia.org/wiki/Endianness, * Intel IA-32 (and probably Intel 64 and AMD 64) are little-endian; * Motorola 68k, Sun SPARC and IBM System/370 processors are little- endian; * PowerPC, ARM, DEC Alpha, MIPS, HP PA-RISC and Intel IA-64 processors are bi-endian. -- Ticket URL: <https://trac.lrde.org/olena/ticket/124> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image library.

2 3