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.

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

calculator numerically estimates instead of giving exact value #2240

Open
adam12371 opened this issue Oct 2, 2024 · 4 comments
Open

calculator numerically estimates instead of giving exact value #2240

adam12371 opened this issue Oct 2, 2024 · 4 comments
Assignees

Comments

@adam12371
Copy link

Numworks calculator provides a numerical estimate when integrating

screenshot
screenshot (1)
screenshot (2)

Expected behavior

The answer on the third screenshot should be 0 as k=8 satisfies the original equation and when done on paper it is correct but when checking answers on the calculator it provided a numerical estimate rather than the correct answer

Environment

Simulator version: 23.2.1
calculator version: 23.2.3
happens on the simulator and physical calculator

@alloploha
Copy link

alloploha commented Oct 13, 2024

Analytical solutions for arbitrary integrals are often impossible to obtain. Most integrals do not have closed-form solutions, making numerical methods necessary in many cases.

@adri1numworks
Copy link

Issue is reported internally. I'll keep you updated

@fbeleznay
Copy link

I just came accross a related issue. I wanted to solve the integral equation on the screenshot, but Numworks kept working for minutes without giving any answer. The online emulator simply stopped responding to any input.

screenshot(1)

I tried it with the HP prime emulator, it gave me instantly the solution 0.19384396...

@adri1numworks
Copy link

adri1numworks commented Nov 19, 2024

Update on this issue – Concerning the first comment, we'll try to update our algorithm but there is a chance we cannot better estimate the integral. As mentioned, we estimate integral numerically, hence leading to small errors.

This being said, the last comment from @fbeleznay is a different issue. I created another internal issue to tackle this problem and will keep you updated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants