Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -231,13 +231,13 @@
231	231	(% class="box infomessage" %)
232	232	(((
233	233	**Screencast** - terminal
234		-\\(% style="color:#000000" %)pip install pyNN
	234	+\\(% style="color:#000000" %)pip install PyNN
235	235	)))
236	236
237	237	(% class="box warningmessage" %)
238	238	(((
239	239	**Note:**
240		-\\Note that PyNN project is spelt with a captial P, small y, and two captital N. But the Python module, as seen here, is spelt starting with a small P. This is in line with general Python convention, where package names start with small alphabets.
	240	+\\Note that PyNN project is spelt with a captial P, small y, and two captital N. The pip command is case-insensitive, so you may write it differently here. But the Python module, as we shall see ahead, is case-sensitive and is spelt starting with a small P. This is in line with general Python convention, whereby package names start with small alphabets. Thus, while importing PyNN module via Python, it needs to be written as 'pyNN'.
241	241	)))
242	242
243	243	To verify that PyNN has been successfully installed on our system, and that it is indeed able to communicate with the other simulators that we installed earlier, we can try running:
...	...	@@ -254,7 +254,7 @@
254	254	(% style="color:#000000" %)sim.end()
255	255	)))
256	256
257		-This confirms that PyNN has been properly setup, and also that is able to employ Brian 2. To verify similary test that PyNN is also able to communicate with NEURON and NEST simulators:
	257	+This confirms that PyNN has been properly setup, and also that is able to employ Brian 2. To verify similary that PyNN is also able to communicate with NEURON and NEST simulators:
258	258
259	259	(% class="box infomessage" %)
260	260	(((