Skip to content

Update path rendering criteria to require source/target node availability #203

@napakalas

Description

@napakalas

Revisiting the current rendering logic: examples from keast-4 and keast-8 show inconsistencies due to missing T13 and L6 nodes in the human flatmap.

  • keast-4 is rendered based on minimum-degree node completeness, despite missing source nodes.
  • keast-8 is not rendered due to a missing minimum-degree node, but also lacks target nodes.

Proposal: prioritise availability of phenotype-defined source and target nodes over minimum-degree node checks when determining rendering eligibility.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions