pep8speaks
commented
5 years ago Hello @martinschwinzerl! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:
- In the file
pysixtrack/particles.py:
Line 27:25: E261 at least two spaces before inline comment Line 27:26: E262 inline comment should start with '# ' Line 27:80: E501 line too long (105 > 79 characters)
- In the file
pysixtrack/track.py:
Line 197:1: E303 too many blank lines (3) Line 198:14: E221 multiple spaces before operator Line 198:21: E201 whitespace after '(' Line 199:72: E202 whitespace before ')' Line 200:14: E221 multiple spaces before operator Line 200:21: E201 whitespace after '(' Line 200:56: E202 whitespace before ')' Line 201:21: E201 whitespace after '(' Line 201:48: E202 whitespace before ')' Line 203:16: E201 whitespace after '(' Line 203:31: E202 whitespace before ')' Line 206:14: E127 continuation line over-indented for visual indent Line 206:19: E201 whitespace after '(' Line 206:67: E202 whitespace before ')' Line 207:16: E201 whitespace after '(' Line 207:37: E202 whitespace before ')' Line 211:13: E125 continuation line with same indent as next logical line Line 221:15: E271 multiple spaces after keyword Line 226:15: E201 whitespace after '(' Line 226:30: E202 whitespace before ')' Line 355:1: W391 blank line at end of file
rdemaria
martinschwinzerl
Provides a placeholder BeamMonitor beam-element. The element does not perform any actual output (this has to be implemented yet; the track() member just consists of a single call to "pass") but allows to use the same lattice in both pysixtrack and pysixtracklib
Updates the proton mass to the value referenced in the PDG booklet of 2018. This fixes differences exceeding the numerical threshold 1e.14 between unit-test resultsof pysixtracklib and pysixtrack