Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question about the ISL establish #8

Open
zxm-bupt opened this issue Dec 13, 2023 · 2 comments
Open

Question about the ISL establish #8

zxm-bupt opened this issue Dec 13, 2023 · 2 comments

Comments

@zxm-bupt
Copy link

When orchestrater establishes the intra-orbits ISLs, it will use function "sn_get_down_satellite()" as follow to find the adjacency node.

def sn_get_down_satellite(current_sat_id, current_orbit_id, sat_num):
    if current_sat_id == sat_num - 1:
        return [0, current_orbit_id]
    else:
        return [current_sat_id + 1, current_orbit_id]

And it will use "sn_get right_satellite()" as follow to establish the inter-orbits ISLs.

def sn_get_right_satellite(current_sat_id, current_orbit_id, orbit_num):
    if current_orbit_id == orbit_num - 1:
        return [current_sat_id, 0]
    else:
        return [current_sat_id, current_orbit_id + 1]

I want to know why inter-orbits function will add the current_orbit_id and intra-orbits function will add the current_sat_id. They maybe have been confused.

I think the satellites in same orbit should not have same id.

@yangtaodeng
Copy link
Contributor

Hi, sn_get_down_satellite() is used for intra-orbits ISLs. That's right. And they have the same orbit_id.
It is the same for sn_get_right_satellite(). The adjacent satellites have the same intra_orbit_id ("current_sat_id") but different orbit_id.

@zxm-bupt
Copy link
Author

I understand what you mean. Thank you very much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants