ZigRazor / ZigRazor/CXXGraph

Input & Output file format

Open
#172 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

core development enhancement hacktoberfest Priority:Medium
Dominant language
C++
Stars
729
Forks
147
Avg merge
19h
Merged PRs (30d)
1

Description

Discussed in https://github.com/ZigRazor/CXXGraph/discussions/170

Originally posted by sidml November 2, 2021
I was thinking that we should ensure compatibility with existing popular formats for saving and loading graphs. Following is taken from here

The BGL currently provides two graph classes and an edge list adaptor:
adjacency_list
adjacency_matrix
edge_list

The adjacency_list class is the general purpose “swiss army knife” of graph classes. It is highly parameterized so that it can be optimized for different situations: the graph is directed or undirected, allow or disallow parallel edges, efficient access to just the out-edges or also to the in-edges, fast vertex insertion and removal at the cost of extra space overhead, etc.

The adjacency_matrix class stores edges in a |V| x |V| matrix (where |V| is the number of vertices). The elements of this matrix represent edges in the graph. Adjacency matrix representations are especially suitable for very dense graphs, i.e., those where the number of edges approaches |V|2.

The edge_list class is an adaptor that takes any kind of edge iterator and implements an Edge List Graph.

Let me know what you guys think.
@ZigRazor @AlfredCP @pavan-pan

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with Discussion #170 and the linked Boost Graph Library documentation to understand the proposed compatibility scope. The issue names no target format, source file, test, or acceptance criteria; done should be defined after the supported format(s) and validation approach are agreed.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.