Untested binaries

[dkfellows]

The following sPyNNaker binaries should be at least minimally tested (do they run?), at least in an overnight test:

• IF_cond_exp_stdp_mad_nearest_pair_additive.aplx
• IF_cond_exp_stdp_mad_nearest_pair_additive_structural_last_neuron_distance_weight.aplx
• IF_cond_exp_stdp_mad_pair_additive_structural_last_neuron_distance_weight.aplx
• IF_cond_exp_stdp_mad_pair_additive_structural_random_distance_weight.aplx
• IF_cond_exp_structural_last_neuron_distance_weight.aplx
• IF_curr_alpha_stdp_mad_pair_additive.aplx
• IF_curr_exp_ca2_adaptive_stdp_mad_pair_additive.aplx
• IF_curr_exp_stdp_mad_nearest_pair_multiplicative.aplx
• IF_curr_exp_stdp_mad_pair_multiplicative.aplx
• IF_curr_exp_stdp_mad_recurrent_pre_stochastic_multiplicative.aplx
• IZK_cond_exp.aplx
• IZK_cond_exp_stdp_mad_pair_additive.aplx
• IZK_curr_exp_stdp_mad_pair_additive.aplx

The following SpiNNFrontEndCommon binaries should be tested, at least in an overnight test:

• spinn_front_end_common/common_model_binaries/bit_field_compressor.aplx

^{This information was obtained from the Report stage of the any Jenkins job.}

[alan-stokes]

spinn_front_end_common/common_model_binaries/bit_field_compressor.aplx is a fail. coz its a abstract for the 2 below (pair vs mundy) I dont think its actually a binary that we can use. but i might be wrong there.

[dkfellows]

If it can't work, why keep it?

(Please, anyone working on this check off the list once you've done something to fix the testing of these binaries.)

[Christian-B]

@andrewgait commented "I got some scripts from Peter a while back that deal with the four "structural" binaries"

@andrewgait commented "The other two binaries in there I would suggest we should probably turn off the builds of them for now"