Olena-bugs June 2014

olena-bugs@lrde.epita.fr

1 participants
68 discussions

Re: [Olena-bugs] [Olena] #235: Support GraphicsMagick++ and drop support for ImageMagick++

by Olena Trac

#235: Support GraphicsMagick++ and drop support for ImageMagick++ -----------------------+------------------------- Reporter: levill_r | Owner: Olena Team Type: proposal | Status: closed Priority: major | Milestone: Olena 2.1 Component: Milena | Version: 2.0 Resolution: wontfix | Keywords: io external -----------------------+------------------------- Changes (by levill_r): * status: new => closed * version: 1.0 => 2.0 * resolution: => wontfix -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/235#comment:3> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

10 years, 6 months

Re: [Olena-bugs] [Olena] #233: Implement reconstructions on sets (logic/binary values)

by Olena Trac

#233: Implement reconstructions on sets (logic/binary values) -----------------------+------------------------ Reporter: levill_r | Owner: Olena Team Type: defect | Status: new Priority: major | Milestone: Olena 2.1 Component: Milena | Version: 1.0 Resolution: | Keywords: -----------------------+------------------------ Description changed by levill_r: Old description: > The following routines: > > * `mln::morpho::reconstruction::by_dilation::union_find` > * `mln::morpho::reconstruction::by_erosion::union_find` > > are not implemented on sets (logic/binary values), and worse, they do not > warn the user of this fact (neither a compile- nor at run-time). New description: The following routines: * `mln::morpho::reconstruction::by_dilation::union_find` * `mln::morpho::reconstruction::by_erosion::union_find` are not implemented on sets (logic/binary values) and abort at run time. -- -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/233#comment:1> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

10 years, 6 months

Re: [Olena-bugs] [Olena] #230: Inplace arithmetic operators do not guaranty that the type of the target can hold the results

by Olena Trac

#230: Inplace arithmetic operators do not guaranty that the type of the target can hold the results ------------------------+------------------------ Reporter: jacquelet | Owner: Olena Team Type: defect | Status: new Priority: major | 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/230#comment:2> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

10 years, 6 months

Re: [Olena-bugs] [Olena] #184: Clean the bread-first thinning (skeleton) algorithm

by Olena Trac

#184: Clean the bread-first thinning (skeleton) algorithm --------------------------+---------------------- Reporter: levill_r | Owner: levill_r Type: enhancement | Status: new Priority: trivial | Milestone: Component: Milena | Version: 2.0 Resolution: | Keywords: --------------------------+---------------------- Changes (by levill_r): * priority: major => trivial * version: 1.0 => 2.0 * milestone: Olena 2.1 => Old description: > * Use `image_if` and operator `|` when it is compatible with > `complex_image` in source:trunk/milena/apps/statues/mesh_complex_skel.cc. > * Likewise in source:trunk/milena/mln/topo/detach.hh. > * Use a cell iterator (when available) in the implementation of > `mln::make::cell` (source:trunk/milena/mln/make/cell.hh); see also #162. > * Make `mln::topo::is_facet` (source:trunk/milena/mln/topo/is_facet.hh) > a method of `mln::complex_psite` (or even of `mln::topo::face`). > * Address various `FIXME`s in > source:trunk/milena/mln/topo/skeleton/breadth_first_thinning.hh. > > * Implement the other algorithm (''A1'') from couprie.08.pami to check > the simplicity of a cell in source:trunk/milena/mln/topo/is_simple_cell > (and factor). New description: * ~~Use `image_if` and operator `|` when it is compatible with `complex_image` in source:milena/apps/mesh-segm-skel/mesh-complex- skel.cc.~~ * Likewise in source:milena/mln/topo/detach_cell.hh. * Use a cell iterator (when available) in the implementation of `mln::make::cell` (source:milena/mln/make/cell.hh); see also #162. * Make `mln::topo::is_facet` (source:milena/mln/topo/is_facet.hh) a method of `mln::complex_psite` (or even of `mln::topo::face`). * ~~Address various `FIXME`s in source:milena/mln/topo/skeleton/breadth_first_thinning.hh.~~ * Implement the other algorithm (''A1'') from couprie.08.pami to check the simplicity of a cell in source:milena/mln/topo/is_simple_cell.hh (and factor). -- Comment: Update ticket's status and paths. -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/184#comment:4> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

10 years, 6 months

Re: [Olena-bugs] [Olena] #179: Float precision issues with epsilon

by Olena Trac

#179: Float precision issues with epsilon ----------------------+------------------------ Reporter: lazzara | Owner: Olena Team Type: defect | Status: new Priority: major | 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/179#comment:3> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

10 years, 6 months

Re: [Olena-bugs] [Olena] #177: Provide safe value types to represent sizes

by Olena Trac

#177: Provide safe value types to represent sizes -----------------------+--------------------------------------- Reporter: levill_r | Owner: Olena Team Type: proposal | Status: new Priority: major | Milestone: Olena 2.2 Component: Milena | Version: 2.0 Resolution: | Keywords: conversion cast promotion -----------------------+--------------------------------------- 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/177#comment:2> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

