June 2014 - Olena-bugs

Re: [Olena-bugs] [Olena] #124: Ensure I/O operations on images holding greater-than-8-bit values are robust w.r.t. endianness
by Olena Trac 19 Jun '14

19 Jun '14

#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: Component: Milena | Version: 2.0 Resolution: | Keywords: -----------------------+------------------------ Changes (by levill_r): * version: 1.0 => 2.0 * milestone: Olena 2.1 => -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/124#comment:4> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 0

Re: [Olena-bugs] [Olena] #116: Move the definitions of the vset property higher in the image hierarchy
by Olena Trac 19 Jun '14

19 Jun '14

#116: Move the definitions of the vset property higher in the image hierarchy --------------------------+------------------------ Reporter: levill_r | Owner: Olena Team Type: enhancement | Status: closed Priority: minor | Milestone: Olena 2.1 Component: Milena | Version: 2.0 Resolution: invalid | Keywords: factor --------------------------+------------------------ Changes (by levill_r): * status: new => closed * version: 1.0 => 2.0 * resolution: => invalid Old description: > Milena is full of redundant definitions of `vset`, like this one: > > {{{ > #!cpp > typedef mln::value::set<value> vset; > }}} > > For instance, see > * source:trunk/milena/mln/core/image2d.hh > * source:trunk/milena/mln/core/internal/t_image.hh > > Factor them in higher super classes. > > {{{ > #!html > <br/> > }}} > > Likewise, factor definitions of method `values()`, in particular in > morphers : > {{{ > #!cpp > const vset& values() const; > }}} > {{{ > #!cpp > template <typename I> > const mln_vset(I)& > t_image<I>::values() const > { > mln_precondition(this->delegatee_() != 0); > return this->delegatee_()->values(); > } > }}} New description: Milena is full of redundant definitions of `vset`, like this one: {{{ #!cpp typedef mln::value::set<value> vset; }}} For instance, see * source:milena/mln/core/image/image2d.hh * source:milena/trash/t_image.hh Factor them in higher super classes. {{{ #!html <br/> }}} Likewise, factor definitions of method `values()`, in particular in morphers : {{{ #!cpp const vset& values() const; }}} {{{ #!cpp template <typename I> const mln_vset(I)& t_image<I>::values() const { mln_precondition(this->delegatee_() != 0); return this->delegatee_()->values(); } }}} -- Comment: This ticket seems irrelevant now, as `values_eligible_values()` seems to have replaced `values()`; closing. -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/116#comment:4> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 0

Re: [Olena-bugs] [Olena] #280: Get rid of trash directories
by Olena Trac 19 Jun '14

19 Jun '14

#280: Get rid of trash directories -----------------------+----------------------- Reporter: levill_r | Owner: levill_r Type: task | Status: assigned Priority: minor | Milestone: Olena 2.1 Component: Milena | Version: 2.0 Resolution: | Keywords: cleanup -----------------------+----------------------- Changes (by levill_r): * owner: Olena Team => levill_r * status: new => assigned Old description: > I.e.: > > * source:milena/doc/examples/trash > * source:milena/trash > > Rationale: if their content is not distributed, they should not be part > of `master`. We can style reintegrate them later from the repository's > history if needed. New description: I.e.: * source:milena/doc/examples/trash * source:milena/trash Rationale: if their content is not distributed, they should not be part of `master`. We can still (selectively) reintegrate them later from the repository's history if needed. Also: once these directories are removed, get rid of everything related to their contents (in scripts, documentation, etc.). -- -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/280#comment:1> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 0

Re: [Olena-bugs] [Olena] #105: Optimize with memory for border::duplicate
by Olena Trac 19 Jun '14

19 Jun '14

#105: Optimize with memory for border::duplicate --------------------------+------------------------ Reporter: duhamel | Owner: Olena Team Type: enhancement | Status: new Priority: minor | Milestone: Component: Milena | Version: 2.0 Resolution: | Keywords: --------------------------+------------------------ Changes (by levill_r): * version: 1.0 => 2.0 * type: task => enhancement * milestone: Olena 2.1 => Old description: > In source:trunk/milena/mln/border/duplicate.hh [[BR]] > > Handle memory traits in the enhancement of this algorithm. New description: In source:milena/mln/border/duplicate.hh [[BR]] Handle memory traits in the enhancement of this algorithm. -- Comment: This ticket's description is too vague. Which cases should be specialized? -- Ticket URL: <https://trac.lrde.org/olena/ticket/105#comment:2> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 0

Re: [Olena-bugs] [Olena] #103: mln/arith/revert.hh : move implementation in mln/fun/v2v/revert.hh
by Olena Trac 19 Jun '14

19 Jun '14

#103: mln/arith/revert.hh : move implementation in mln/fun/v2v/revert.hh --------------------------+------------------------ Reporter: duhamel | Owner: Olena Team Type: enhancement | Status: new Priority: minor | Milestone: Olena 2.2 Component: Milena | Version: 2.0 Resolution: | Keywords: --------------------------+------------------------ Changes (by levill_r): * version: 1.0 => 2.0 * milestone: Olena 2.1 => Olena 2.2 -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/103#comment:3> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 0

Re: [Olena-bugs] [Olena] #89: Add three levels of tests
by Olena Trac 19 Jun '14

19 Jun '14

