-
Notifications
You must be signed in to change notification settings - Fork 234
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
Having issue with xmeshfem3D command #1768
Comments
I seem to remember similar issues in the past. Does
*
make clean
*
make all
*
running the decomposer again
solve the problem?
…---------------------------------------
Hom Nath Gharti, PhD
Assistant Professor | Digital Earth Scientist
https://www.digitalearthscience.com/
Department of Geological Sciences and Geological Engineering
Miller Hall 314, 36 Union St
Queen’s University
Kingston, ON K7L 3N6, Canada
Queen’s University is situated on traditional
Anishinaabe and Haudenosaunee Territory.<https://www.queensu.ca/encyclopedia/t/traditional-territories>
________________________________
From: Varun Sharma ***@***.***>
Sent: Friday, November 29, 2024 9:52 AM
To: SPECFEM/specfem3d ***@***.***>
Cc: Subscribed ***@***.***>
Subject: [SPECFEM/specfem3d] Having issue with xmeshfem3D command (Issue #1768)
I am having the following problem with the xmeshfem3D. Can anybody suggest what might be the issue?
image.png (view on web)<https://github.com/user-attachments/assets/6912d38a-e814-435f-acf7-3ec3d11b38c8>
—
Reply to this email directly, view it on GitHub<#1768>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABMCQ4S3HSWQHIOZ7ARKHBD2DB5ULAVCNFSM6AAAAABSXIV442VHI2DSMVQWIX3LMV43ASLTON2WKOZSG4YDKMZWGIZDCNQ>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
|
@homnath Issue is resolved there was an error in the interface file |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am having the following problem with the xmeshfem3D. Can anybody suggest what might be the issue?
The text was updated successfully, but these errors were encountered: