CNV: Assignment 2

In this assignment, you will make modifications to a Topographica model to get experience in building and testing models. You will also write a short research proposal to get experience with locating and understanding scholarly neuroscientific and computational literature, and selecting research topics. The goal is to end the course in a good position to start constructing novel and feasible visual cortex models using Topographica.

You are encouraged to work in pairs of your choosing. Just submit one copy of the assignment, listing your partner, and the mark will be allocated equally to each. It is ok to work together just on Part 1 if you prefer; in that case, one of the pair should submit Part 1, listing both partners, and the other should submit only Part 2 plus a list of the two partners.

Part 1: The role of noise in map development

For this assignment you should again use the copy of Topographica installed in /group/teaching/cnv/topographica.

Part 2: Research Proposal

Prepare a short (1-2 page) essay discussing recently published peer-reviewed work on models of topographic maps or experimental data relevant to topographic map formation or function, and proposing concrete computational experiments that you could do to build upon that work and answer an important outstanding question. It's important to propose a question that can be answered computationally (to demonstrate that you are aware of how models are used), and also to propose something novel and feasible. Models from any source can be discussed, not simply those mentioned in this course. Suggestions on how to write such a proposal are in our Proposal guidelines from the DTC Neuroinformatics Research course, although the marking criteria will be significantly less strict in this course because not all of the students are enrolled in a PhD program.

Submission

Your work must be submitted by 10am on the deadline, Thursday, 3 April, using the submit command on Informatics DICE machines (type man submit for more details). Your work should be in the form of one plain PDF file per problem, plus one .ty file where appropriate, each named as listed below. Late submissions will not be accepted without good reason, and will be penalized according to the standard university policy of 5% penalty per working day or part of a day.

Example of submit command:

submit msc cnv 2 1_1.pdf 1_1.ty 1_2.pdf 1_2.ty 1_3.pdf 1_3.ty 1_4.pdf 1_4.ty 2.pdf

Tips for selecting types of noise to model

Essentially any computation performed by a physical system will involve noise, so in some sense any type of noise is fine to investigate. However, it's especially interesting to consider noise that might actually be serving a functional role, or is surprising in some way. For instance, Finn, Priebe and Ferster (2007) suggest that noise on the input to a V1 neuron can help explain contrast-invariant tuning, while Geisler and Albrecht (1997) argue that the output of V1 neurons includes a surprising amount of multiplicative noise. It would be worthwhile to do a short literature search to see if other specific roles for noise have been proposed, and if so whether they can be tested in the network used for this assignment.

Since adding the noise is easy to try, you could also simply considering trying out lots of different options, and then focusing on the four that seem most interesting or informative.

Note that because this network uses firing-rate neurons, we cannot investigate spike-timing dependent variability directly, only the corresponding variation in average firing rate that results from variable spike times.

Tips for running in batch mode

You can use batch mode to automate various tedious tasks and keep track of things. For instance, the command shown above is equivalent to:
  /group/teaching/cnv/topographica/topographica -a -c "run_batch('asst2.ty',analysis_fn=default_analysis_function,times=[100,1000,2500],default_density=30)" -c "save_snapshot()"
  

This runs the default_analysis_function (defined in topo/commands/basic.py) at each of the specified simulation times. You can copy that function to your own .ty file, change the function's name, and add any code inside it that you want to run repeatedly for the simulation.

Any parameter that you add at the end of the run_batch command, like default_density=30, will be set before running your .ty file, and will be put into the filename of the output directory. You can use this mechanism to keep track of the various configurations that you run. For each parameter you want to control like this, just put in code like locals().get('some_parameter',0.25) wherever the value 0.25 appeared in your .ty file. That way Python will first check if some_parameter has been defined, and if not it will use the value 0.25. See the code for default_density in asst2.ty for an example.

Tips for getting a good mark

Be sure that you provide evidence that you did each part of this assignment. I can only judge what is actually submitted, so you should make sure that the files you submit make it clear that you have done everything, and thought about everything.

Be sure to cite any information that you use that is not from the course material or your own experience. Including such information is encouraged, but it must be properly cited. You can use the CMVC book Bibliography database for citation information for any paper cited in the CMVC text.

Submissions must be in PDF except by prior approval with the instructor. I can be sure to be able to read PDF; others like .doc or .sxw have a certain probability of working properly, but the probability is far from 1.0. Naming the files as I suggest will make my job a lot easier, because I will be able to see exactly what you are submitting for each problem.

Read and follow my list of writing tips.

Last update: assignment2.html,v 1.8 2009/02/23 11:23:41 jbednar Exp


Home : Teaching : Courses : Cnv : 2007-2008 : Coursework 

Informatics Forum, 10 Crichton Street, Edinburgh, EH8 9AB, Scotland, UK
Tel: +44 131 651 5661, Fax: +44 131 651 1426, E-mail: school-office@inf.ed.ac.uk
Please contact our webadmin with any comments or corrections. Logging and Cookies
Unless explicitly stated otherwise, all material is copyright © The University of Edinburgh