#89: Add three levels of tests -----------------------+------------------------ Reporter: levill_r | Owner: Olena Team Type: proposal | Status: new Priority: minor | Milestone: Component: Milena | Version: 2.0 Resolution: | Keywords: -----------------------+------------------------ Changes (by levill_r): * version: 1.0 => 2.0 * type: enhancement => proposal * milestone: Olena 2.1 => Old description: > Level 0: Tests from source:trunk/milena/tests/core only.[[BR]] > Possible target names: > * `check-core` (current favorite) > * `check-unit` > > Level 1: All tests form source:trunk/milena/tests, except long > (comprehensive) tests.[[BR]] > Target name: > * check > > Level 2: All tests form source:trunk/milena/tests, including long > (comprehensive) tests.[[BR]] > Possible target names: > * `check-world` (one of the current favorite) > * `check-everything` > * `check-torture` > * `check-full` > * `check-long` > * `check-all` (one of the current favorite) > * `check-extra` > * `super-check` > * `check-more` > * `check-what-else` > * `check-hard(er)` > * `check-strong(er)` > > [[BR]] > > Note : a good 'torture test' is a file with > {{{ > #!cpp > #include <mln/all.hh> > }}} New description: Level 0: Tests from source:milena/tests/core only.[[BR]] Possible target names: * `check-core` (current favorite) * `check-unit` Level 1: All tests form source:milena/tests, except long (comprehensive) tests.[[BR]] Target name: * check Level 2: All tests form source:milena/tests, including long (comprehensive) tests.[[BR]] Possible target names: * `check-world` (one of the current favorite) * `check-everything` * `check-torture` * `check-full` * `check-long` * `check-all` (one of the current favorite) * `check-extra` * `super-check` * `check-more` * `check-what-else` * `check-hard(er)` * `check-strong(er)` [[BR]] Note : a good 'torture test' is a file with {{{ #!cpp #include <mln/all.hh> }}} -- -- Ticket URL: <https://trac.lrde.org/olena/ticket/89#comment:3> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 0

Re: [Olena-bugs] [Olena] #86: Simplify the creation and maintenance of Makefile.am's under milena/tests/
by Olena Trac 19 Jun '14

19 Jun '14

#86: Simplify the creation and maintenance of Makefile.am's under milena/tests/ --------------------------+----------------------- Reporter: levill_r | Owner: levill_r Type: enhancement | Status: closed Priority: minor | Milestone: Olena 2.1 Component: Milena | Version: 2.0 Resolution: fixed | Keywords: --------------------------+----------------------- Changes (by levill_r): * status: new => closed * version: 1.0 => 2.0 * resolution: => fixed Comment: Automake provides `AM_DEFAULT_SOURCE_EXT` since version 1.11 (see http://www.gnu.org/software/automake/manual/html_node/Default- _005fSOURCES.html). This feature has been used in Milena (since [245453d3]) and Scribo (since [12d0a854]) to simplify `Makefile`s. Closing. -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/86#comment:2> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 0

Re: [Olena-bugs] [Olena] #46: Snake forward works only on 2D
by Olena Trac 19 Jun '14

19 Jun '14

#46: Snake forward works only on 2D --------------------------+------------------------- Reporter: anonymous | Owner: Olena Team Type: enhancement | Status: new Priority: minor | Milestone: Component: Milena | Version: 2.0 Resolution: | Keywords: trait check --------------------------+------------------------- Changes (by levill_r): * version: 1.0 => 2.0 * milestone: Olena 2.1 => Old description: > source:trunk/milena/mln/canvas/browsing/snake_fwd.hh > > Now, snake-fwd works only on 2D, but it's not checked ! > > One could either check that the image is in 2D > or make the canvas generalized. New description: source:milena/mln/canvas/browsing/snake_fwd.hh Now, snake-fwd works only on 2D, but it's not checked ! One could either check that the image is in 2D or make the canvas generalized. -- -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/46#comment:1> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 0

Re: [Olena-bugs] [Olena] #45: Check if a point belong to an image during forward.
by Olena Trac 19 Jun '14

19 Jun '14

#45: Check if a point belong to an image during forward. ------------------------+------------------------ Reporter: anonymous | Owner: Olena Team Type: task | Status: closed Priority: minor | Milestone: Olena 2.1 Component: Milena | Version: 2.0 Resolution: wontfix | Keywords: has ------------------------+------------------------ Changes (by levill_r): * status: new => closed * version: 1.0 => 2.0 * resolution: => wontfix Old description: > source:trunk/milena/mln/canvas/browsing/ > > When we do a call of function of a functor, should we test if the point > belongs to the image ? New description: source:milena/mln/canvas/browsing/ When we do a call of function of a functor, should we test if the point belongs to the image ? -- Comment: This ticket's description is too vague; closing. -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/45#comment:2> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 0

Re: [Olena-bugs] [Olena] #36: Factor the implementation of literals with a singleton
by Olena Trac 19 Jun '14

19 Jun '14

#36: Factor the implementation of literals with a singleton --------------------------+------------------------ Reporter: theo | Owner: Olena Team Type: enhancement | Status: new Priority: trivial | Milestone: Component: Milena | Version: 2.0 Resolution: | Keywords: --------------------------+------------------------ Changes (by levill_r): * priority: minor => trivial * version: 1.0 => 2.0 * milestone: Olena 2.1 => Old description: > Add a generic singleton, and use it to factor the code in > source:trunk/milena/mln/literal. New description: Add a generic singleton, and use it to factor the code in source:milena/mln/literal. -- -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/36#comment:2> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 0