Olena/Paradigm2003

This major version of Olena is a transitory phase for 0.9 release. 2003paradigm version of oln project mainly concerns the transition to a new kind of static hierarchy and a new modeling.

PRCS major version

oln.2003paradigm

prcs checkout -r2003paradigm oln

Done

• Transition to the Exact static hierarchy
• New modeling (core)
• clean directories and related tests:
  • arith: Main.SylvainBerlemont done
  • convert: Main.RedaDehak done
  • convol: Main.AstridWang done
  • core: Main.DavidLesage and Main.NicolasBurrus done
  • doc: Main.GiovanniPalma and Main.NicolasBurrus done
  • io: Main.NicolasBurrus & Main.DavidLesage done
  • level: Main.SylvainBerlemont done
  • math: Main.RedaDehak done
  • morpho: Main.GiovanniPalma done
  • swilena: Main.DavidLesage and Main.NicolasBurrus done
  • tools: Main.DavidLesage done
  • topo: Main.SylvainBerlemont done
  • transforms: Main.RedaDehak done
  • utils: Main.SylvainBerlemont done

TODO

• Coding style: Main.DavidLesage & Main.NicolasBurrus: nearly done

• iterators on data
  • should be added in image_impl interface
  • usage:

     abstract::image<E>::impl_fwd_iter_type it(ima); for (it = begin; it != end; ++it) std::cout << *it; 

HowTo clean a directory

• the aim is to make it check
• associated tests (olena/tests) must be adapted

• things to take care about
  • includes: some files have disappeared: ex: core/internal/*image*.hh, core/border*.hh. Please refer to the documentation and/or Main.NicolasBurrus & Main.DavidLesage.
  • ExactCref: they must disappear. Take also care about template parameters that should not have the "underscore" style anymore.
  • Borders operations: there is no namespace "border" anymore. All these operations are now image member functions.
  • For any question about the new modeling, please refer to the documentation and/or Main.NicolasBurrus & Main.DavidLesage.

Documentation

A dia UML diagram is available here: ~david/pub/new_olena_model.{dia, ps}

Suggestions

Image Hierarchy Modeling

• Adding a new discriminant: one related to the way the object is stored in memory. It allows having dense/sparse images, for example, represented differently in memory. Maybe taking a few ideas from vaucanson is a good thing ? (i'm thinking of the 'Element' model) Plus, this model can include function images, as well, thus leading us to a 'Unified Model'. -- Main.YoussefElfassyfihry