-
Notifications
You must be signed in to change notification settings - Fork 15
RevitComparisonConfig.NumericTolerance overridden #1200
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
Conversation
@BHoMBot check required |
@pawelbaran to confirm, the following checks are now queued:
There are 9 requests in the queue ahead of you. |
BHoM/Revit_Toolkit#1200 introduced a new default value for tolerance, so the default number of differences for the same objects dataset changed.
@pawelbaran just to let you know, I have provided a |
@pawelbaran just to let you know, I have provided a |
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.
This PR was tested with the DiffingTests_Prototypes toolkit. No errors were reported by it.
All scripts are bound to keep working as before, with the exception that the results returned by the RevitDiffing (on the same couples of input object sets) may be different because of this PR.
This approach is the preferred one when modifying default values for ComparisonConfigs (and finally a good use case for virtual
/override
)! 😄
@pawelbaran to confirm, the following checks are now queued:
|
@BHoMBot check ready-to-merge |
@pawelbaran to confirm, the following checks are now queued:
There are 7 requests in the queue ahead of you. |
FAO: @FraserGreenroyd The check they wish to have dispensation on is ready-to-merge. If you are providing dispensation on this occasion, please reply with:
|
@BHoMBot this is a DevOps instruction. I am authorising dispensation to be granted on check ref. 6225050990 |
@FraserGreenroyd I have now provided a passing check on reference |
Issues addressed by this PR
Closes #1199
Test files
Invoke the RevitDiffing tests in DiffingTests_Prototypes . They should all pass.
Changelog
1e-6
instead ofDouble.MaxValue
. This will affect every Diffing done with RevitDiffing from now on. Comparisons on the same sets of objects done previously with RevitDiffing will return different results after this PR, if the default tolerance of was used. To replicate the same results as before, setDouble.MaxValue
manually on the NumericTolerance property of the RevitComparisonConfig before triggering the RevitDiffing.Additional comments