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

place_application_graph vs FixedLocation #444

Open
Christian-B opened this issue Jul 4, 2022 · 5 comments
Open

place_application_graph vs FixedLocation #444

Christian-B opened this issue Jul 4, 2022 · 5 comments
Assignees
Labels

Comments

@Christian-B
Copy link
Member

Christian-B commented Jul 4, 2022

The place_application_graph does a single pass through all vertices

Therefor if it hits a fixed_location these may already have been taken by another vertex/ same_chip_group

Discussing with @rowleya we decided to leave this until after #436

To replicate edit/ clone
test_application_placer in PACMAN/unittests/operations_tests/placer_algorithms_tests/test_application_placer.py

vertex = make_vertices(app_graph, 10, 1, 1, f"app_vertex{i}")
if i ==55:
for mv in vertex.machine_vertices:
mv.add_constraint(ChipAndCoreConstraint(1, 1)

@Christian-B
Copy link
Member Author

Will require either a sort of the vertices to process or a two pass approach

@Christian-B
Copy link
Member Author

One simplification would be to only allow users to add ChipAndCoreConstraint to the WHOLE Application vertex.

this includes machine_vertices such as GFE ones that that are the ONLy one of their Application_vertex

@Christian-B
Copy link
Member Author

Christian-B commented Sep 1, 2022

The coverage branch unittests/operations_tests/placer_algorithms_tests/test_application_placer.py
Has a Test that raise SkipTest due to this.

@Christian-B Christian-B changed the title place_application_graph vs ChipAndCoreConstraint place_application_graph vs FixedLocation Sep 27, 2022
@Christian-B
Copy link
Member Author

APPEARS TESTED AND WORKING

@Christian-B
Copy link
Member Author

test still skips

@Christian-B Christian-B reopened this Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants