-
Notifications
You must be signed in to change notification settings - Fork 11
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
adds speed up report #274
adds speed up report #274
Conversation
…a, used in debug when other cores go boom.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good - before merging, can I check that this is OK to do on each run i.e. would you prefer to have an option to disable this report?
good question......... dont see the harm in putting a config param in (par the mounting pile of them). either your welcoem to add it, or itll need to wait till ive finished having my arms deep in data in guts. |
Conflicts: spinn_front_end_common/interface/buffer_management/buffer_manager.py spinn_front_end_common/interface/interface_functions/buffer_manager_creator.py spinn_front_end_common/interface/interface_functions/insert_extra_monitor_vertices_to_graphs.py spinn_front_end_common/utility_models/data_speed_up_packet_gatherer_machine_vertex.py spinn_front_end_common/utility_models/data_speed_up_packete_gatherer_application_vertex.py
Happy enough with that now... |
used for debug when other cores go boom in unsetting the timeouts. this report will be allowing us to determine if the speed up data flowed through the chip.
includes a Spynnaker8 for testing this:
SpiNNakerManchester/sPyNNaker8#111