-
Notifications
You must be signed in to change notification settings - Fork 9
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
Issue 394 src rcv python #397
base: issue-228-anisotropy
Are you sure you want to change the base?
Conversation
Forgot to add the test to the google_test_discover part
…sity/SPECFEMPP into issue-394-src-rcv-python
Issue 395 - Adds support for reading the sources as a yaml-node
…tations-dict or a stations-file
…ad_receivers function. setup.receivers now just a YAML node
Both Sources and receivers can now be defined from python. see specfempp-py repo. |
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.
LGTM
* specfem::receiver::receiver * object | ||
* | ||
* The receivers are defined in the YAML file as | ||
* |
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.
…le, and not the from a YAML node
…d as either a file or a YAML Node
The recent updates change the |
The updates also include zero-padded filenaming for the plotter output |
Finally I have updated the receivers:
stations: path/to/receiver_file || yaml node
sources:
sources: path/to/source_file || yaml node |
there are a lot of files changed, but it's all |
Description
Pull request for sources and receivers defined through Python.
Issue Number
Closes #394
Checklist
Please make sure to check developer documentation on specfem docs.