eXlibris issueshttp://git.gem.ec-nantes.fr/groups/eXlibris/-/issues2018-05-18T07:23:37Zhttp://git.gem.ec-nantes.fr/eXlibris/Xfiles/-/issues/26CGAL interface not compatible with CGAL 4.112018-05-18T07:23:37ZGrégory LEGRAINCGAL interface not compatible with CGAL 4.11AABBPrimitiveExtension.h seems incompatible with new CGAL implementation
`pas de concordance pour l'appel à « (CGAL::Cartesian_base_no_ref_count<double, CGAL::Simple_cartesian<double> >::Construct_projected_point_3 {aka CGAL::CartesianK...AABBPrimitiveExtension.h seems incompatible with new CGAL implementation
`pas de concordance pour l'appel à « (CGAL::Cartesian_base_no_ref_count<double, CGAL::Simple_cartesian<double> >::Construct_projected_point_3 {aka CGAL::CartesianKernelFunctors::Construct_projected_point_3<CGAL::Simple_cartesian<double> >}) (CGAL::internal::Primitive_helper<CGAL::AABB_traits<CGAL::Simple_cartesian<double>, CGAL::AABB_point_primitive<CGAL::Simple_cartesian<double>, __gnu_cxx::__normal_iterator<CGAL::Point_3<CGAL::Simple_cartesian<double> >*, std::vector<CGAL::Point_3<CGAL::Simple_cartesian<double> > > > > >, false>::Datum_type, const Point&) »
Point closest_point = geom_traits.construct_projected_point_3_object()(
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
internal::Primitive_helper<AT>::get_datum(pr,m_traits), p);
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
`
It complains that the point to point case (whici is de fined in AABBPrimitiveExtension. if I am correct) is missing.
Good to know when we will update the version which is available on the platformGrégory LEGRAINGrégory LEGRAINhttp://git.gem.ec-nantes.fr/eXlibris/Xfiles/-/issues/25Keeping boost iostream isolated2018-05-18T07:23:37ZAlexis SALZMANKeeping boost iostream isolatedDiscussion around cmake point out that with some effort (little ?) we may hide boost iostram (used for gzip output) from Xfem interface.
That may also be treated as an extra interface in xInterface.
In one hand treating it in Xfem corr...Discussion around cmake point out that with some effort (little ?) we may hide boost iostram (used for gzip output) from Xfem interface.
That may also be treated as an extra interface in xInterface.
In one hand treating it in Xfem correspond to where it is used for now, in the other adding it as an Xinterface gives a way to use it everywhere.http://git.gem.ec-nantes.fr/eXlibris/ExternalLib/-/issues/1populate2017-12-12T09:13:49ZAlexis SALZMANpopulateThis have to be populate at least with following source package:
<ul><li> mumps 4.10
</li><li>pastix 5.2.1
</li><li>taucs 2.2
</li><li>SuperLU 3.0
</li><li>scotch 5.1.8
</li><li>parmetis 3.1.1
</li><li>CGAL 4.2
...This have to be populate at least with following source package:
<ul><li> mumps 4.10
</li><li>pastix 5.2.1
</li><li>taucs 2.2
</li><li>SuperLU 3.0
</li><li>scotch 5.1.8
</li><li>parmetis 3.1.1
</li><li>CGAL 4.2
</li><li>ann 1.1.2
</li><li>autopack 1.3.2
</ul>
As we stay with old software version for now.
Otherwise eXlibris interface should work with following newer version in future:
<ul><li>mumps 5.0.1 (and above normally but API check needed)
</li><li>taucs 2.2 (patched)
</li><li>pastix ?? (with new scotch API which version is needed and compatible with eXlibris interface is an open question)
</li><li>SuperLU ?? (with new metis API which version is needed and compatible with eXlibris interface is an open question)
</li><li> scotch 6.0.0
</li><li>parmetis 4.0.3
</ul>http://git.gem.ec-nantes.fr/eXlibris/Xfiles/-/issues/24treillis with _DEBUG_ macro enable2018-05-18T07:23:37ZAlexis SALZMANtreillis with _DEBUG_ macro enableIn Treillis, in mVector and mPoint (at least) if _DEBUG_ macro is enable code does not compile.
Bug correction needed.
For now don't turn on USE_DEBUG_FLAG option in cmake (which is not only a printing stuff as message suggest)In Treillis, in mVector and mPoint (at least) if _DEBUG_ macro is enable code does not compile.
Bug correction needed.
For now don't turn on USE_DEBUG_FLAG option in cmake (which is not only a printing stuff as message suggest)http://git.gem.ec-nantes.fr/eXlibris/Xfiles/-/issues/21Removing xFitToVertexKeyManager in xFitToVertices class2018-05-18T07:23:38ZAlexis SALZMANRemoving xFitToVertexKeyManager in xFitToVertices classFollowing commit 5d34c604 the key manager xFitToVertexKeyManager should be remove and usage replace by new keyManagerSendOrReceiveFollowing commit 5d34c604 the key manager xFitToVertexKeyManager should be remove and usage replace by new keyManagerSendOrReceivehttp://git.gem.ec-nantes.fr/eXlibris/Xfiles/-/issues/16xCFL getDt2018-05-18T07:23:38ZAlexis SALZMANxCFL getDtFrom Kevin Moreau this is weird to divide by 1 and by 2 ! missing parenthesis (i.e. divinding by 0.5) or volonteer (i.e. divinding by 2.)
<br>
double xCFL::getDt(xRegion s) {<br>
return ((xCFL::getLength(s))/1./2.);<br>
}From Kevin Moreau this is weird to divide by 1 and by 2 ! missing parenthesis (i.e. divinding by 0.5) or volonteer (i.e. divinding by 2.)
<br>
double xCFL::getDt(xRegion s) {<br>
return ((xCFL::getLength(s))/1./2.);<br>
}http://git.gem.ec-nantes.fr/eXlibris/Xfiles/-/issues/14newMeshDataId vs lookupMeshDataId2018-05-18T07:23:38ZAlexis SALZMANnewMeshDataId vs lookupMeshDataIdIt looks like lookupMeshDataId have been used in many place in xfem. But it is not so clear to me that newMeshDataId would have not been the right choice in some cases.
To checkIt looks like lookupMeshDataId have been used in many place in xfem. But it is not so clear to me that newMeshDataId would have not been the right choice in some cases.
To checkhttp://git.gem.ec-nantes.fr/eXlibris/Xfiles/-/issues/11Boost2018-05-18T07:23:38ZAlexis SALZMANBoostCommit 297718b and GemUtil commit 12aa2c6 introduce new BOOST_SPECIAL_INCLUDE_PATH variable.
It have been used sucessfully with Xfem and SplitMesh/test. But it had to be done on all CMAKE of eXlibris where it have to.
It replace prope...Commit 297718b and GemUtil commit 12aa2c6 introduce new BOOST_SPECIAL_INCLUDE_PATH variable.
It have been used sucessfully with Xfem and SplitMesh/test. But it had to be done on all CMAKE of eXlibris where it have to.
It replace properly what was done in eXlibrisType.
Boost version checking mechanism may have to be adapted.