Ticket #1941 (new defect)
Finish bipartite graph implementation
| Reported by: | rlm | Owned by: | rlm |
|---|---|---|---|
| Priority: | major | Milestone: | sage-5.11 |
| Component: | graph theory | Keywords: | |
| Cc: | brunellus | Work issues: | |
| Report Upstream: | N/A | Reviewers: | |
| Authors: | Merged in: | ||
| Dependencies: | Stopgaps: |
Description (last modified by brunellus) (diff)
Systematically go through the functions of graph and generic_graph and see which ones, such as add_vertex, need to be overridden in the bipartite graph class so that everything makes sense. Right now, you can add an edge so that the bipartite graph is no longer bipartite.
- add to __cmp__ to distinguish Bipartite from other graphs
- loops - this should always be false for bipartite, right? (other functions with "loops" in the name)
- density - should this reflect "bipartite density"?
- #8330: add_vertex, add_vertices
- clear - left & right too?
- add left_vertices and right_vertices?
- #12376: complement?
- #8329: copy
- #10959, #8744: add_edge(s)
- adjacency_matrix - should this order the vertices a certain way?
- add_cycle
- add_path
- add a function "bipartite_subgraph" to preserve class?
- bipartite_color, bipartite_sets, is_bipartite
Change History
comment:2 Changed 5 years ago by rlm
1. add to __cmp__ to distinguish Bipartite from other graphs 2. loops - this should always be false for bipartite, right? (other functions with "loops" in the name) 3. density - should this reflect "bipartite density"? 4. add_vertex - to which side? 5. add_vertices - what to do with this? 6. clear - left & right too? 7. add left_vertices and right_vertices? 8. complement? 9. copy 10. add_edge(s) 11. adjacency_matrix - should this order the vertices a certain way? 12. add_cycle 13. add_path 14. add a function "bipartite_subgraph" to preserve class? 15. bipartite_color, bipartite_sets, is_bipartite
Note: See
TracTickets for help on using
tickets.
