[Insight-developers] Mesh IO : IJ

[Alexandre GOUAILLARD]

my understanding is that all v4 i alpha and we can change API for at
least until march (beta release).
so the question is: do we work in the main architecture or in review.

I would prefer to move the code out of review and work there.

now, I agree there are some changes to be made that will impact
architecture. Thanks for the wiki page (did not look at it yet). let's
keep it alive and speak about it in iowa.

thanks again,

alex.


On Tue, Sep 28, 2010 at 10:05 PM, Arnaud Gelas
<Arnaud_Gelas at hms.harvard.edu> wrote:
> Hi Alex,
> To my opinion, we should hold on merging.
> It seems that there are two problems to be addressed: data with QE Mesh and
> data processing in filters (I started a wiki page on this last
> problem: http://www.itk.org/Wiki/ITK_Release_4/QuadEdgeMesh_Filter/DataProcessing).
> Fixing these two problems may impact base classes, the usage of  all QE Mesh
> filters, and might impact the backward compatibility (over next releases).
> If we can change API after moving out QE Mesh, I'd say: Go!
> Else we shall first fix these two issues.
> Thanks,
> Arnaud
>
> On Sep 27, 2010, at 11:29 PM, Alexandre GOUAILLARD wrote:
>
> Before we do that, I need your advice: do you think we should hold on
>
> moving the Decimation classes from review then? We know there is a
>
> performance issue we did not address either, and I had written in my
>
> to do list to write a benchmark, and profile this part (most likely a
>
> problem in our implementation of the mutable priority list).
>
> The rest of QE (the structure and the other filters) could move
> independantly.
>
> please advise.
>
> alex.
>
>
>
> hi arnaud,
>
> I'm holding on a big merge waiting for  your answer.
>
> Could you please advise?
>
> alex.
>
>