-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Mesh3d cell data checks #3369
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
Merged
Mesh3d cell data checks #3369
Changes from 3 commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
12f3e1f
removed indices convert
archmoj 33e2b9a
if no indices then trace visible to false
archmoj f1772a2
check for vertex data only
archmoj e531e4e
Merge remote-tracking branch 'origin/master' into 2630-mesh3d-dont-mo…
archmoj 65a5806
revised code after 1st review 3369
archmoj e97f5ed
improved condition checks and added jasmine tests for mesh3d
archmoj 55e5e12
added more logic
archmoj 79deeae
revert optional deps
archmoj bf51940
fixed syntax
archmoj 83060bc
using loops instead of map in mesh3d convert
archmoj a041e51
moved certain condition checks to convert step
archmoj 2b54f14
pass 2 removed some extra checks
archmoj a9ab05f
fixed jasmine tests to also check for position and cell data
archmoj ec502ee
improved jasmine tests and -0.49 > 0 round edge case
archmoj fadce01
traceIn > traceOut and more jasmine tests
archmoj 29f5a06
must have tested traceOut after coerce fix
archmoj 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
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.
Hmm. So you didn't move this to
mesh3d/convert.js
? Just 🔪 ing it didn't break any tests?Can you try plotting a mesh3d trace with non-integer indices and see what happens?
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.
@etpinard Thanks for the review.
That's true! One could get bad errors in case of having non-integer ids.
So, in the revised code I added map functions to round the float values to integers.
However; there is now extra logic to check and handle for such cases. A series of jasmine tests are also added to define the expected behaviour in various scenarios.