Skip to content

Separating construction of weights matrix and thresholding in reconstructors #271

@sdmccabe

Description

@sdmccabe

As in #174, we should explicitly separate thresholding as a separate behavior in graph reconstruction. The reconstructors should return either complete graphs or weight matrices, that are then thresholded or backboned with a separate .threshold() (or something similar) call.

The advantages of this, from my perspective, are:

  1. the current thresholding behavior is filled with odd defaults and unexpected behavior around kwargs. We did this to make things as simple as possible, but adding the slight additional complexity of requiring two method calls to get a useful graph makes the process much more explicit and predictable.
  2. By being explicit about thresholding as a separate behavior, it sets us up to write more modular (and useful) thresholding and backboning code, perhaps even as another submodule. (netrdb)

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions