Last modified by adavison on 2022/10/04 13:53

From version 32.1
edited by shailesh
on 2021/10/11 10:20
Change comment: There is no comment for this version
To version 37.1
edited by shailesh
on 2021/10/13 12:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -96,7 +96,7 @@
96 96  (% class="box infomessage" %)
97 97  (((
98 98  **Screencast** - file explorer
99 -\\(% style="color:#000000" %)<< show directory contents; especially lib/python3.9/site-packages >>
99 +\\(% style="color:#000000" %)<< show directory contents; especially lib/python3.8/site-packages >>
100 100  )))
101 101  
102 102  As you see here, only a limited number of basic packages have currently been installed in this virtual environment. In the steps ahead, we shall install various other packages, and you shall see that these would be reflected here.
... ... @@ -139,7 +139,7 @@
139 139  (% class="box infomessage" %)
140 140  (((
141 141  **Screencast** - file explorer
142 -\\(% style="color:#000000" %)<< show directory contents lib/python3.9/site-packages >>
142 +\\(% style="color:#000000" %)<< show directory contents lib/python3.8/site-packages >>
143 143  )))
144 144  
145 145  To confirm that we have properly installed Brian 2 on our computer, we can test as follows:
... ... @@ -231,9 +231,15 @@
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 +(% class="box warningmessage" %)
238 +(((
239 +**Note:**
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 +)))
242 +
237 237  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:
238 238  
239 239  (% class="box infomessage" %)
... ... @@ -248,7 +248,7 @@
248 248  (% style="color:#000000" %)sim.end()
249 249  )))
250 250  
251 -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:
252 252  
253 253  (% class="box infomessage" %)
254 254  (((