-
Notifications
You must be signed in to change notification settings - Fork 370
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
Minor improvement to microcircuit example #2087
Conversation
…umentation accordingly
I have changed the problematic files from #1208 in this PR too. The PBS part was removed and writing the submission file is something the user will have to do own their own. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! I have two small formatting comments, but otherwise it looks good :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
@morales-gregorio Just noticed that GitHub actions complains about some pep8 formatting errors in |
Hi @stinebuu I see all the PEP8 errors refer to line breaks after a binary operator:
Such as:
But all of these happen within parentheses, so python will have no problem interpreting them :/ I would not force a |
@morales-gregorio No, we definitely don't want to introduce line continuation by self.num_neurons = np.round((self.net_dict['full_num_neurons']
* self.net_dict['N_scaling'])).astype(int) When fixing this, make sure you don't leave whitespace at the end of the first line or PEP8 will complain about that ;). |
833daf1
to
0f79037
Compare
Hi! I think all the tests now pass, from my side it can be merged |
@jhnnsnk: friendly ping! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Looks good to me. Thanks, @morales-gregorio, for the improvements (and thanks, @jougs, for the ping)!
As mentioned in #1207 the examples code has already improved significantly and I could only identify one place where a warning would be fitting.
Additionally I spotted one superfluous import.
Best,
Aitor