lanl / lanl/dfnWorks

dfnGraph (v2.8) fails to identify the backbones with bipartite approach considering weight (length and hydraulic resistence)

Open
#85 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
96
Forks
53
Avg merge
2h 58m
Merged PRs (30d)
2

Description

Hello all,

When i run the example "pruning" to generate bipartite graphs, there is an error:
image
So i change the code in "pruning.py":
"path_nodes = sorted(list(k_shortest))--------> path_nodes =list(k_shortest)"
Then the running is OK.

However, if i try to use "greedy_edge_disjoint" method to identifying the backbones of DFN, here is another issue:
image
So i change the code in "pruning.py" again:
"if G.graph['representation'] != "intersection":--------> if G.graph['representation'] != "bipartite":"
Then the running is OK. Is it right?

These results are good for me. However,how can i identify the backbones with bipartite graph-based approach considering weight (length and hydraulic resistence) ? Is there any open source codes ? I cann't find it. So i cann't repeat the results in:
Hyman et al. 2018 "Identifying Backbones in Three-Dimensional Discrete Fracture Networks: A Bipartite Graph-Based Approach" SIAM Multiscale Modeling and Simulation.

Thanks in advance!

Contributor guide

No contributing guide indexed for this repository

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 by reproducing the "pruning" example and inspect the reported paths in pruning.py, including the k_shortest handling and greedy_edge_disjoint representation check. Compare the weighted bipartite-backbone question with the Hyman et al. 2018 reference and determine whether this approach is supported; done should include a reproducible result and a clear answer about the required implementation or documentation.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, data
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.