Simplify combined_networks structure?
@krivit is already working on this.
Since Mar 15, 2026.
- #44 by @copilot-swe-agent — closed without merging
Assessment
This issue has not been assessed yet.
Description
Currently, the system is designed to, in principle, be able to un-combine networks in any order. It may make sense to instead mandate that the networks be uncombined in the same order as they are combined. This will simplify the data structure and save memory. It may also make sense to store subnetwork information not on vertices but on subnetworks (and the .subnetattr of the combined network).
uncombine_networks() can also be simplified, since we would then only need to take the .subnetcache networks and copy the edges.
This is related to #42, since it needs to assume that the uncombining is done in reverse order of the combining.
- Dominant language
- R
- Stars
- 16
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from statnet/ergm.multi
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
statnet/ergm.multi#42 · 3 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
statnet/ergm.multi#39 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
statnet/ergm.multi#38 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
statnet/ergm.multi#27 · 4 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
statnet/ergm.multi#16 · 2 comments ·
All issues in statnet/ergm.multi
Similar issues
-
Typos in schema fileOpen
Difficulty 1/5 1-3 hours Newbie friendliness 65/100
-
Component: R
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days
-
bug pixi-build-r
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
prefix-dev/pixi#7229 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
rstudio/reticulate#1933 ·