Running from /tmp/job7639843567867601452.tmp; changing to spinnaker Going back to /tmp/job7639843567867601452.tmp total 16 -rw-rw-r-- 1 spinnaker spinnaker 0 Apr 1 17:28 output_3390108571328537447.txt -rw-rw-r-- 1 spinnaker spinnaker 6998 Apr 1 17:28 run.py -rw-rw-r-- 1 spinnaker spinnaker 7006 Apr 1 17:28 setup.bash 2022-04-01 17:28:42 INFO: Read cfg files: /home/spinnaker/spinnaker/SpiNNFrontEndCommon/spinn_front_end_common/interface/spinnaker.cfg, /home/spinnaker/spinnaker/sPyNNaker/spynnaker/pyNN/spynnaker.cfg, /home/spinnaker/.spynnaker.cfg, ./spynnaker.cfg 2022-04-01 17:28:42 INFO: Will search these locations for binaries: /home/spinnaker/spinnaker/SpiNNFrontEndCommon/spinn_front_end_common/common_model_binaries : /home/spinnaker/spinnaker/sPyNNaker/spynnaker/pyNN/model_binaries 2022-04-01 17:28:42 INFO: Setting time scale factor to 1000. 2022-04-01 17:28:42 INFO: Setting machine time step to 100 micro-seconds. 2022-04-01 17:28:42 INFO: Starting execution process 2022-04-01 17:28:42 INFO: Simulating for 10300 0.1ms timesteps using a hardware timestep of 100000us Adding Splitter selectors where appropriate This_was_a_triumph!_I'm_making_a_note_here_Huge_Success!!!_ It's_hard_to_overstate_my_satisfaction._Aperture_Science___ 2022-04-01 17:28:43 INFO: Time 0:00:00.000388 taken by SpynnakerSplitterSelector Adding delay extensions as required We_do_what_we_must_because_we_can_For_the_good_of_all_of_us Except_the_ones_who_are_dead._But_there's_no_sense_crying__ 2022-04-01 17:28:43 INFO: Time 0:00:00.002419 taken by DelaySupportAdder 2022-04-01 17:28:47 INFO: Time 0:00:04.685670 taken by HBPMaxMachineGenerator Preallocating resources for Extra Monitor support vertices over_every_mistake._You_just_keep_on_trying_till_you_run___ out_of_cake._And_the_science_gets_done._And_you_make_a_neat 2022-04-01 17:28:48 INFO: Time 0:00:00.491237 taken by PreAllocateResourcesForExtraMonitorSupport Partitioning graph vertices gun_for_the_people_are_still_alive._I'm_not_even_angry..... I'm_being_so_sincere_right_now._Even_through_you_broke_my__ Partitioning graph edges heart,_and_killed_me._And_tore_me_to_pieces._And_threw_____ every_piece_into_a_fire._As_they_burned_it_hurt_because____ 2022-04-01 17:28:58 INFO: Time 0:00:10.620339 taken by SpYNNakerSplitterPartitioner 2022-04-01 17:29:03 INFO: Time 0:00:05.048986 taken by HBPAllocator 2022-04-01 17:29:03 INFO: Creating transceiver for 10.11.229.81 2022-04-01 17:29:03 INFO: Working out if machine is booted 2022-04-01 17:29:07 INFO: Attempting to boot machine 2022-04-01 17:29:13 INFO: Found board with version [Version: SC&MP 3.4.1 at SpiNNaker:0:0:0 (built Thu Feb 11 14:36:44 2021)] 2022-04-01 17:29:13 INFO: Machine communication successful 2022-04-01 17:29:13 INFO: Detected a machine on IP address 10.11.229.81 which has 856 cores and 120.0 links 2022-04-01 17:29:13 INFO: Time 0:00:09.949155 taken by MachineGenerator java version "1.8.0_191" Java(TM) SE Runtime Environment (build 1.8.0_191-b12) Java HotSpot(TM) 64-Bit Server VM (build 25.191-b12, mixed mode) Generating partitioner report I_was_so_happy_for_you!_Now,_these_points_of_data_make_a___ beautiful_line._And_we're_out_of_beta._We're_releasing_on__ 2022-04-01 17:29:14 INFO: Time 0:00:00.000638 taken by PartitionerReport 2022-04-01 17:29:14 INFO: Time 0:00:00.000204 taken by NetworkSpecificationReport Allocating virtual identifiers time!_So_I'm_GLaD_I_got_burned!_Think_of_all_the_things_we_ learned!_for_the_people_who_are_still_alive._Go_ahead_and__ 2022-04-01 17:29:14 INFO: Time 0:00:00.000895 taken by MallocBasedChipIDAllocator Inserting extra monitors into graphs leave_me..._I_think_I'd_perfer_to_stay_inside..._Maybe_you_ will_find_someone_else_to_help_you._Maybe_Black_Mesa?_That_ 2022-04-01 17:29:14 INFO: Time 0:00:00.004282 taken by InsertExtraMonitorVerticesToGraphs Writing the board chip report was_a_joke._Ha_Ha._Fat_Chance!_Anyway_this_cake_is_great!__ It's_so_delicious_and_moist!_Look_at_me__still_talking_when 2022-04-01 17:29:14 INFO: Time 0:00:00.000330 taken by BoardChipReport Getting number of keys required by each edge using application graph there's_science_to_do!_When_I_look_out_there,_it_makes_me__ glad_I'm_not_you._I've_experiments_to_run._There_is________ 2022-04-01 17:29:14 INFO: Time 0:00:00.000742 taken by EdgeToNKeysMapper 2022-04-01 17:29:14 INFO: The time scale factor could be reduced to 666.6560000000001 2022-04-01 17:29:14 INFO: Time 0:00:00.000911 taken by LocalTDMABuilder Placing graph vertices via spreading over an entire machine research_to_be_done._On_the_people_who_are_still_alive._And believe_me_I_am_still_alive._I'm_doing_science_and_I'm_____ 2022-04-01 17:29:14 INFO: Time 0:00:00.015680 taken by SpreaderPlacer Inserting edges between vertices which require FR speed up functionality. still_alive._I_feel_fantastic_and_I'm_still_alive._While___ you're_dying_I'll_be_still_alive._And_2022-04-01 17:29:14 INFO: Time 0:00:00.005522 taken by InsertEdgesToExtraMonitorFunctionality Generating routing tables for data in system processes you're_dying_I'll_be_still_alive._And_when_you're_dead_I___ will_be_still_alive......_Still_alive.....Still_alive!!!!!! 2022-04-01 17:29:14 INFO: Time 0:00:00.003032 taken by SystemMulticastRoutingGenerator Generating fixed router routes On_the_farm,_ev'ry_Friday_On_the_farm,_it's_rabbit_pie_day_ So_ev'ry_Friday_that_ever_comes_along_I_get_up_early_and___ 2022-04-01 17:29:14 INFO: Time 0:00:00.000896 taken by FixedRouteRouter Generating placement report sing_this_little_song_Run_rabbit,_run_rabbit,_run,_run,_run Run_rabbit,_run_rabbit,_run,_run,_run_Bang,_bang,_bang,____ Generating placement by core report bang_goes_the_farmer's_gun_Run_rabbit,_run_rabbit,_run,_run ,_run,_run_Run_rabbit,_run_rabbit,_run,_run,_run_Don't_give 2022-04-01 17:29:14 INFO: Time 0:00:00.003899 taken by PlacerReportWithApplicationGraph Routing the_farmer_his_fun,_fun,_fun_He'll_get_by_without_his______ rabbit_pie_So_run_rabbit,_run_rabbit,_run,_run,_run_Run____ 2022-04-01 17:29:14 INFO: Time 0:00:00.083611 taken by NerRouteTrafficAware Discovering tags run,_run,_run_Bang,_bang,_bang,_bang_goes_the_farmer's_gun_ Run_rabbit,_run_rabbit,_run,_run,_run,_run_Run_rabbit,_run_ Allocating tags rabbit,_run,_run,_run_Don't_give_the_farmer_his_fun,_fun,__ fun_He'll_get_by_without_his_rabbit_pie_So_run_rabbit,_run_ 2022-04-01 17:29:14 INFO: Time 0:00:00.001800 taken by BasicTagAllocator Reporting Tags rabbit,_run,_run,_run______________________________________ On_the_farm,_ev'ry_Friday_On_the_farm,_it's_rabbit_pie_day_ 2022-04-01 17:29:14 INFO: Time 0:00:00.000314 taken by TagReport Getting constraints for machine graph So_ev'ry_Friday_that_ever_comes_along_I_get_up_early_and___ sing_this_little_song_Run_rabbit,_run_rabbit,_run,_run,_run 2022-04-01 17:29:14 INFO: Time 0:00:00.003084 taken by ProcessPartitionConstraints Calculating zones Run_rabbit,_run_rabbit,_run,_run,_run_Bang,_bang,_bang,____ bang_goes_the_farmer's_gun_Run_rabbit,_run_rabbit,_run,_run Allocating routing keys ,_run,_run_Run_rabbit,_run_rabbit,_run,_run,_run_Don't_give the_farmer_his_fun,_fun,_fun_He'll_get_by_without_his______ 2022-04-01 17:29:14 INFO: Time 0:00:00.001346 taken by ZonedRoutingInfoAllocator Generating Routing info report rabbit_pie_So_run_rabbit,_run_rabbit,_run,_run,_run_Run____ rabbit,_run_rabbit,_run,_run,_run_Run_rabbit,_run_rabbit,__ 2022-04-01 17:29:14 INFO: Time 0:00:00.001103 taken by routingInfoReports Generating routing tables run,_run,_run_Bang,_bang,_bang,_bang_goes_the_farmer's_gun_ Run_rabbit,_run_rabbit,_run,_run,_run,_run_Run_rabbit,_run_ 2022-04-01 17:29:14 INFO: Time 0:00:00.015482 taken by BasicRoutingTableGenerator 2022-04-01 17:29:14 INFO: Time 0:00:00.011761 taken by RouterCollisionPotentialReport Finding executable start types rabbit,_run,_run,_run_Don't_give_the_farmer_his_fun,_fun,__ fun_He'll_get_by_without_his_rabbit_pie_So_run_rabbit,_run_ 2022-04-01 17:29:14 INFO: Time 0:00:00.001619 taken by LocateExecutableStartType Initialising buffers rabbit,_run,_run,_run______________________________________ On_the_farm,_ev'ry_Friday_On_the_farm,_it's_rabbit_pie_day_ 2022-04-01 17:29:14 INFO: Time 0:00:00.050394 taken by BufferManagerCreator Allocating SDRAM for SDRAM outgoing egde partitions So_ev'ry_Friday_that_ever_comes_along_I_get_up_early_and___ sing_this_little_song_Run_rabbit,_run_rabbit,_run,_run,_run 2022-04-01 17:29:14 INFO: Time 0:00:00.000658 taken by SDRAMOutgoingPartitionAllocator Generating data specifications Run_rabbit,_run_rabbit,_run,_run,_run_Bang,_bang,_bang,____ bang_goes_the_farmer's_gun_Run_rabbit,_run_rabbit,_run,_run 2022-04-01 17:29:18 INFO: Time 0:00:04.597847 taken by SpynnakerDataSpecificationWriter Preparing Routing Tables ,_run,_run_Run_rabbit,_run_rabbit,_run,_run,_run_Don't_give the_farmer_his_fun,_fun,_fun_He'll_get_by_without_his______ 2022-04-01 17:29:19 INFO: Time 0:00:00.110479 taken by RoutingSetup Finding binaries rabbit_pie_So_run_rabbit,_run_rabbit,_run,_run,_run_Run____ rabbit,_run_rabbit,_run,_run,_run_Run_rabbit,_run_rabbit,__ 2022-04-01 17:29:19 INFO: Time 0:00:00.004379 taken by GraphBinaryGatherer Running pair routing table compression on chip run,_run,_run_Bang,_bang,_bang,_bang_goes_the_farmer's_gun_ Run_rabbit,_run_rabbit,_run,_run,_run,_run_Run_rabbit,_run_ 2022-04-01 17:29:22 INFO: Time 0:00:03.492681 taken by PairOnChipRouterCompression Generating Router table report fun_He'll_get_by_without_his_rabbit_pie_So_run_rabbit,_run_ rabbit,_run,_run,_run______________________________________ 2022-04-01 17:29:22 INFO: Time 0:00:00.016283 taken by unCompressedRoutingTableReports loading fixed routes On_the_farm,_ev'ry_Friday_On_the_farm,_it's_rabbit_pie_day_ So_ev'ry_Friday_that_ever_comes_along_I_get_up_early_and___ 2022-04-01 17:29:22 INFO: Time 0:00:00.019208 taken by LoadFixedRoutes Executing data specifications and loading data for system vertices using Java sing_this_little_song_Run_rabbit,_run_rabbit,_run,_run,_run Run_rabbit,_run_rabbit,_run,_run,_run_Bang,_bang,_bang,____ 2022-04-01 17:29:24 INFO: Time 0:00:01.921140 taken by HostExecuteSystemDataSpecification Loading system executables onto the machine bang_goes_the_farmer's_gun_Run_rabbit,_run_rabbit,_run,_run ,_run,_run_Run_rabbit,_run_rabbit,_run,_run,_run_Don't_give 2022-04-01 17:29:30 INFO: Time 0:00:05.882073 taken by LoadSystemExecutableImages 2022-04-01 17:29:30 INFO: Time 0:00:00.001954 taken by TagsFromMachineReport Clearing tags the_farmer_his_fun,_fun,_fun_He'll_get_by_without_his______ rabbit_pie_So_run_rabbit,_run_rabbit,_run,_run,_run_Run____ Loading Tags rabbit,_run_rabbit,_run,_run,_run_Run_rabbit,_run_rabbit,__ run,_run,_run_Bang,_bang,_bang,_bang_goes_the_farmer's_gun_ 2022-04-01 17:29:30 INFO: Time 0:00:00.003215 taken by TagsLoader Executing data specifications and loading data for application vertices using Java Run_rabbit,_run_rabbit,_run,_run,_run,_run_Run_rabbit,_run_ rabbit,_run,_run,_run_Don't_give_the_farmer_his_fun,_fun,__ 2022-04-01 17:29:32 INFO: Time 0:00:01.937167 taken by HostExecuteApplicationDataSpecification Preparing to Expand Synapses fun_He'll_get_by_without_his_rabbit_pie_So_run_rabbit,_run_ rabbit,_run,_run,_run______________________________________ Expanding Synapses On_the_farm,_ev'ry_Friday_On_the_farm,_it's_rabbit_pie_day_ So_ev'ry_Friday_that_ever_comes_along_I_get_up_early_and___ 2022-04-01 17:29:37 INFO: Time 0:00:05.059683 taken by SynapseExpander Running bitfield generation on chip bang_goes_the_farmer's_gun_Run_rabbit,_run_rabbit,_run,_run ,_run,_run_Run_rabbit,_run_rabbit,_run,_run,_run_Don't_give 2022-04-01 17:29:41 INFO: Time 0:00:03.712341 taken by OnChipBitFieldGenerator Finalising Retrieved Connections rabbit,_run_rabbit,_run,_run,_run_Run_rabbit,_run_rabbit,__ run,_run,_run_Bang,_bang,_bang,_bang_goes_the_farmer's_gun_ 2022-04-01 17:29:41 INFO: Time 0:00:00.000723 taken by FinishConnectionHolders Reading Routing Tables from Machine Run_rabbit,_run_rabbit,_run,_run,_run,_run_Run_rabbit,_run_ rabbit,_run,_run,_run_Don't_give_the_farmer_his_fun,_fun,__ 2022-04-01 17:29:41 INFO: Time 0:00:00.594674 taken by ReadRoutingTablesFromMachine Generating compressed router table report fun_He'll_get_by_without_his_rabbit_pie_So_run_rabbit,_run_ rabbit,_run,_run,_run______________________________________ 2022-04-01 17:29:41 INFO: Time 0:00:00.015565 taken by compressedRoutingTableReports Generating comparison of router table report bacon_bacon_bacon_bacon_bacon_bacon_bacon_bacon_bacon_bacon mushroom_mushroom_bacon_bacon_bacon_bacon_bacon_bacon_bacon 2022-04-01 17:29:41 INFO: Time 0:00:00.000897 taken by comparisonOfRoutingTablesReport Generating Routing summary report bacon_bacon_bacon_bacon_bacon_bacon_bacon_bacon_bacon_bacon mushroom_mushroom_bacon_bacon_bacon_bacon_bacon_bacon_bacon 2022-04-01 17:29:41 INFO: Time 0:00:00.003840 taken by CompressedRouterSummaryReport Reading Routing Tables from Machine snake_snake_bacon_bacon_bacon_bacon_bacon_bacon_bacon_bacon bacon_bacon_bacon_bacon_bacon_bacon_bacon_bacon_bacon_bacon 2022-04-01 17:29:41 INFO: Time 0:00:00.015218 taken by RoutingTableFromMachineReport Writing fixed route report mushroom_mushroom_bacon_bacon_bacon_bacon_bacon_bacon_bacon bacon_bacon_bacon_bacon_bacon_bacon_bacon_bacon_bacon_bacon 2022-04-01 17:29:41 INFO: Time 0:00:00.025212 taken by FixedRouteFromMachineReport Loading executables onto the machine mushroom_mushroom_bacon_bacon_bacon_bacon_bacon_bacon_bacon snake_snake_bacon_bacon_bacon_bacon_bacon_bacon_bacon_bacon 2022-04-01 17:29:48 INFO: Time 0:00:07.134566 taken by LoadApplicationExecutableImages 2022-04-01 17:29:48 INFO: Running for 1 steps for a total of 1030.0ms 2022-04-01 17:29:48 INFO: Run 1 of 1 Generating SDRAM usage report bacon_bacon_bacon_bacon_bacon_bacon_bacon_bacon_bacon_bacon mushroom_mushroom_bacon_bacon_bacon_bacon_bacon_bacon_bacon 2022-04-01 17:29:48 INFO: Time 0:00:00.004346 taken by SdramUsageReportPerChip 2022-04-01 17:29:49 INFO: Time 0:00:00.033086 taken by DatabaseInterface 2022-04-01 17:29:49 INFO: ** Notifying external sources that the database is ready for reading ** 2022-04-01 17:29:49 INFO: Time 0:00:00.000761 taken by CreateNotificationProtocol Getting provenance data from machine graph bacon_bacon_bacon_bacon_bacon_bacon_bacon_bacon_bacon_bacon mushroom_mushroom_bacon_bacon_bacon_bacon_bacon_bacon_bacon Getting provenance data from application graph snake_snake_bacon_bacon_bacon_bacon_bacon_bacon_bacon_bacon There_is_a_flower_within_my_heart,_Daisy,_Daisy!_Planted___ 2022-04-01 17:29:49 INFO: Time 0:00:00.004909 taken by GraphProvenanceGatherer Waiting for cores to be either in PAUSED or READY state one_day_by_a_glancing_dart,_Planted_by_Daisy_Bell!_Whether_ she_loves_me_or_loves_me_not,_Sometimes_it's_hard_to_tell;_ Updating run time Yet_I_am_longing_to_share_the_lot_Of_beautiful_Daisy_Bell!_ Daisy,_Daisy,_Give_me_your_answer,_do!_I'm_half_crazy,_All_ 2022-04-01 17:29:49 INFO: Time 0:00:00.025621 taken by ChipRuntimeUpdater 2022-04-01 17:29:49 INFO: *** Running simulation... *** Loading buffers for_the_love_of_you!_It_won't_be_a_stylish_marriage,_I_____ can't_afford_a_carriage,_But_you'll_look_sweet_on_the_seat_ 2022-04-01 17:29:49 INFO: ** Awaiting for a response from an external source to state its ready for the simulation to start ** 2022-04-01 17:29:49 INFO: ** Sending start / resume message to external sources to state the simulation has started or resumed. ** 2022-04-01 17:29:49 INFO: ** Awaiting for a response from an external source to state its ready for the simulation to start ** 2022-04-01 17:29:49 INFO: Application started; waiting 1030.1s for it to stop 2022-04-01 17:46:59 INFO: ** Sending pause / stop message to external sources to state the simulation has been paused or stopped. ** 2022-04-01 17:46:59 INFO: Time 0:17:10.294556 taken by ApplicationRunner clearing IOBUF from the machine Of_a_bicycle_built_for_two!_We_will_go_"tandem"_as_man_and_ wife,_Daisy,_Daisy!_"Ped'ling"_away_down_the_road_of_life,_ 2022-04-01 17:46:59 INFO: Time 0:00:00.004427 taken by ChipIOBufClearer Extracting buffers from the last run I_and_my_Daisy_Bell!_When_the_road's_dark_we_can_both______ despise_P'liceman_and_"lamps"_as_well;_There_are_"bright___ 2022-04-01 17:48:23 INFO: Time 0:01:24.515698 taken by BufferExtractor 2022-04-01 17:48:23 INFO: Time 0:00:00.000178 taken by FinaliseTimingData Getting provenance data will_stand_by_you_in_"wheel"_or_woe,_Daisy,_Daisy!_You'll__ be_the_bell(e)_which_I'll_ring_you_know!_Sweet_little_Daisy 2022-04-01 17:48:23 INFO: Time 0:00:00.061426 taken by PlacementsProvenanceGatherer 2022-04-01 17:48:23 INFO: Time 0:00:00.001355 taken by RedundantPacketCountReport Getting Router Provenance Bell!_You'll_take_the_"lead"_in_each_"trip"_we_take,_Then__ if_I_don't_do_well;_I_will_permit_you_to_use_the_brake,_My_ 2022-04-01 17:48:23 INFO: Time 0:00:00.035294 taken by RouterProvenanceGatherer Getting profile data beautiful_Daisy_Bell!______________________________________ On_the_farm,_ev'ry_Friday_On_the_farm,_it's_rabbit_pie_day_ 2022-04-01 17:48:24 INFO: Time 0:00:00.057501 taken by ProfileDataGatherer Getting spikes for Excitatory_Cells So_ev'ry_Friday_that_ever_comes_along_I_get_up_early_and___ sing_this_little_song_Run_rabbit,_run_rabbit,_run,_run,_run Getting spikes for Inhibitory_Cells Run_rabbit,_run_rabbit,_run,_run,_run_Bang,_bang,_bang,____ bang_goes_the_farmer's_gun_Run_rabbit,_run_rabbit,_run,_run Getting v for Excitatory_Cells ,_run,_run_Run_rabbit,_run_rabbit,_run,_run,_run_Don't_give the_farmer_his_fun,_fun,_fun_He'll_get_by_without_his______ Getting v for Inhibitory_Cells rabbit_pie_So_run_rabbit,_run_rabbit,_run,_run,_run_Run____ rabbit,_run_rabbit,_run,_run,_run_Run_rabbit,_run_rabbit,__ Getting gsyn_exc for Excitatory_Cells run,_run,_run_Bang,_bang,_bang,_bang_goes_the_farmer's_gun_ Run_rabbit,_run_rabbit,_run,_run,_run,_run_Run_rabbit,_run_ 2022-04-01 17:48:33 WARNING: Getting data on a whole population when selective recording is active will result in only the requested neurons being returned in numerical order and without repeats. Getting gsyn_inh for Excitatory_Cells rabbit,_run,_run,_run_Don't_give_the_farmer_his_fun,_fun,__ fun_He'll_get_by_without_his_rabbit_pie_So_run_rabbit,_run_ 2022-04-01 17:48:33 WARNING: The extra monitor on 1, 1 has detected that 5 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 1, 2 has detected that 3 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 1, 3 has detected that 8 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 1, 4 has detected that 24 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 2, 1 has detected that 15 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 2, 2 has detected that 15 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 2, 3 has detected that 4 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 2, 4 has detected that 16 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 2, 5 has detected that 17 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 3, 1 has detected that 22 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 3, 3 has detected that 15 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 3, 4 has detected that 12 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 3, 5 has detected that 1 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 3, 6 has detected that 17 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 4, 1 has detected that 13 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 4, 2 has detected that 12 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 4, 3 has detected that 11 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 4, 4 has detected that 24 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 4, 5 has detected that 6 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 4, 7 has detected that 14 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 5, 3 has detected that 9 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 5, 4 has detected that 8 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 5, 5 has detected that 6 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 5, 6 has detected that 14 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 5, 7 has detected that 11 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 6, 2 has detected that 82 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 6, 4 has detected that 8 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 6, 5 has detected that 16 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 6, 6 has detected that 18 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 6, 7 has detected that 16 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 7, 3 has detected that 19 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 7, 4 has detected that 11 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 7, 5 has detected that 18 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 7, 6 has detected that 21 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. 2022-04-01 17:48:33 WARNING: The extra monitor on 7, 7 has detected that 13 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. Exception in thread HBPJobController: Traceback (most recent call last): File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner self.run() File "/usr/lib/python3.8/threading.py", line 870, in run self._target(*self._args, **self._kwargs) File "/home/spinnaker/spinnaker/SpiNNFrontEndCommon/spinn_front_end_common/abstract_models/impl/machine_allocation_controller.py", line 67, in __manage_allocation self._teardown() File "/home/spinnaker/spinnaker/SpiNNFrontEndCommon/spinn_front_end_common/interface/interface_functions/hbp_allocator.py", line 92, in _teardown self._release(self._machine_name) File "/home/spinnaker/spinnaker/SpiNNFrontEndCommon/spinn_front_end_common/interface/interface_functions/hbp_allocator.py", line 71, in _release r.raise_for_status() File "/home/spinnaker/spinnaker3.8/lib/python3.8/site-packages/requests-2.25.1-py3.8.egg/requests/models.py", line 943, in raise_for_status raise HTTPError(http_error_msg, response=self) requests.exceptions.HTTPError: 500 Server Error: Server Error for url: http://192.168.0.1:9090/services/rest/job/165453/machine?machineName=10.11.229.81 {'inputs': [], 'outputs': [{'output': 'spikes', 'population': 0}, {'output': 'spikes', 'population': 1}, {'output': 'v', 'population': 0}, {'output': 'v', 'population': 1}], 'outputs_sample': [{'output': 'gsyn_exc', 'population': 0, 'sample': 500}, {'output': 'gsyn_inh', 'population': 0, 'sample': 500}], 'populations': {'0': {'cellclass': 'IF_cond_exp', 'cellparams': {'cm': 0.2, 'e_rev_E': 0.0, 'e_rev_I': -80.0, 'i_offset': 0.0, 'tau_m': 20.0, 'tau_refrac': 5.0, 'tau_syn_E': 5.0, 'tau_syn_I': 10.0, 'v_reset': -60.0, 'v_rest': -60.0, 'v_thresh': -50.0}, 'label': 'Excitatory_Cells', 'size': 8000}, '1': {'cellclass': 'IF_cond_exp', 'cellparams': {'cm': 0.2, 'e_rev_E': 0.0, 'e_rev_I': -80.0, 'i_offset': 0.0, 'tau_m': 20.0, 'tau_refrac': 5.0, 'tau_syn_E': 5.0, 'tau_syn_I': 10.0, 'v_reset': -60.0, 'v_rest': -60.0, 'v_thresh': -50.0}, 'label': 'Inhibitory_Cells', 'size': 2000}, '2': {'cellclass': 'SpikeSourcePoisson', 'cellparams': {'duration': 30.0, 'rate': 180.0}, 'label': 'expoisson', 'size': 20}}, 'projections': [{'connector': 'FixedProbabilityConnector', 'connector_params': {'probability': 0.02, 'rng': True}, 'post_syn_pop_id': 0, 'pre_syn_pop_id': 0, 'receptor_type': 'excitatory', 'synapse_params': {'delay': 0.2, 'weight': 0.005880000000000001}, 'synapse_type': 'StaticSynapse'}, {'connector': 'FixedProbabilityConnector', 'connector_params': {'probability': 0.02, 'rng': True}, 'post_syn_pop_id': 1, 'pre_syn_pop_id': 0, 'receptor_type': 'excitatory', 'synapse_params': {'delay': 0.2, 'weight': 0.005880000000000001}, 'synapse_type': 'StaticSynapse'}, {'connector': 'FixedProbabilityConnector', 'connector_params': {'probability': 0.02, 'rng': True}, 'post_syn_pop_id': 0, 'pre_syn_pop_id': 1, 'receptor_type': 'inhibitory', 'synapse_params': {'delay': 0.2, 'weight': 0.07475}, 'synapse_type': 'StaticSynapse'}, {'connector': 'FixedProbabilityConnector', 'connector_params': {'probability': 0.02, 'rng': True}, 'post_syn_pop_id': 1, 'pre_syn_pop_id': 1, 'receptor_type': 'inhibitory', 'synapse_params': {'delay': 0.2, 'weight': 0.07475}, 'synapse_type': 'StaticSynapse'}, {'connector': 'FixedProbabilityConnector', 'connector_params': {'probability': 0.01, 'rng': False}, 'post_syn_pop_id': 0, 'pre_syn_pop_id': 2, 'receptor_type': 'excitatory', 'synapse_params': {'weight': 0.1}, 'synapse_type': 'StaticSynapse'}, {'connector': 'FixedProbabilityConnector', 'connector_params': {'probability': 0.01, 'rng': False}, 'post_syn_pop_id': 1, 'pre_syn_pop_id': 2, 'receptor_type': 'excitatory', 'synapse_params': {'weight': 0.1}, 'synapse_type': 'StaticSynapse'}], 'simulation_settings': {'max_delay': 14.4, 'min_delay': 0.1, 'simulation_length': 1030, 'timestep': 0.1}} ['/home/spinnaker/spinnaker/SpiNNFrontEndCommon/spinn_front_end_common/interface/spinnaker.cfg', '/home/spinnaker/spinnaker/sPyNNaker/spynnaker/pyNN/spynnaker.cfg', '/home/spinnaker/.spynnaker.cfg', './spynnaker.cfg'] These log messages where generated at level WARNING or above Getting data on a whole population when selective recording is active will result in only the requested neurons being returned in numerical order and without repeats. The extra monitor on 1, 1 has detected that 5 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 1, 2 has detected that 3 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 1, 3 has detected that 8 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 1, 4 has detected that 24 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 2, 1 has detected that 15 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 2, 2 has detected that 15 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 2, 3 has detected that 4 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 2, 4 has detected that 16 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 2, 5 has detected that 17 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 3, 1 has detected that 22 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 3, 3 has detected that 15 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 3, 4 has detected that 12 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 3, 5 has detected that 1 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 3, 6 has detected that 17 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 4, 1 has detected that 13 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 4, 2 has detected that 12 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 4, 3 has detected that 11 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 4, 4 has detected that 24 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 4, 5 has detected that 6 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 4, 7 has detected that 14 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 5, 3 has detected that 9 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 5, 4 has detected that 8 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 5, 5 has detected that 6 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 5, 6 has detected that 14 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 5, 7 has detected that 11 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 6, 2 has detected that 82 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 6, 4 has detected that 8 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 6, 5 has detected that 16 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 6, 6 has detected that 18 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 6, 7 has detected that 16 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 7, 3 has detected that 19 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 7, 4 has detected that 11 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 7, 5 has detected that 18 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 7, 6 has detected that 21 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate. The extra monitor on 7, 7 has detected that 13 packets were dumped from a core failing to take the packet. This often occurs when the executable has crashed or has not been given a multicast packet callback. It can also result from the core taking too long to process each packet. These packets were reinjected and so this number is likely a overestimate.