Olena-bugs October 2013

olena-bugs@lrde.epita.fr

1 participants
15 discussions

[Olena] #295: Morpher applying a function with memoization

by Olena Trac

#295: Morpher applying a function with memoization --------------------------------------------------+------------------------ Reporter: levill_r | Owner: Olena Team Type: task | Status: new Priority: trivial | Milestone: Component: Milena | Version: 2.0 Keywords: laziness non-strictness call-by-need | --------------------------------------------------+------------------------ In addition to our morpher(s) performing point-site-wise function application, we should experiment with a version providing a memoization mechanism, and evaluate the potential gains on various use cases (especially when working on a subset of an image). We should start by implementing a read-only morpher and see whether a read/write version is feasible or even relevant. -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/295> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

10 years, 6 months

[Olena] #294: Streamline and improve morphers

by Olena Trac

#294: Streamline and improve morphers -------------------------+------------------------ Reporter: levill_r | Owner: Olena Team Type: enhancement | Status: new Priority: major | Milestone: Component: Milena | Version: 2.0 Keywords: | -------------------------+------------------------ Foreword: this should of course be done both in the code *and* in the documentation (e.g. in a section "Guidelines for future morphers"). Some reflexions: * We must carefully set a policy regarding embedded images (are they copied into morphers or manipulated through references/pointers?) * Hence a potential directive in the documentation regarding the implementation/manipulation of all images in Milena: should they all be manipulated by copies, but behaved as smart pointers, sharing data? * Does this mean we should never manipulate images through references (within morphers, but also elsewhere) and let the smart (tracked) pointer do the job of allocating/freeing memory? * Also, what about the constness of embeded images? All morphers are currently not equal before this aspect. -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/294> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

10 years, 6 months

[Olena] #293: Experiment with Vagrant

by Olena Trac

#293: Experiment with Vagrant --------------------------------------------+------------------------ Reporter: levill_r | Owner: Olena Team Type: proposal | Status: new Priority: trivial | Milestone: Component: Olena | Version: 2.0 Keywords: virtual machine virtualization | --------------------------------------------+------------------------ Vagrant makes VM instantiation, use and disposal easy: http://www.vagrantup.com/ We should definitely have a look at it, and possibly consider using it in Olena's test suite(s) (e.g. as part of the continuous integration service). -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/293> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

10 years, 6 months

Re: [Olena-bugs] [Olena] #232: Update contributors' list on Olena's Web site

by Olena Trac

#232: Update contributors' list on Olena's Web site -----------------------+------------------------ Reporter: levill_r | Owner: Olena Team Type: task | Status: new Priority: critical | Milestone: Olena 2.1 Component: Web | Version: 1.0 Resolution: | Keywords: -----------------------+------------------------ Changes (by levill_r): * cc: demoulins (added) * milestone: Olena 2.2 => Olena 2.1 Old description: > This page : > > https://www.lrde.epita.fr/cgi-bin/twiki/view/Olena/Contributors > > should be updated with the latest version (e.g., from branch `next`) of > this file : > > source:AUTHORS > > Better: write a script to automate the conversion, so as to simplify the > process of updating this page down to a copy-and-paste operation. New description: This page : http://www.lrde.epita.fr/cgi-bin/twiki/view/Olena/Contributors should be updated with the latest version of this file (i.e., from `master`): source:AUTHORS Better: write a script to automate the conversion, so as to simplify the process of updating this page down to a copy-and-paste operation. We should look at other LRDE projects to see how they handle this issue. Handling this together with the migration to the new (!MediaWiki-based) Web server (see #292) would be a good idea. -- Comment: * s/https/http/ * s/next/master/ * Mention other projects. * CC Clément. -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/232#comment:3> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

10 years, 6 months

Re: [Olena-bugs] [Olena] #281: Repair the online Document Layout Analysis and Reconstruction demo

by Olena Trac

#281: Repair the online Document Layout Analysis and Reconstruction demo -----------------------+--------------------------- Reporter: levill_r | Owner: levill_r Type: defect | Status: new Priority: major | Milestone: Olena 2.1 Component: Web | Version: 2.0 Resolution: | Keywords: demonstration -----------------------+--------------------------- Changes (by levill_r): * milestone: => Olena 2.1 -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/281#comment:2> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform

10 years, 7 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 October 2013