Workflow dispatch inputs are strings, although they are called boolean. 🙃

If gh fixes this, the publish workflow will break again, so keep an eye on this.
Refer to ec545c6

And see issue: actions/runner#1483

Simply highlight the node

It right now says Stable Models which is stupid in some cases.
Write Facts/Partial Model/Stable Model instead.

Steps to reproduce

Draw a program such that a node contains more symbols that it's possible to display and the ... get's shown. Then, toggle "show all" in the settings menu.

Expected behaviour

The ... disappear if the symbols now fit.

Actual behaviour:

The ... do not disappear, although there would be enough space for the symbols now.

c+p How to build your own ASP system?

import sys
from clingo.application import clingo_main, Application
from clingo.script import enable_python

enable_python()
class App(Application):
  def main(self, ctl, files):
    for path in files:
      ctl.load(path)
      if not files:
        ctl.load("-")
    ctl.ground([("base", [])])
    ctl.solve()

if __name__ == "__main__":
  clingo_main(App(), sys.argv[1:])

The program displayed is not updating sometimes

Steps to reproduce

Start viasp (viasp &)
Run any program using quickstart.py
Change the program to {r}.
Run again

Expected behaviour

graph for {r}. is shown

Actual behaviour

The graph for the previous program is shown

Maybe the program database doesn't get cleared correctly?

Maybe as entry point

Should look sth like this:

import sys
import clingo

options = ["0"]

ctl = clingo.Control(options)

for path in sys.argv[1:]:
  ctl.load(path)
if not sys.argv[1:]:
  ctl.load("-")
ctl.ground([("base", [])])

with ctl.solve(yield_=True) as handle:
  for m in handle: print("Answer:\n{}".format(m))
  print(handle.get())

$ echo "{a(1..2)}." | python minimal_clingo_input_files.py
Answer:

Answer:
a(2)
Answer:
a(1)
Answer:
a(1) a(2)
SAT

See https://github.com/glaserL/viasp/runs/4650515503?check_suite_focus=true
for the log

Right now, #show statements are simply ignored.
It might be helpful if they would somehow be stored and passed to the frontend to have them as active filters from the beginning.

Steps to reproduce

Set program to

a(1). a(2).
b(X) :- a(X).
{c(X)} :- b(X).
{d(X)} :- c(X).
{e(X)} :- d(X).

#Expected behaviour
The edges don't overlap

Actual behaviour

Some edges overlap unnecessarily

E.g.

app.layout = html.Div([
    viasp_dash.ViaspDash(
        id="myID",
        backend_url="foobar.com:port"
    ),
    html.Div(id='output')
])

Steps to reproduce

1. Start the frontend with a bad backend url.
2. Set the backend url to the correct one.

Expected behaviour

Everything gets redrawn.

Actual behaviour

Everything gets redrawn but the fact node.

Fix after #43

Somehow the rules aren't split correctly here.

Program

c :- not b; a.b :- not c; a.

Result

• Make the search bar wider
• Active filters should be same width as search bar with out the useless padding
• Suggestions should either have some container or not be wider than search bar

Try

{rain, sprinkler}.
wet:- rain.
wet:- sprinkler.

Looking at you GraphDataBaseKEKL

Try

{rain; sprinkler} 1.
wet :- rain.
wet :- sprinkler.

Signature filter applies for each model.

do not filter results in general

Remove the bandage on top and draw a node instead

Hi @glaserL,

a lot has happened to viASP since you last worked on it and I want to give you a little update. I also have a request in regards to publishing.

I recently finished my master's thesis on the project where I added features and made it easier to use overall. At this stage, Javier and I decided to move the repository (my fork of viasp) to the potassco organization. You can try out the current version on binder: https://mybinder.org/v2/gh/potassco/viasp/main?filepath=examples%2FIntroduction%20to%20viASP.ipynb.

Now we would like to publish the current version to pypi. Since you are the owner of the three viasp packages (viasp, viasp-dash, viasp-backend) on pypi.org, there are a couple of options on how to update those from the new repository location:

• You add me as a collaborator (owner) on the pypi project page, so I can manage the publishing (this option would be the least involved for you)
• You send me the API tokens, so that I can define the secrets in the github repo
• I ask Javier to give you the permissions to administer the potassco repo and you set the API secrets yourself

You can choose any of these three ways and I will let you know any infos you need to finish it.

I hope to hear back from you soon!

Best,
Stephan