- Olena-bugs

[Olena] #298: Make Swilena work with SWIG 2.0.9+
by Olena Trac 19 May '14

19 May '14

#298: Make Swilena work with SWIG 2.0.9+ ----------------------+------------------------ Reporter: levill_r | Owner: Olena Team Type: defect | Status: new Priority: critical | Milestone: Olena 2.1 Component: Swilena | Version: 2.0 Keywords: | ----------------------+------------------------ The Swilena test suite fails when the wrappers are generated with a version of SWIG equal to or greater than 2.0.9. This problem has been observed with SWIG 2.0.9, 2.0.11 and 3.0.0. It works fine with SWIG 2.0.7 though. Try to compare the generated wrappers (C++ and Python files) in order to highlight the issue. -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/298> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 1

Re: [Olena-bugs] [Olena] #183: Have mln::complex_image be more flexible w.r.t. its domain
by Olena Trac 19 May '14

19 May '14

#183: Have mln::complex_image be more flexible w.r.t. its domain --------------------------+---------------------- Reporter: levill_r | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Milena | Version: 1.0 Resolution: | Keywords: site set --------------------------+---------------------- Changes (by levill_r): * owner: levill_r => * priority: critical => minor * milestone: Olena 2.1 => Old description: > `mln::complex_image` makes it mandatory us to assign values to ''each'' > face of a complex. But sometimes, we are only interested by a subset of > a complex (e.g., its edges). We should have the choice of the domain of > a `mln::complex_image`. > > Hint: see how Guillaume revamped the graph-based images, using functions > (i.e. domain + value -> image). I (Roland) still consider actual images > types are desirable, but we could implement them as wrappers of function- > based images. > > I have set the priority of this ticket to 2 (« critical ») because we > really need this feature for the examples of the ISMM'09 submission. New description: `mln::complex_image` makes it mandatory us to assign values to ''each'' face of a complex. But sometimes, we are only interested by a subset of a complex (e.g., its edges). We should have the choice of the domain of a `mln::complex_image`. Hint: see how Guillaume revamped the graph-based images, using functions (i.e. domain + value -> image). I (Roland) still consider actual images types are desirable, but we could implement them as wrappers of function- based images. -- -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/183#comment:2> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 0

Re: [Olena-bugs] [Olena] #157: Improve depency tracking in Swilena
by Olena Trac 19 May '14

19 May '14

#157: Improve depency tracking in Swilena --------------------------+----------------- Reporter: levill_r | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Swilena | Version: 1.0 Resolution: | Keywords: --------------------------+----------------- Changes (by levill_r): * owner: levill_r => * status: assigned => new * milestone: Olena 2.1 => Old description: > Our hand-made build system does not seem to track dependencies very well > in Swilena/Python. Improve this. New description: Our hand-made build system does not seem to track dependencies very well in Swilena/Python. Improve this. We whould exhibit a (small) instance of this problem first. -- -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/157#comment:3> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 0

Re: [Olena-bugs] [Olena] #260: Create Homebrew formula
by Olena Trac 19 May '14

19 May '14

#260: Create Homebrew formula --------------------------+----------------- Reporter: lazzara | Owner: Type: enhancement | Status: new Priority: trivial | Milestone: Component: Olena | Version: 1.0 Resolution: | Keywords: --------------------------+----------------- Changes (by levill_r): * owner: lazzara => * priority: minor => trivial * status: assigned => new * milestone: Olena 2.1 => -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/260#comment:2> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 0

Re: [Olena-bugs] [Olena] #248: Scribo-viewer does not warn if fop or xsltproc are missing
by Olena Trac 19 May '14

19 May '14

#248: Scribo-viewer does not warn if fop or xsltproc are missing --------------------------+----------------------- Reporter: lazzara | Owner: Type: enhancement | Status: new Priority: major | Milestone: Olena 2.1 Component: Scribo | Version: 2.0 Resolution: | Keywords: --------------------------+----------------------- Changes (by levill_r): * owner: lazzara => * status: assigned => new -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/248#comment:2> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 0

Re: [Olena-bugs] [Olena] #42: Add missing operators in mln/literal/ops.hh.
by Olena Trac 19 May '14

19 May '14

#42: Add missing operators in mln/literal/ops.hh. --------------------------+----------------------- Reporter: garrigues | Owner: Type: enhancement | Status: new Priority: major | Milestone: Olena 2.1 Component: Milena | Version: 1.0 Resolution: | Keywords: --------------------------+----------------------- Changes (by levill_r): * owner: lazzara => * status: assigned => new -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/42#comment:4> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 0

[Olena] #291: Improve the MinGW build on TeamCity
by Olena Trac 19 May '14

19 May '14

#291: Improve the MinGW build on TeamCity ------------------------------------+------------------------ Reporter: levill_r | Owner: Olena Team Type: enhancement | Status: new Priority: minor | Milestone: Component: Olena | Version: 2.0 Keywords: continuous integration | ------------------------------------+------------------------ The current MinGW build running on the !TeamCity server (http://teamcity.lrde.epita.fr/viewType.html?buildTypeId=bt11) is limited to the compilation of a subset of Olena: many features are disabled as we cannot run programs built by `i686-w64-mingw32-c++` or even link them with most of our external dependencies (such as !GraphicsMagick). Likewise, the rebuilding of the documentation is circumvented by `touch`-ing timestamps and output files generated by locally-built Milena programs. Could we use Wine (http://www.winehq.org/) to run binaries built by `i686-w64-mingw32-c++`? Or run them on a Windows host (either an actual machine or a VM)? Here is a summary of things that could be improved: * Do not run programs in `milena/doc/` — or have them run in the host environment (Windows). This is currently circumvented by not passing `--enable-apps` to `configure`. * Do not use the `random()` function (used at least in `milena/apps/mesh- segm-skel/`) as MinGW does not provide it. * Enable support for !GraphicsMagick (or !ImageMagick) and Qt. * Enable the `make check` and `make distcheck` TeamCity build steps. * More generally, be able to pass `--enable-all` to `configure`. -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/291> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 2

[Olena] #285: Overhaul the Olena configurations on TeamCity
by Olena Trac 14 May '14

14 May '14

#285: Overhaul the Olena configurations on TeamCity -------------------------+---------------------- Reporter: levill_r | Owner: levill_r Type: enhancement | Status: new Priority: minor | Milestone: Component: Milena | Version: 2.0 Keywords: | -------------------------+---------------------- * Factor common parts using a template (see HAVM's, MonoBURG's and Nolimips' configurations). * Use uniform names/identifiers (likewise). * We may want to remove some unused or redundant configurations. * The set of compatible agents for all configurations is relatively small; try to install missing requirements and/or make the necessary changes in the project to work around/get rid of these dependencies (e.g. Swig ≠ 2.0.9). -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/285> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 1

[Olena] #299: Use a Team City friendly tests output format
by Olena Trac 14 May '14

14 May '14

#299: Use a Team City friendly tests output format -------------------------+------------------------ Reporter: levill_r | Owner: Olena Team Type: enhancement | Status: new Priority: trivial | Milestone: Component: Team City | Version: 2.0 Keywords: build farm | -------------------------+------------------------ Spot's builds (http://teamcity.lrde.epita.fr/project.html?projectId=Spot&tab=projectOvervi…) produce tests outputs showing detailed information. We should try to enable this for Olena too. -- Ticket URL: <https://trac.lrde.org/olena/ticket/299> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 0

Re: [Olena-bugs] [Olena] #205: Repair the TracNav bar
by Olena Trac 14 May '14

14 May '14

#205: Repair the TracNav bar -----------------------+------------------------ Reporter: levill_r | Owner: Olena Team Type: defect | Status: closed Priority: minor | Milestone: Component: Trac | Version: 1.0 Resolution: wontfix | Keywords: system web -----------------------+------------------------ Changes (by levill_r): * status: new => closed * resolution: => wontfix Comment: Trac's usage is decreasing at LRDE, and it will eventually be replaced by !GitLab (https://gitlab.lrde.epita.fr/) This is a minor problem that won't be fixed; closing. -- Ticket URL: <https://trac.lrde.org/olena/ticket/205#comment:1> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

1 0