-
Notifications
You must be signed in to change notification settings - Fork 11
included tol limit #339
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
included tol limit #339
Conversation
🧹 Catalogue's Preview Site CleanupThe preview site for this pull request has been cleaned up. If you need a new preview, please reopen the PR or create a new one. |
...hm_catalog/vito/random_forest_firemapping/benchmark_scenarios/random_forest_firemapping.json
Show resolved
Hide resolved
| "job-results.json": "https://s3.waw3-1.cloudferro.com/swift/v1/apex-examples/whittaker/job-results.json" | ||
| }, | ||
| "reference_options": { | ||
| "atol": 0.1 |
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.
any specific reason why atol is prefered over rtol?
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.
no reason a specific reason, I simply followed couple of examples and thought absolute check is preferred. Will update if rtol is preferred one
|
@EmileSonneveld resolved conflit and avoided tolerance in here |
|
Since it has been approved, I will hopefully merge it. Please let me know if you have additional suggestions @HansVRP |
introduced tolerance limit in the benchmark