Skip to content

Does the cross-scale k_s work in the way described in the paper? #2

Description

@Leopold2333

min_total_corss_scale_neighbors = 5 # number

kp=max(kp,min_total_corss_scale_neighbors)

Hi, I'm confused of this min_total_corss_scale_neighbors variable here. If there is 'min_total_corss_scale_neighbors', then what's the meaning of the existence of $k_s$? The paper does not mention about the variable, is there any reason why it would improve performance? If so, it feels like that $k_s$ doesn't consistently act as a constraint.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions