You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Stefano Spezia: Check correctness from inside the editor.
Jamie Morken: When an A number has no Loda program, maybe the oeis bfile could be downloaded by the web editor to plot terms from there (since the tooltips are useful in general too).
Simon Strandgaard: Compare with b-file data. When developing a program, it would be nice to be able to compare the terms
with the actual b-file. Being able to see the computed terms vs. the expected terms.
Actual
It's possible to use loda check from command line.
However as of 30 dec 2021, there is no way to check correctness from inside the editor.
Solution
Port the loda check command to the editor.
Do some experimental cross over between the loda check and a plotting the bfile terms.
The text was updated successfully, but these errors were encountered:
Great suggestion. One remark: many sequences have more than 1000 terms in their b-file. The web editor currently supports only up to 1000 terms. Another thing: since there can be many terms, the progress should be shown interactively (like the web editor plots the graph)
Excepted
Stefano Spezia: Check correctness from inside the editor.
Jamie Morken: When an A number has no Loda program, maybe the oeis bfile could be downloaded by the web editor to plot terms from there (since the tooltips are useful in general too).
Simon Strandgaard: Compare with b-file data. When developing a program, it would be nice to be able to compare the terms
with the actual b-file. Being able to see the computed terms vs. the expected terms.
Actual
It's possible to use
loda check
from command line.However as of 30 dec 2021, there is no way to check correctness from inside the editor.
Solution
Port the
loda check
command to the editor.Do some experimental cross over between the
loda check
and a plotting the bfile terms.The text was updated successfully, but these errors were encountered: