Wrap GMT_Put_Vector and GMT_Write_Data #74
Merged
Conversation
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
Test only for catastrophic failure, not that the data is actually the correct one. Need GMT_Write_Data for that.
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Used to insert numpy 1d array into a GMT_Dataset and to write the dataset to a file so we can test it.
Limit write_data to output to a file only (no streams). That would be too troublesome going from Python to C and not that useful anyway.
The vectors need to be C contiguous when passed to put_vector. Can't change them inside the method because the array will be garbage collected when the method returns and the memory will be wiped. This must be done by the function calling create_data and put_vector.