Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S sasa
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 8
    • Issues 8
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • verimag
  • synchrone
  • sasa
  • Issues
  • #3

Closed
Open
Created May 17, 2019 by erwan@jahierOwner

Compute the graph degree, diameter, etc.

Indeed, this info can be useful for some algo, and would avoid one to hard-code it in the algo, which outgh to work on any graph.

For example, in the following example, the diameter is hard-coded : https://gricad-gitlab.univ-grenoble-alpes.fr/verimag/synchrone/sasa/blob/master/test/bfs-spanning-tree/p.ml

Assignee
Assign to
Time tracking