Ticket #27 (new defect)
About Conductances lists and ouputs format in pyNN
| Reported by: | pierre | Owned by: | |
|---|---|---|---|
| Priority: | blocker | Milestone: | 0.2 |
| Component: | signals | Version: | trunk |
| Keywords: | Cc: |
Description
What should we do with a conductance file ? I mean, the fact that we have both exc and inh conductances (and it will maybe be the case also latter with the currents) should maybe let the load_conductancelist function to return 2 AnalogSignalList?, no ? gexc, ginh = load(myfile, 'c')
And also, the format saved by pyNN (with or without time in those files should be discussed, because having a proper NeuroTools package which is working properly may need to fix some issue in pyNN (padding and eventually this time column))
Now, due to the padding, a population recorded in pyNN will not always be loadable by NeuroTools because the header (first_id, last_id) will be wrong (if several populations). So either I change the header informations written by pyNN (first_id = 0, last_id = len(population)) and this seems to be the simplest things to do that won't affect the work of anybody, either we remove the padding.
