Unpack the boxsize as a cosmo_array. #214
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #128
Finally got around to implementing this. It's set up to mimic the way units are applied to header fields.
One thing to consider is whether we're happy with how the non-cosmological case is handled. If the simulation is non-cosmological, then the
scale_factorwill default to 1.0 (because swiftsimio enforces that it exists). Thebox_sizeis then created as acosmo_arraywithcomoving=True, but that's acceptable becausescale_factor=1so it will just silently convert to physical if it ever needs to.If we're not happy with that, then some further introspection will be needed to figure out if the snapshot is non-cosmological.