Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Miscellaneous fixes #842

Merged
merged 5 commits into from
Sep 16, 2015
Merged

Miscellaneous fixes #842

merged 5 commits into from
Sep 16, 2015

Conversation

tbekolay
Copy link
Member

These are a small collection of things that I changed while working on the Frontiers paper. The only user facing change, I believe, is the Config.configures change, so it has a changelog entry associated with it.

If any of these things are controversial, I'm happy to spin it into its own PR.

These three add_op calls were all the same, so took it out of the
if statement.
@tbekolay tbekolay added this to the 2.1.0 release milestone Sep 15, 2015
@tbekolay
Copy link
Member Author

FYI I have no idea why TravisCI is borking on the builds for NumPy < 1.9. I made an issue with Conda to see if they have any insight.

@hunse
Copy link
Collaborator

hunse commented Sep 15, 2015

FYI I have no idea why TravisCI is borking on the builds for NumPy < 1.9.

Yeah, they must have changed something on their end. The build also failed for #816 after you squashed it, and it wasn't failing before, so I'm quite sure it's not us.

@hunse
Copy link
Collaborator

hunse commented Sep 15, 2015

Yeah, this all looks good.

@Seanny123
Copy link
Contributor

LGTM too.

Previously this was possible in the `Config` constructor, but not
in `Config.configures`. This change makes it more consistent,
and easier to configure multiple classes on an existing config.
This change can provide a legitimate speedup, since the function call
happens once per timestep. The check should be pretty fast.
Similar to how they're done for NeuronTypes.
@tbekolay
Copy link
Member Author

OK, I amended that commit so it adds things to strings.ipynb, and normalizes the Operator strings quite a bit (28704ec). I also added d8dc25b which includes __repr__s for learning rules that are printed in strings.ipybn while I was at it. I made sure not to add synapes and other things that I know @hunse added in #758 though!

@hunse
Copy link
Collaborator

hunse commented Sep 16, 2015

Looks good! I added a little fix to make the list of operators in strings.ipynb slightly more legible.

Also, you reminded me that learning rule types should also be frozen objects. I forgot to include them in #758.

@hunse
Copy link
Collaborator

hunse commented Sep 16, 2015

If that fixup looks good to you, @tbekolay, I'll merge.

@tbekolay
Copy link
Member Author

Yep, looks good to me!

Now, all Operators accept at `tag` argument which is part of the
string representation.

Also added a few sections to the `strings` notebook to demonstrate
the Signal and Operators string representations, as well as some
methods of comparing two sims by looking at the string representations
of all of the operators.

Also added some labels for unlabelled nodes in networks.
@hunse hunse merged commit 117e04d into master Sep 16, 2015
@hunse hunse deleted the misc-fixes branch September 16, 2015 20:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants