-
Notifications
You must be signed in to change notification settings - Fork 65
Line duplicate points fix #979
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
Merged
doutriaux1
merged 4 commits into
CDAT:master
from
chaosphere2112:line_duplicate_points_fix
Feb 23, 2015
Merged
Changes from 3 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,23 @@ | ||
| import vcs, os, sys | ||
|
|
||
| x = vcs.init() | ||
|
|
||
| line = x.createline() | ||
| line.x = [[0, .1], [.2, .3], [.4, .5], [.6, .7]] | ||
| line.y = [[0, .1], [.2, .3, .4], [.5], [.6, .7]] | ||
|
|
||
| x.plot(line, bg=1) | ||
|
|
||
| if line.x[0] != [0, .1]: | ||
| print "line.x[0] should be [0, .1]; is %s" % line.x[0] | ||
| sys.exit(-1) | ||
|
|
||
| if line.x[1] != [.2, .3, .3]: | ||
| print 'line.x[1] should be [.2, .3]; is %s' % line.x[1] | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @chaosphere2112 should'nt that line say:
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ah, yeah, good catch. I'll update that. |
||
| sys.exit(-1) | ||
|
|
||
| if line.y[2] != [.5, .5]: | ||
| print "line.y[2] should be [.5, .5]; is %s" % line.y[2] | ||
| sys.exit(-1) | ||
|
|
||
| sys.exit(0) | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
@doutriaux1 This looks like the same issue we had in 46105aa. Can you check the similar functions in this file and make sure they're treating both n and N correctly?
I think this
while len(a) < number_points: a.append(a[-1])bit should just beassert(len(a) == number_points)(or similar failure) here, too, unless this is an expected feature. Otherwise it would likely just mask user mistakes and give unexpected incorrect results.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.
Well I'm open to this, but historically it would pad it for the user with the last value.
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.
Gotcha. As long as it's doing what they'd expect it to!
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.
Oops, and I'd linked the wrong commit earlier -- I meant to point at this one: d8f725a