-
Notifications
You must be signed in to change notification settings - Fork 361
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
Change 12a43badc70bf5f4ea77b14b5044250c5ac16a76 from May 2 broke Julia #5384
Comments
OK, so a couple of things:
Thoughts on this, @seisman and @meghanrjones? |
The detection problem here was that I didn't have this test in my test suites, or only tested that the GMT syntax is well generated. The culprit was this in change in
|
PyGMT runs its full tests with GMT master branch nightly, so any GMT API problems should be detected by PyGMT tests (if there are covered) in a few days. |
Please check if the revert (which was one line only) negatively affects the pyGMT examples. |
Yes, scripts in GenericMappingTools/pygmt#1313 now break. |
@joa-quim let me know please. |
I am passing a GMTdataset. It works if I only pass the matrix. You can reproduce it in Matlab. This crashes Matlab (if using
|
But even Matrices have problems. This should plot bars with error-bars and what is passed in is 5x3 matrix
The generated command is
No crash but 0-error bars |
I think I will make a test*.c example to do some more testing on -i and passing various things in. |
And @seisman, I think PyGMT uses mostly GMT_VECTOR when passing in datasets and GMT_MATRIX when passing in grids, or do you mix it up? |
I think PyGMT doesn't use GMT_VECTOR and GMT_MATRIX together. |
I meant across all PyGMT modules you do use both methods for passing data into GMT. not mixing, but one modules may use VECTOR and another may use MATRIX. |
Yes. |
Maybe I was wrong. For example, in PyGMT, the |
Can you check this again - should work fine after the fix. if so please close. |
It's fine ... and closed. |
This now crashes
Very likely it's because it can't handle the -i0-1,1 anymore. The crash is indeed caused when it tries to access a 3rd column in data that has only 2 columns
The text was updated successfully, but these errors were encountered: