-
Notifications
You must be signed in to change notification settings - Fork 229
File name input in meca does not accept top comments #2613
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
Comments
👋 Thanks for opening your first issue here! Please make sure you filled out the template with as much detail as possible. You might also want to take a look at our contributing guidelines and code of conduct. |
Sorry, I don't fully understand your issue. Do you mean the following input file doesn't work?
|
Sorry for the late reply. Yes the file you showed works. I meant if you put a comment on top without # then it does not work. Like this:
Of course, is a minor thing and I can either add a # character or simply delete the comment. Still, in the previous version of PyGMT having a top comment without # was not inconvenient. Thanks |
The file you posted should not work with any GMT or PyGMT versions. If it worked, then it's a bug. So closing the issue. |
Description of the problem
Probably this is a minor thing, so sorry for the inconvenience and I hope it was useful for someone like me that is trying to migrate from pure GMT to PyGMT.
I installed PyGMT on Mar 25, 2022. However, I needed to use the meca feature including the option cmap and I realized that this is a recent improvement . Unfortunately, the same code that used to work with the old PyGMT version is not working with the new version unless I remove the top comment from the input file given in spec (using convention = "mt").
Text input file used to be and work:
**The new PyGMT imposes removing the top comments or adding a "#" in front of the comment:
Although the message is a warning the focal mechanisms are not plotted.
Minimal Complete Verifiable Example
Full error message
System information
The text was updated successfully, but these errors were encountered: