Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[DOC] getJsonObject float number has difference compared to CPU #1922

Closed
res-life opened this issue Apr 3, 2024 · 1 comment
Closed

[DOC] getJsonObject float number has difference compared to CPU #1922

res-life opened this issue Apr 3, 2024 · 1 comment
Assignees
@thirtiseven
Labels
documentation Improvements or additions to documentation

Comments

@res-life
Copy link
Collaborator

res-life commented Apr 3, 2024

Describe the bug

getJsonObject float number has acceptable difference compared to CPU.
Need to update getJsonObject compatibility doc.

Refer to below examples:

diffs 
cpu: 1.699061985174609E-4
gpu: 1.6990619851746093E-4

diffs 
cpu: 3.7811116603045884E-4,
gpu: 3.781111660304589E-4

diffs 
cpu: 4.590000043095363E-4,
gpu: 4.590000043095362E-4

diffs
cpu: 8.19777772911422E-4,
gpu: 8.197777729114221E-4

diffs
cpu: 2.631111129703598E-4,
gpu: 2.6311111297035975E-4
@res-life res-life added bug Something isn't working ? - Needs Triage labels Apr 3, 2024
@mattahrens mattahrens added documentation Improvements or additions to documentation and removed bug Something isn't working ? - Needs Triage labels Apr 9, 2024
@mattahrens mattahrens changed the title [BUG] getJsonObject float number has difference compared to CPU [DOC] getJsonObject float number has difference compared to CPU Apr 9, 2024
@thirtiseven thirtiseven mentioned this issue Apr 11, 2024
Merged
@thirtiseven
Copy link
Collaborator

Doc updated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@thirtiseven thirtiseven

Labels
documentation Improvements or additions to documentation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mattahrens @thirtiseven @res-life