-
Notifications
You must be signed in to change notification settings - Fork 7
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
Comments
Will require either a sort of the vertices to process or a two pass approach |
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 |
The coverage branch unittests/operations_tests/placer_algorithms_tests/test_application_placer.py |
APPEARS TESTED AND WORKING PACMAN/unittests/operations_tests/placer_algorithms_tests/test_application_placer.py Line 113 in ecade56
|
PACMAN/unittests/operations_tests/placer_algorithms_tests/test_application_placer.py Line 113 in f689c54
test still skips |
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)
The text was updated successfully, but these errors were encountered: