Bundled WASM does not allow one to compute answer sets with config.json

[matthiasknorr]

I found this problem when being pointed to it by students: essentially when I use the computation with config.json with the option of using clingo from the path, it works just fine. When I use it with the embedded WASM, the .lp file itself is not found (Error File not found: followed by the file name). It shows correctly the config.options from the config.json (in the ASP window), but that's it. Can you please check?

Thank you in advance.

[CaptainUnbrauchbar]

Hello, thanks for reporting the issue!
We're currently trying to reproduce the issue but have issues finding the problem you're describing. Would it be possible for you to share the used config and the content of the associated file so we can find the issue on our end if it still persists?

As a quick explanation, the "addtionalFiles" config option is usually used to seperate logic constraints and the problem instance itself so you can run clingo from the main file containing all of the constraints and have different instances or input values in seperate files and - attach - them like this. Maybe the option was used in a non intended way?

Let us know if you have any questions, we're currently working on some more improvements for the extension we hope that also helps at some point!

Best Regards 💯

[matthiasknorr]

Hi,

Thanks for reply, and sorry for the somewhat imprecise problem specification. I have checked and with a non-modified config.json this actually works. But if I add to args a constant instantiation, it does not, so the problem would result from that. More concisely, I tried both ways (-c n=1 and --const n=1 for a suitable program with #const n declared), and it does work when using clingo from path, and it ceases to work with when unticking this box in the settings.

[CaptainUnbrauchbar]

Good find and thanks for reporting!

We found the problem and will try to make a new release until tomorrow!
You should then be able to add a new optional "constants" argument to your config and specify constants this way.

An example for this would be:

"constants": ["n=3", "x=4*3+2"] will be converted to --const n=3 --const x=4*3+2

Generating a new config also works of course. This new config handling is fully backwards compatible of course. We also fixed the way customArgs is processed so this use case also works properly now:

"customArgs": "--const a=3 -c x=3" will be carried over as --const a=3 -c x=3

... and will work as intended!

Thanks for using our extension and for your contribution 😄