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

correct domain_dimensions in non-fixed block size uniform grid FLASH output #4797

Merged
merged 2 commits into from
Feb 1, 2024

Conversation

acreyes
Copy link
Contributor

@acreyes acreyes commented Jan 31, 2024

PR Summary

In non-fixed block size grids FLASH output the domain is output as a single block, rather than being domain decomposed as is assumed for the fixed block size UG. This PR checks for this case
so that yt correctly determines domain_dimensions.

PR Checklist

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

Copy link

welcome bot commented Jan 31, 2024

Hi! Welcome, and thanks for opening this pull request. We have some guidelines for new pull requests, and soon you'll hear back about the results of our tests and continuous integration checks. Thank you for your contribution!

@neutrinoceros
Copy link
Member

neutrinoceros commented Feb 1, 2024

hi @acreyes , thank you for your contribution !
I don't think we need a new test for it, but could you share with us some additional insight, like a quote from Flash's documentation that references this, or maybe a small sample data file that uses it ?

Failure other than linting are unrelated, so I'm going to auto-format now.

@neutrinoceros
Copy link
Member

pre-commit.ci autofix

@neutrinoceros neutrinoceros added this to the 4.3.1 milestone Feb 1, 2024
@neutrinoceros neutrinoceros added the code frontends Things related to specific frontends label Feb 1, 2024
@acreyes
Copy link
Contributor Author

acreyes commented Feb 1, 2024

From the FLASH users guide:

Hierarchical Data Format (HDF) 5 output. A single HDF5 file is created, with each processor writing its data to the same file simultaneously. All data is written out as one block. This relies on the underlying MPIIO layer in HDF5. This particular implementation only works in non-fixedblocksize mode.

Here's an example of an 8x8 simulation run with 2 mpi ranks in each direction with the non-fixed block size mode in FLASH where I'm plotting a covering_grid using domain_dimensions to illustrate the issue.

nofbs-bug
assuming 1 block per mpi rank used in the simulation
nofbs-fix
checking the total number of blocks

Copy link
Member

@neutrinoceros neutrinoceros left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems ok to me, but I'll give other maintainers a couple days to reply if they wish.

@matthewturk
Copy link
Member

This looks good to me, and I'm happy to defer to this explanation. I'm going to merge. Thank you for your first contribution!

@matthewturk matthewturk closed this Feb 1, 2024
@matthewturk matthewturk reopened this Feb 1, 2024
@matthewturk
Copy link
Member

(sorry I accidentally hit the wrong button)

@matthewturk matthewturk merged commit 6119d78 into yt-project:main Feb 1, 2024
20 of 22 checks passed
Copy link

welcome bot commented Feb 1, 2024

Hooray! Congratulations on your first merged pull request! We hope we keep seeing you around! 🎆

neutrinoceros added a commit that referenced this pull request Feb 7, 2024
…7-on-yt-4.3.x

Backport PR #4797 on branch yt-4.3.x (correct domain_dimensions in non-fixed block size uniform grid FLASH output)
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

4 participants