From: Derek G. <der...@in...> - 2010-07-13 17:16:26
|
Hmmm... it appears that the Elem class is missing in the libMesh doxygen currently on the website. I can't come up with any reason why it's missing other than a botched doxygen run.... Derek |
From: John P. <pet...@cf...> - 2010-07-13 18:00:37
|
On Tue, Jul 13, 2010 at 12:16 PM, Derek Gaston <der...@in...> wrote: > Hmmm... it appears that the Elem class is missing in the libMesh doxygen currently on the website. > > I can't come up with any reason why it's missing other than a botched doxygen run.... Strange indeed. I reran doxygen on my box and it does not appear to have generated an Elem page either. (This is a little hard to debug locally, any idea how to get a browser to process local php files w/o running a webserver, etc?) There were a bunch of warnings for elem.C (below) so it is actually processing the file. None of them really appear to be fatal though... -- John .../libmesh-petsc3/src/geom/elem.C:64 Warning: documented function `const unsigned int libMesh::Elem::_bp1' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:65 Warning: documented function `const unsigned int libMesh::Elem::_bp2' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:105 Warning: documented function `const unsigned int libMesh::Elem::type_to_n_nodes_map' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:113 Warning: no uniquely matching class member found for AutoPtr< Elem > libMesh::Elem::build(const ElemType type, Elem *p) .../libmesh-petsc3/src/geom/elem.C:281 Warning: no matching file member found for Point libMesh::Elem::centroid() const Possible candidates: static libMesh::Point centroid static libMesh::Point centroid static libMesh::Point centroid FactoryImp< CentroidPartitioner, Partitioner > centroid("Centroid") .../libmesh-petsc3/src/geom/elem.C:293 Warning: documented function `Real libMesh::Elem::hmin' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:310 Warning: documented function `Real libMesh::Elem::hmax' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:328 Warning: documented function `Real libMesh::Elem::length' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:338 Warning: no uniquely matching class member found for bool libMesh::Elem::operator==(const DofObject &rhs) const .../libmesh-petsc3/src/geom/elem.C:436 Warning: documented function `bool libMesh::Elem::contains_vertex_of' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:447 Warning: documented function `bool libMesh::Elem::contains_edge_of' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:468 Warning: no matching class member found for void libMesh::Elem::find_point_neighbors(std::set< const Elem * > &neighbor_set) const .../libmesh-petsc3/src/geom/elem.C:526 Warning: documented function `void libMesh::Elem::find_edge_neighbors' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:586 Warning: no matching file member found for void libMesh::Elem::libmesh_assert_valid_node_pointers() const Possible candidates: void libmesh_assert_valid_node_pointers(const MeshBase &mesh) .../libmesh-petsc3/src/geom/elem.C:598 Warning: no matching file member found for void libMesh::Elem::libmesh_assert_valid_neighbors() const Possible candidates: void libmesh_assert_valid_neighbors(const MeshBase &mesh) .../libmesh-petsc3/src/geom/elem.C:660 Warning: documented function `void libMesh::Elem::make_links_to_me_remote' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:773 Warning: documented function `void libMesh::Elem::write_connectivity' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:851 Warning: no uniquely matching class member found for Real libMesh::Elem::quality(const ElemQuality q) const .../libmesh-petsc3/src/geom/elem.C:880 Warning: documented function `bool libMesh::Elem::ancestor' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:902 Warning: no uniquely matching class member found for void libMesh::Elem::add_child(Elem *elem) .../libmesh-petsc3/src/geom/elem.C:929 Warning: no uniquely matching class member found for void libMesh::Elem::add_child(Elem *elem, unsigned int c) .../libmesh-petsc3/src/geom/elem.C:948 Warning: documented function `bool libMesh::Elem::is_child_on_edge' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:964 Warning: documented function `void libMesh::Elem::family_tree' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:987 Warning: documented function `void libMesh::Elem::active_family_tree' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:1012 Warning: documented function `void libMesh::Elem::family_tree_by_side' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:1039 Warning: documented function `void libMesh::Elem::active_family_tree_by_side' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:1066 Warning: documented function `void libMesh::Elem::family_tree_by_neighbor' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:1097 Warning: documented function `void libMesh::Elem::family_tree_by_subneighbor' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:1144 Warning: documented function `void libMesh::Elem::active_family_tree_by_neighbor' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:1175 Warning: documented function `unsigned int libMesh::Elem::min_p_level_by_neighbor' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:1208 Warning: documented function `unsigned int libMesh::Elem::min_new_p_level_by_neighbor' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:1248 Warning: no uniquely matching class member found for bool libMesh::Elem::contains_point(const Point &p, Real tol) const .../libmesh-petsc3/src/geom/elem.C:1266 Warning: documented function `void libMesh::Elem::nullify_neighbors' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:1292 Warning: no uniquely matching class member found for unsigned int libMesh::Elem::n_second_order_adjacent_vertices(const unsigned int) const .../libmesh-petsc3/src/geom/elem.C:1301 Warning: no uniquely matching class member found for unsigned short int libMesh::Elem::second_order_adjacent_vertex(const unsigned int, const unsigned int) const .../libmesh-petsc3/src/geom/elem.C:1310 Warning: no uniquely matching class member found for std::pair< unsigned short int, unsigned short int > libMesh::Elem::second_order_child_vertex(const unsigned int) const .../libmesh-petsc3/src/geom/elem.C:1318 Warning: documented function `ElemType libMesh::Elem::first_order_equivalent_type' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:1369 Warning: documented function `ElemType libMesh::Elem::second_order_equivalent_type' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:1477 Warning: documented function `Elem::side_iterator libMesh::Elem::boundary_sides_begin' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:1486 Warning: documented function `Elem::side_iterator libMesh::Elem::boundary_sides_end' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:1495 Warning: no uniquely matching class member found for Real libMesh::Elem::volume() const .../libmesh-petsc3/src/geom/elem.C:1526 Warning: documented function `const unsigned int libMesh::Elem::PackedElem::header_size' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:1531 Warning: documented function `void libMesh::Elem::PackedElem::pack' was not declared or defined. .../libmesh-petsc3/src/geom/elem.C:1579 Warning: documented function `Elem * libMesh::Elem::PackedElem::unpack' was not declared or defined. |
From: Roy S. <roy...@ic...> - 2010-07-13 18:09:36
|
On Tue, 13 Jul 2010, John Peterson wrote: > On Tue, Jul 13, 2010 at 12:16 PM, Derek Gaston <der...@in...> wrote: >> Hmmm... it appears that the Elem class is missing in the libMesh doxygen currently on the website. >> >> I can't come up with any reason why it's missing other than a botched doxygen run.... > > Strange indeed. I reran doxygen on my box and it does not appear to > have generated an Elem page either. (This is a little hard to debug > locally, any idea how to get a browser to process local php files w/o > running a webserver, etc?) There were a bunch of warnings for elem.C > (below) so it is actually processing the file. None of them really > appear to be fatal though... It's generating a file for elem.h, but yeah, all those warnings are consistent with it somehow not seeing the Elem class. Very weird... --- Roy |
From: Tim K. <tim...@ce...> - 2010-09-16 13:17:23
Attachments:
elem-patch
|
On Tue, 13 Jul 2010, Roy Stogner wrote: > On Tue, 13 Jul 2010, John Peterson wrote: > >> On Tue, Jul 13, 2010 at 12:16 PM, Derek Gaston <der...@in...> wrote: >>> Hmmm... it appears that the Elem class is missing in the libMesh doxygen currently on the website. >>> >>> I can't come up with any reason why it's missing other than a botched doxygen run.... >> >> Strange indeed. I reran doxygen on my box and it does not appear to >> have generated an Elem page either. (This is a little hard to debug >> locally, any idea how to get a browser to process local php files w/o >> running a webserver, etc?) There were a bunch of warnings for elem.C >> (below) so it is actually processing the file. None of them really >> appear to be fatal though... > > It's generating a file for elem.h, but yeah, all those warnings are > consistent with it somehow not seeing the Elem class. Very weird... This keep annoying me continuously, so I tracked it back and found that the attached patch solves the problem, although I don't know why. I'll check that in if nobody objects. Will the documentation be regenerated and uploaded automatically then? Best Regards, Tim -- Dr. Tim Kroeger CeVis -- Center of Complex Systems and Visualization University of Bremen tim...@ce... Universitaetsallee 29 tim...@me... D-28359 Bremen Phone +49-421-218-7710 Germany Fax +49-421-218-4236 |
From: Roy S. <roy...@ic...> - 2010-09-16 14:08:35
|
On Thu, 16 Sep 2010, Tim Kroeger wrote: > This keep annoying me continuously, so I tracked it back and found that the > attached patch solves the problem, although I don't know why. I'll check that > in if nobody objects. I wonder if doxygen is getting confused by my spartan ifdefs there? Unless you take one preprocessor path or the other the braces don't even match up; of course the compiler will be fine but perhaps doxygen's parser gets confused by it. Maybe try making a copy of that "return false;\n}" and put the two copies inside the two halfs of the ifdef/else? That would be a cleaner solution. Of course, if the fix you've found is the only one that works then by all means, check it in, cleaner be damned. > Will the documentation be regenerated and uploaded automatically then? No; "make doc upload" does that. You should have write permissions to the svn web space, but if it gives you any trouble let us know. Thanks!! --- Roy |
From: Tim K. <tim...@ce...> - 2010-09-16 15:21:34
Attachments:
elem-patch2
|
On Thu, 16 Sep 2010, Roy Stogner wrote: > On Thu, 16 Sep 2010, Tim Kroeger wrote: > >> This keep annoying me continuously, so I tracked it back and found that the >> attached patch solves the problem, although I don't know why. I'll check >> that in if nobody objects. > > I wonder if doxygen is getting confused by my spartan ifdefs there? > Unless you take one preprocessor path or the other the braces don't > even match up; of course the compiler will be fine but perhaps > doxygen's parser gets confused by it. Maybe try making a copy of that > "return false;\n}" and put the two copies inside the two halfs of the > ifdef/else? That would be a cleaner solution. That does not solve the problem. However, the attached method does and is certainly cleaner than my first solution. I'll check that in if you agree (or you can check it in yourself if you like). >> Will the documentation be regenerated and uploaded automatically then? > > No; "make doc upload" does that. You should have write permissions to > the svn web space, but if it gives you any trouble let us know. The problem is that this will also upload the documentation for my subset_solve work. Hence I suggest that you upload it this time (provided that your working copy does not have any local changes). I will know what to do later when the subset_solve stuff is finished. Best Regards, Tim -- Dr. Tim Kroeger CeVis -- Center of Complex Systems and Visualization University of Bremen tim...@ce... Universitaetsallee 29 tim...@me... D-28359 Bremen Phone +49-421-218-7710 Germany Fax +49-421-218-4236 |
From: Roy S. <roy...@ic...> - 2010-09-16 16:55:40
|
On Thu, 16 Sep 2010, Tim Kroeger wrote: > That does not solve the problem. However, the attached method does and is > certainly cleaner than my first solution. I'll check that in if you agree > (or you can check it in yourself if you like). It works for me and looks nicer than the original metacode. It's checked in and I've uploaded the fixed docs. Thanks again! --- Roy |
From: Derek G. <fri...@gm...> - 2010-09-16 18:26:27
|
Sweet! Thanks for working on this Tim! Derek On Sep 16, 2010, at 10:55 AM, Roy Stogner wrote: > > On Thu, 16 Sep 2010, Tim Kroeger wrote: > >> That does not solve the problem. However, the attached method does and is >> certainly cleaner than my first solution. I'll check that in if you agree >> (or you can check it in yourself if you like). > > It works for me and looks nicer than the original metacode. It's > checked in and I've uploaded the fixed docs. Thanks again! > --- > Roy > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > Libmesh-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libmesh-devel |