vcswatch reports that
this package seems to have a new changelog entry (version
3.4-1, distribution
unstable) and new commits
in its VCS. You should consider whether it's time to make
an upload.
Here are the relevant commit messages:
commit f3acfddecd4e20e36a6237500680cb63e730111b
Author: Dimitris Kalamaras <dimitris.kalamaras@gmail.com>
Date: Wed Apr 1 23:39:55 2026 +0300
update .gitignore
commit d350b1127bcec80d434e754e0d57b0445a006e79
Author: Dimitris Kalamaras <dimitris.kalamaras@gmail.com>
Date: Sat Mar 28 03:00:35 2026 +0200
WS6 | socnetv-cli: document clustering kernel v6, add baselines and golden coverage [ci]
commit f4d7daf5a4ca9ced7ebc8b651f23944f1994b36b
Author: Dimitris Kalamaras <dimitris.kalamaras@gmail.com>
Date: Sat Mar 28 02:37:57 2026 +0200
WS9 | fix(filters): reset visibility history on graph clear and initApp
- Clear m_visibilityHistory in Graph constructor and Graph::clear()
to prevent stale filter snapshots surviving a network reload
- Disable filterNodesRestoreAllAct in MainWindow::initApp()
so the UI state stays consistent with the empty history stack
Refs #210 [ci]
commit 0e94f38218802f42a0b4a2e3ba46c29d60fb43d7
Author: Dimitris Kalamaras <dimitris.kalamaras@gmail.com>
Date: Sat Mar 28 02:24:08 2026 +0200
docs
commit ba92793e8eada527537e25198fbe5111e7a29d43
Author: Dimitris Kalamaras <dimitris.kalamaras@gmail.com>
Date: Sat Mar 28 02:24:02 2026 +0200
Graph | graphTriadCensus() | fix - as it was it appended 16 new zeros every time the routine runs. That was risky for repeated runs in one process.
commit 6e6df48d9f7db23a0a8afba0581520a25f104f93
Author: Dimitris Kalamaras <dimitris.kalamaras@gmail.com>
Date: Sat Mar 28 02:22:03 2026 +0200
CLI: add clustering kernel v6 + Graph triad census accessor
- Add kernel_clustering_v6 (CLC, triad census, clique census)
- Use Graph::clusteringCoefficient(), graphTriadCensus(), graphCliques()
- Add Graph::graphTriadTypeFreqs() const accessor (read-only)
- Follow kernel_prominence_v4 structure and schema conventions
- Introduce schema_version=6 for clustering regression harness
commit cb544698767961f6b0387020851c90ec93a3a5d1
Author: Dimitris Kalamaras <dimitris.kalamaras@gmail.com>
Date: Sat Mar 28 02:21:32 2026 +0200
WS9 | fix(ui): enable filterNodesByEgoNetworkAct based on selection state
Enable "Focus on Node (Ego Network)" action only when exactly one
node is selected. Wired into slotEditSelectionChanged() which is
already driven by signalSelectionChanged from Graph.
Closes #210
commit a4815cb80ace4e8c635948a57d13b79965686beb
Author: Dimitris Kalamaras <dimitris.kalamaras@gmail.com>
Date: Sat Mar 28 01:32:49 2026 +0200
WS9 | feat(ui): wire ego network focus mode into MainWindow (#210)
- Add slotFilterNodesByEgoNetwork() and slotFilterNodesRestoreAll() slots
- Add filterNodesByEgoNetworkAct and filterNodesRestoreAllAct QActions
with keyboard shortcuts (Ctrl+X, Ctrl+F / Ctrl+X, Ctrl+R)
- Add visibilityHistoryEmpty() to Graph for UI enable/disable state
- Place both actions at the top of the Filter menu, above existing filters
- filterNodesRestoreAllAct is enabled only when history stack is non-empty
Refs #210 [ci]
commit 51977b9a1d61bcf4608e11f20b3ee68c4d06cea8
Author: Dimitris Kalamaras <dimitris.kalamaras@gmail.com>
Date: Sat Mar 28 01:12:46 2026 +0200
WS9 | feat(filters): add vertexFilterByEgoNetwork() and vertexFilterRestoreAll()
Introduces non-destructive ego network focus mode for #210.
- vertexFilterByEgoNetwork(v1, depth): hides all vertices and edges
not in the 1-hop neighborhood of v1 in the current relation.
Uses enabled out-edges only (correct for both directed/undirected).
- vertexFilterRestoreAll(): restores visibility from the top snapshot
on the history stack, one step at a time.
Both functions use GraphVisibilitySnapshot pushed onto
m_visibilityHistory (QStack) before any changes are made,
laying the foundation for future undo/redo support.
Closes #210 (backend)
Refs #215
commit 77c63c1b5453aa36fc3efb6b46f9ab01294db948
Author: Dimitris Kalamaras <dimitris.kalamaras@gmail.com>
Date: Fri Mar 27 18:49:42 2026 +0200
WS9 | minor updates
Refs #210
commit 693e35a7c879ebf705542790a79a609bcc96bf24
Author: Dimitris Kalamaras <dimitris.kalamaras@gmail.com>
Date: Fri Mar 27 18:45:56 2026 +0200
WS9 | refactor(vertex): rename neighborhoodList to reciprocalNeighborhoodList
The function only returns mutually connected neighbors, not all 1-hop
neighbors. Rename to accurately reflect semantics.
- Replace member buffer m_neighborhoodList with a local return value
- Fix fragile qreal equality check: use != 0 instead of == m_weight
- Update all call sites in Graph and GraphVertex
- Update vertexNeighborhoodList() and vertexNeighborhoodSet() accordingly
Refs #210
commit e64222af9ff562fc18753b99b1d7efec5797f2f8
Author: Dimitris Kalamaras <dimitris.kalamaras@gmail.com>
Date: Fri Mar 27 18:28:02 2026 +0200
WS9 | fix(filters): use non-const iterator for H_edges mutation in edge/node filters
QMultiHash::const_iterator::value() returns const T&, making assignment
through cbegin()/cend() iterators semantically incorrect. Switch to
non-const iterator in edgeFilterByWeight() and vertexFilterByCentrality()
so that ed.value() mutations are well-defined.
Also fix debug log typo in edgeClickedSet(): reverse tie target was
logged as v2->v2 instead of v2->v1.
Refs #210
commit 483455ac6fcb0888c181d7d22b25f47582f0ba30
Author: Dimitris Kalamaras <dimitris.kalamaras@gmail.com>
Date: Fri Mar 27 18:24:57 2026 +0200
docs | minor
commit 94f987630c6e08708d3a78966097933cd683b1b8
Author: Dimitris Kalamaras <dimitris.kalamaras@gmail.com>
Date: Fri Mar 27 17:26:39 2026 +0200
docs | updated WS9 "Scope" section
commit 3349999321e2c141d1064f9d457cde4605c89701
Author: Dimitris Kalamaras <dimitris.kalamaras@gmail.com>
Date: Fri Mar 27 01:05:16 2026 +0200
[docs] introduce WS9 graph exploration roadmap and align architectural direction
- add roadmap_graph_exploration.md (WS9: filtering, subgraphs, data workflows)
- rewrite ARCHITECTURAL_REFACTORING_ROADMAP.md to be forward-looking (remove historical verbosity)
- update README_DEVELOPER_NOTES.md to reflect WS9 as primary workstream
- reposition WS6 as supporting regression/CI layer
This establishes a clear product + architecture direction:
WS9 drives user-facing capabilities while WS6 ensures regression safety.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/s/socnetv.png){kind=link}