Open Hub
Open Hub

 Settings |  Report Duplicate

2
I Use This!
Very Low Activity

News

Analyzed 1 day ago. based on code collected 1 day ago.
Changeset [1234]: Applied Yury's patch to trunk, to prepare for NEST 2.2 (see ticket:240)
Posted almost 13 years ago by apdavison
Applied Yury's patch to trunk, to prepare for NEST 2.2 (see ticket:240)
Changeset [1233]: Applied Yury's patch to 0.7 branch, to prepare for NEST 2.2 (see ...
Posted almost 13 years ago by apdavison
Applied Yury's patch to 0.7 branch, to prepare for NEST 2.2 (see ticket:240)
Changeset [1232]: Added unit tests for `ParameterSpace` class
Posted about 13 years ago by apdavison
Added unit tests for ParameterSpace class
Changeset [1231]: removed the asserts because they were failing when absolutely no spikes ...
Posted about 13 years ago by antolikjan
removed the asserts because they were failing when absolutely no spikes had been recorded
Ticket #243 (In NEST tests, recording_devices accumulate from previous runs causing ...) updated
Posted about 13 years ago by yury
Sorry, I believe that I've got confused by all the patches I had applied on top of the svn version. I think what actually helped was to empty these lists by hand, reload()ing was a nice idea, but, unfortunately, it didn't work for me...
reload_nest_module.2.patch attached to Ticket #243
Posted about 13 years ago by yury
synapse_models_init_stable.patch attached to Ticket #246
Posted about 13 years ago by yury
Ticket #246 (When sim.setup() is called, NEST_SYNAPSE_TYPES are not re-initialized ...) updated
Posted about 13 years ago by yury
Also relevant for 0.7.x.
synapse_models_init.patch attached to Ticket #246
Posted about 13 years ago by yury
Ticket #246 (When sim.setup() is called, NEST_SYNAPSE_TYPES are not re-initialized ...) created
Posted about 13 years ago by yury
Hi Andrew, Some tests are failing with the following symptoms: ====================================================================== ERROR: scenario1a ---------------------------------------------------------------------- Traceback (most recent ... [More] call last): File "/srv/virtualenv/mle/lib/python2.7/site-packages/nose/case.py", line 187, in runTest self.test(*self.arg) File "/home/zaytsev/src/nest/pyNN-trunk/test/system/scenarios.py", line 114, in scenario1a sim.setup(timestep=dt, min_delay=dt, threads=n_threads) File "/srv/virtualenv/mle/lib/python2.7/site-packages/pyNN/nest/__init__.py", line 132, in setup 'max_delay': float(max_delay)}) File "/home/zaytsev/src/nest/nest-10kproject-work/build/results/lib/python2.7/site-packages/nest/hl_api.py", line 402, in SetDefaults sr('/%s exch SetDefaults' % model) File "/home/zaytsev/src/nest/nest-10kproject-work/build/results/lib/python2.7/site-packages/nest/__init__.py", line 119, in catching_sr raise hl_api.NESTError(errorname ' in ' commandname message) NESTError: UnknownModelName in SetDefaults_l_D: /static_synapse_projection_0 is not a known model name. -------------------- >> begin captured logging << -------------------- PyNN: DEBUG: rng_seeds = [37454] --------------------- >> end captured logging << --------------------- This happens, because you don't re-build NEST_SYNAPSE_TYPES after nest.ResetKernel?(), but the latter removes all copied models, so some models from NEST_SYNAPSE_TYPES might become invalid. See the attached patch that fixes the tests for me. I don't know how to fix the problem properly in lines with pyNN architecture, so the patch is just to illustrate the problem and a possible solution. May be related to #243. Z. [Less]