May 2014 - Olena-bugs

[Olena] #288: Pull Request: exp/magick-improvements
by Olena Trac 01 Jul '14

01 Jul '14

#288: Pull Request: exp/magick-improvements --------------------------+----------------------- Reporter: levill_r | Owner: levill_r Type: pull-request | Status: new Priority: major | Milestone: Olena 2.1 Component: Milena | Version: 2.0 Keywords: i/o | --------------------------+----------------------- PR sent by Guillaume Lazzara. This branch adds support for 16-bit value types with !GraphicsMagick as well as a new routine to read meta-data from an image file before loading the (whole) actual data. Be careful, these changes have not been tested on OS X (with !GraphicsMagick or !ImageMagick from the !MacPorts). -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/288> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 1

[Olena] #296: Adress recent GCC warnings regarding unused local typedefs
by Olena Trac 27 Jun '14

27 Jun '14

#296: Adress recent GCC warnings regarding unused local typedefs ----------------------+------------------------ Reporter: levill_r | Owner: Olena Team Type: defect | Status: new Priority: major | Milestone: Olena 2.1 Component: Milena | Version: 2.0 Keywords: | ----------------------+------------------------ GCC's `-Wunused-local-typedefs` option (which seems to be hooked to `-Wall` since version 4.8) triggers a lot of messages regarding Milena's code (and probably Scribo's as well). Some cases are easy to solve (typedefs actually used nowhere), while others are more delicate to handle, as `typedef` is used as a concept checking mechanism within Milena's concept classes. See how other projects doing concept checking with typedefs handled this issue. I guess we may be able to leverage GCC attributes to solve this. -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/296> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 3

[Olena] #287: Pull Request: xml2doc-fix-template-path
by Olena Trac 24 Jun '14

24 Jun '14

#287: Pull Request: xml2doc-fix-template-path --------------------------+----------------------- Reporter: levill_r | Owner: levill_r Type: pull-request | Status: new Priority: major | Milestone: Olena 2.1 Component: Scribo | Version: 2.0 Keywords: | --------------------------+----------------------- PR sent by Guillaume Lazzara. This branch solves a path-related issue regarding data used in XML-to- PDF/HTML conversions. -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/287> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 2

[Olena] #297: Stop using mln_VAR in installed libraries
by Olena Trac 19 Jun '14

19 Jun '14

#297: Stop using mln_VAR in installed libraries -------------------------+------------------------ Reporter: levill_r | Owner: Olena Team Type: defect | Status: new Priority: major | Milestone: Olena 2.1 Component: Milena | Version: 2.0 Keywords: portability | -------------------------+------------------------ The `mln_VAR` macro defined in source:milena/mln/core/var.hh relies on the non-standard `typeof` keyword. It should only be used in client code, not in library code. Ensure installed headers do not make use of this feature. -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/297> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 1

[Olena] #290: Check Olena with Cppcheck
by Olena Trac 17 Jun '14

17 Jun '14

#290: Check Olena with Cppcheck ----------------------+------------------------ Reporter: levill_r | Owner: Olena Team Type: task | Status: new Priority: major | Milestone: Olena 2.1 Component: Olena | Version: 2.0 Keywords: | ----------------------+------------------------ Check the whole code base with Cppcheck (http://cppcheck.sourceforge.net/) and use the report(s) produced by this tool to make changes to the code if they are deemed relevant. -- Ticket URL: <https://trac.lrde.org/olena/ticket/290> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 1

[Olena] #292: Migrate Olena's Web site to the new (MediaWiki-based) Web server
by Olena Trac 17 Jun '14

17 Jun '14

#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

2 6

Re: [Olena-bugs] [Olena] #126: Speed up tests
by Olena Trac 22 May '14

22 May '14

#126: Speed up tests -----------------------+------------------------ Reporter: levill_r | Owner: Olena Team Type: task | Status: new Priority: major | Milestone: Olena 2.1 Component: Milena | Version: 2.0 Resolution: | Keywords: -----------------------+------------------------ Changes (by levill_r): * version: 1.0 => 2.0 * type: enhancement => task -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/126#comment:4> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 0

Re: [Olena-bugs] [Olena] #151: Comparison operators (equality) on (concrete) windows and neighborhoods
by Olena Trac 22 May '14

22 May '14

#151: Comparison operators (equality) on (concrete) windows and neighborhoods -----------------------+------------------------ Reporter: levill_r | 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/151#comment:2> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 0

Re: [Olena-bugs] [Olena] #150: Deducing/computing the « complementary » neighborhood
by Olena Trac 22 May '14

22 May '14

#150: Deducing/computing the « complementary » neighborhood -----------------------+-------------------------- Reporter: levill_r | Owner: Olena Team Type: proposal | Status: new Priority: minor | Milestone: Component: Milena | Version: 2.0 Resolution: | Keywords: connectivity -----------------------+-------------------------- Changes (by levill_r): * priority: major => minor * version: 1.0 => 2.0 * type: task => proposal * milestone: Olena 2.1 => -- Ticket URL: <https://trac.lrde.org/olena/ticket/150#comment:2> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 0

Re: [Olena-bugs] [Olena] #146: Ensure the output value type is large enough in labeling algorithms
by Olena Trac 22 May '14

22 May '14

#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

1 0