#19007: Refactor Closeness Centrality
-------------------------------------+-------------------------------------
Reporter: borassi | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.9
Component: graph theory | Resolution:
Keywords: Closeness | Merged in:
centrality | Reviewers:
Authors: Michele Borassi | Work issues:
Report Upstream: N/A | Commit:
Branch: | f1c7fd57d513efda616b6dc8c3a81c7891ef5f12
u/borassi/refactor_centrality_closeness| Stopgaps:
Dependencies: #18931, #18876, |
#18910 |
-------------------------------------+-------------------------------------
Comment (by borassi):
I'm afraid that all the attempts I have made were unsuccessful. The point
is that importing module `centrality.pyx` at startup is expensive, and I
need it to import it to add method `centrality_closeness` to
`GenericGraph`. Hence, the startup time becomes 2 seconds (too much).
In my opinion, this might be a reason why it is better to leave method
`centrality_closeness` in `generic_graph`, and put only Cython-related
methods inside `centrality.pyx`, in order to use lazy imports. May I move
method centrality_closeness back?
If we still want to move `centrality_closeness` and related methods to
`centrality.pyx`, I think we should open another ticket, in order to find
a way to use lazy imports (I have no idea how, though).
--
Ticket URL: <http://trac.sagemath.org/ticket/19007#comment:32>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.