Merged
Conversation
Collaborator
ismael-mendoza
left a comment
There was a problem hiding this comment.
preliminary comments
ismael-mendoza
requested changes
May 23, 2023
Collaborator
ismael-mendoza
left a comment
There was a problem hiding this comment.
Seems like there are several places where jitting will break
Collaborator
|
Facing this problem with the I guess we need to discuss how we want to allow the Image object to be vectorized. |
Collaborator
ToDo:
Questions
|
ismael-mendoza
approved these changes
Jun 20, 2023
Collaborator
ismael-mendoza
left a comment
There was a problem hiding this comment.
Tests are passing, see if CI runs ?
This file contains hidden or 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.
This PR should be rebased on main once #15 is merged, it adds an implementation of galsim.Image.
There are some questions about this though. galsim.Image are mutable objects, which really does not play nicely with JAX, it is simply not possible to assign values to array in jax without making a copy. We can follow the galsim API, but the behavior will be different, it won't be possible to assign values to a view of a larger image.
In particular, we cannot do the following in Jax-GalSim:
This would not update the original
im.This will become even sharper of a question when we go to the next PR, which implements drawing functions.
Already here, there is a question of whether we want to make all Image immutable explicitly, whether we want to allow this sort of things:
these are examples of bad OO patterns that do not play nicely at all with the JAX functional spirit, but if we remove them, we break the GalSim API....