Skip to content
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

MAESTROeX uses namespaces for parameters #4347

Merged
merged 2 commits into from
Feb 21, 2023

Conversation

zingale
Copy link
Member

@zingale zingale commented Feb 21, 2023

this fixes the detection of how temperature is defined

PR Summary

PR Checklist

  • New features are documented, with docstrings and narrative docs
  • Adds a test for any bugs fixed. Adds tests for new features.

this fixes the detection of how temperature is defined
@neutrinoceros neutrinoceros added bug code frontends Things related to specific frontends labels Feb 21, 2023
@neutrinoceros
Copy link
Member

Seems pretty straightforward. Does the exact name of this parameter depend on MAESTROeX's version ?

@zingale
Copy link
Member Author

zingale commented Feb 21, 2023

MAESTRO is the old code, written in F90. It is really not used much any more. MAESTROeX is the rewrite in C++, and it uses namespaces for the parameters, hence the change in the parameter name. I don't expect any more changes.

@neutrinoceros
Copy link
Member

Ok, can you add inline comments to indicate what branch is destined to what code ?

@zingale
Copy link
Member Author

zingale commented Feb 21, 2023

Ok, can you add inline comments to indicate what branch is destined to what code ?

done

@neutrinoceros neutrinoceros merged commit 1c75757 into yt-project:main Feb 21, 2023
1 check passed
@neutrinoceros neutrinoceros changed the title MAESTROeX uses namespaces for paramters MAESTROeX uses namespaces for parameters May 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug code frontends Things related to specific frontends
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants