added partial support for abritrary precision calculations #4
Conversation
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
All calculation are using the precision given by $RHWorkingPrecision. Currently this only works for IFuns and solving RHPs which solely need Cauchy tansforms over contours consisting of lines or rays. The overhead to support this functionality is about 2% - 3% CPU Time, when using MachinePrecision calcultion.
Owner
|
If there's overhead, maybe this should be in a separate branch? How do I pull this into the branch? Or I guess I can leave it as tauu:workingprecision |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Added the variable $RHWorkingPrecision to set a "WorkingPrecision" for the Package.
So far this setting is only used by IFuns and functions required to solve RHPs,
which solely need Cauchy transforms over contours consisting of lines or rays.
The overhead to support this functionality is about 2% - 3% CPU Time,
when using MachinePrecision calculation.
I'm not really sure if this should be included in the master branch, because it is only an incomplete implementation and not extensively tested. But maybe it's useful for you.