-
Notifications
You must be signed in to change notification settings - Fork 3
IITM: extend n-fold azimuthal FFT acceleration to generic complex types #12
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
Does Arblib.jl version 1.0.0 provide anArblib.precisionfunction that accepts an Acb argument and returns the working precision in bits?💡 Result:
Arblib.jl version 1.0.0 does not provide a function named
Arblib.precisionthat specifically accepts anAcbargument to return its working precision in bits [1][2][3]. WhileArblib.jluses Julia'sprecisionfunction in some contexts—typically viaBase.precisionfor types or by accessing aprecisionfield within its Julia structs (likeArbandAcb)—it does not expose an exportedArblib.precisionmethod for this purpose [1][4][3]. InArblib.jl, Julia structs such asArbandAcbcontain aprecisionfield that stores the precision used by that specific object [1][4][3]. You can typically access this field directly on an instance (e.g.,my_acb.precision). Furthermore,Arblibfollows a naming convention where many Arb C-library functions are wrapped and "Juliafied," often mapping to keyword arguments (likeprec) rather than dedicated precision-querying functions [1][3]. For querying precision related to the underlying Arb/FLINT library, users may also rely on C-level functions likeacb_bitsif accessing low-level wrappers [5][6].Citations:
Fix possible API mismatch in
Arblib.precision(s.m)forAcb(src/IITM/nfold.jl:49-52)When
CT === Acb, the code callsArblib.precision(s.m); Arblib.jl v1.0.0 sources indicate there isn’t anArblib.precision(::Acb)API, so this can throw aMethodError. Use the correct Arblib precision accessor forAcb(e.g., the precision stored on theAcbobject) instead.🤖 Prompt for AI Agents