CGAL users discussion list

[Monique Teillaud <>]

Le 08/05/15 17:27, Tom Van Doorsselaere a écrit :
> Dear CGAL enthousiasts,

:)
Dear Tom,

> I'm building a program for the rendering of emission of solar coronal
> models.

This sounds very interesting.

I tested your code on my laptop, with CGAL 4.6, both release and debug 
modes, clang 5.0.

I had to add a space line 61 to avoid the consecutive >>
vector<vector<double> > allvar;
Then it compiled.

teillaud@tzitziki:~/CGAL/test >./testreadinwriteout --write
writing out triangulationGelukt
teillaud@tzitziki:~/CGAL/test >./testreadinwriteout --read
reading in triangulationGelukt

If I understand correctly, this is the result that you expect. It seems 
to work like a charm...

Best regards,
--
Monique Teillaud
http://www.loria.fr/~teillaud/
INRIA Nancy - Grand Est, LORIA
Institut National de Recherche en Informatique et Automatique

> For that I'm doing simulations first, computing the
> triangulation, which I then render onto artificial images. Since it is
> the bottleneck of the computation, I would like to store the
> triangulation, to be read in again for the rendering stage.
>
> I have attached a minimal representation of my code, with test data. I
> have compiled the code with gcc version 4.4.7:
> g++ -frounding-math -std=gnu++0x -g -Wall -lCGAL -lgmp -o testreadin
> testreadinwriteout.cpp
>
> and then run it with
>
> -----------------------
> > ./testreadin --write
> writing out triangulationGelukt
> -----------------------
>
>   and
>
> -----------------------
> > ./testreadin --read
> terminate called after throwing an instance of 'CGAL::Assertion_exception'
>    what():  CGAL ERROR: assertion violation!
> Expr: false
> File: /usr/include/CGAL/Triangulation_3.h
> Line: 5321
> reading in triangulationAborted
> -----------------------
>
> I have no idea what can cause this issue, because I have checked the
> validity of the triangulation in the write stage, and I would expect a
> written valid triangulation to be read in again as one.
>
> Even more confusing is that when I remove the conversion from
> cylindrical coordinates in the data file to cartesian coordinates in the
> code (i.e. line 82 and 83 in the attached program), then the reading in
> and writing out is no issue and both stages work as expected.
>
> What important issue am I missing here?
>
> Thanks for your input!
>
> Tom