10 years, 6 months

Re: [Olena-bugs] [Olena] #168: Revamp mln::topo::internal::complex_data<D>

by Olena Trac

#168: Revamp mln::topo::internal::complex_data<D> --------------------------+---------------------- Reporter: levill_r | Owner: levill_r Type: enhancement | Status: new Priority: trivial | Milestone: Component: Milena | Version: 2.0 Resolution: | Keywords: cleanup --------------------------+---------------------- Changes (by levill_r): * priority: major => trivial * version: 1.0 => 2.0 * milestone: Olena 2.1 => Old description: > See source:branches/cleanup-2008/milena/mln/topo/complex.hh > > * Store only the indices ('''and the sign'''!) of adjacent faces in > `complex_data<D>`: we don't really need actual faces there, and it costs > a lot (memory, execution time, design complexity, etc.) > * Then (or concurrently) simplify the design: use an array of array > instead of an ad hoc type list. > * The '''dynamic''' access(es) to the set of ''n''-faces of a complex > (e.g., `mln::complex::nfaces(unsigned)`) has (have) a linear complexity! > We should get rid of that. We could create an index at the creation of > the complex, mapping dynamic dimension numbers to the corresponding > (static) mixin/data. New description: See source:milena/mln/topo/complex.hh * Store only the indices ('''and the sign'''!) of adjacent faces in `complex_data<D>`: we don't really need actual faces there, and it costs a lot (memory, execution time, design complexity, etc.) * Then (or concurrently) simplify the design: use an array of array instead of an ad hoc type list. * The '''dynamic''' access(es) to the set of ''n''-faces of a complex (e.g., `mln::complex::nfaces(unsigned)`) has (have) a linear complexity! We should get rid of that. We could create an index at the creation of the complex, mapping dynamic dimension numbers to the corresponding (static) mixin/data. -- -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/168#comment:3> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

10 years, 6 months

Re: [Olena-bugs] [Olena] #167: Write (more) iterators on complexes

by Olena Trac

#167: Write (more) iterators on complexes -----------------------+---------------------- Reporter: levill_r | Owner: levill_r Type: proposal | Status: new Priority: trivial | Milestone: Component: Milena | Version: 2.0 Resolution: | Keywords: -----------------------+---------------------- Changes (by levill_r): * priority: major => trivial * version: 1.0 => 2.0 * type: task => proposal * milestone: Olena 2.1 => Old description: > Most of this task is described in > [source:branches/cleanup-2008/milena/tests/topo/complex.cc > tests/topo/complex.cc]. (This should be turned into actual > documentation, BTW.) > > See also #162 for applications of these iterators in > windows/neighborhoods and images. > > (Task mostly done in r2444, r2456, r2471, r2486, r2487, r2488, r2493, > r2494, r2511, r2512, r2520, r2521, and r2625.) > > ~~Also, introduce a class factoring common parts of~~ > * ~~`mln::topo::internal::complex_set_iterator_base` and~~ > * ~~`mln::topo::internal::complex_relative_iterator_base`~~ > (done in r2647 and r2648). New description: Most of this task is described in source:milena/tests/topo/complex.cc. (This should be turned into actual documentation, BTW.) See also #162 for applications of these iterators in windows/neighborhoods and images. (Task mostly done in r2444, r2456, r2471, r2486, r2487, r2488, r2493, r2494, r2511, r2512, r2520, r2521, and r2625.) ~~Also, introduce a class factoring common parts of~~ * ~~`mln::topo::internal::complex_set_iterator_base` and~~ * ~~`mln::topo::internal::complex_relative_iterator_base`~~ (done in r2647 and r2648). -- -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/167#comment:7> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

10 years, 6 months

Re: [Olena-bugs] [Olena] #165: Separate sites sets from their psites?

by Olena Trac

#165: Separate sites sets from their psites? -----------------------+------------------------ Reporter: levill_r | Owner: Olena Team Type: proposal | Status: new Priority: minor | Milestone: Component: Milena | Version: 2.0 Resolution: | Keywords: -----------------------+------------------------ Changes (by levill_r): * priority: major => minor * version: 1.0 => 2.0 * milestone: Olena 2.1 => -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/165#comment:2> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

10 years, 6 months

Re: [Olena-bugs] [Olena] #161: Implement more complex psite iterators

by Olena Trac

#161: Implement more complex psite iterators -----------------------+---------------------- Reporter: levill_r | Owner: levill_r Type: proposal | Status: new Priority: trivial | Milestone: Component: Milena | Version: 2.0 Resolution: | Keywords: -----------------------+---------------------- Changes (by levill_r): * priority: major => trivial * version: 1.0 => 2.0 * type: task => proposal * milestone: Olena 2.1 => -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/161#comment:4> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

10 years, 6 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

Olena-bugs June 2014