#292: Migrate Olena's Web site to the new (MediaWiki-based) Web server
----------------------+------------------------
Reporter: levill_r | Owner: Olena Team
Type: task | Status: new
Priority: major | Milestone: Olena 2.1
Component: Web | Version: 2.0
Keywords: |
----------------------+------------------------
This is a big task, that we should of course discuss and break into
smaller tasks.
Let's target the Olena 2.1 release.
--
Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/292>
Olena <http://olena.lrde.epita.fr>
Olena, a generic and efficient image processing platform
#146: Ensure the output value type is large enough in labeling algorithms
-----------------------+-------------------------------
Reporter: levill_r | Owner: levill_r
Type: defect | Status: new
Priority: major | Milestone: Olena 2.2
Component: Milena | Version: 1.0
Resolution: | Keywords: overflow labeling
-----------------------+-------------------------------
Changes (by levill_r):
* milestone: Olena 2.1 => Olena 2.2
Old description:
> Most labeling algorithm do not check that the output value is large
> enough to hold the whole set of labels. This is at least the case in
>
> * source:trunk/milena/mln/labeling/regional_minima.hh
> * source:trunk/milena/mln/labeling/regional_maxima.hh
> * source:trunk/milena/mln/morpho/watershed/flooding.hh (and its ancestor
> source:trunk/milena/mln/morpho/meyer_wst.hh)
>
> These algorithms should trigger an error if this happens, even if the
> output value type is not equipped to detect overflows.
>
> To do:
>
> 1. Write (small) test cases for each algorithm.
> 1. Choose a sound behavior (exceptions?).
> 1. Apply the required modifications.
New description:
Most labeling algorithm do not check that the output value is large enough
to hold the whole set of labels. This is at least the case in
* source:milena/mln/labeling/regional_minima.hh
* source:milena/mln/labeling/regional_maxima.hh
* source:milena/mln/morpho/watershed/flooding.hh
These algorithms should trigger an error if this happens, even if the
output value type is not equipped to detect overflows.
To do:
1. Write (small) test cases for each algorithm.
1. Choose a sound behavior (exceptions?).
1. Apply the required modifications.
--
Comment:
Update URLs.
--
Ticket URL: <https://trac.lrde.org/olena/ticket/146#comment:2>
Olena <http://olena.lrde.epita.fr>
Olena, a generic and efficient image processing platform
#106: Implement border::mirror for 3D images
----------------------+------------------------
Reporter: duhamel | Owner: Olena Team
Type: task | 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
Old description:
> In source:trunk/milena/mln/border/mirror.hh.
>
> Implement ~~1D and~~ 3D version for `border::mirror` algorithm.
>
> Note that the code for the 2D (and maybe 1D) version(s) could be
> factored.
New description:
Implement `mln::border::mirror` for 3D images (based on `mln::box3d`); see
source:milena/mln/border/mirror.hh.
--
--
Ticket URL: <https://trac.lrde.org/olena/ticket/106#comment:4>
Olena <http://olena.lrde.epita.fr>
Olena, a generic and efficient image processing platform