Skip to content

Conversation

@ctpelok77
Copy link
Contributor

Moved old kstar to kstar-legacy
Added modern kstar version installation via pip

@ctpelok77 ctpelok77 requested a review from haz May 24, 2025 01:49
Copy link
Contributor

@haz haz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only one minor thing to discuss.

}
],
"call":"{package_name} {domain} {problem} --search '{search_algorithm}'",
"call":"{package_name} -k 10 -q 1.0 -H lmcut {domain} {problem} >> plan",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the only thing that gives me pause. You've moved away all the configuration and hard-coded the cli options. Why not leave it exposed? Would kstar use these as defaults? If not, you could beef up the run shell script to look and set defaults.

The reason it's nice to expose these in the json as args is that it will pre-populate the UI for those settings (online editor, and I think vscode as well). So running kstar from there (hosted on solver.planning.domains), could be configured for the individual user.

@haz haz merged commit d3510b3 into main Jun 5, 2025
1 check passed
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

Successfully merging this pull request may close these issues.

3 participants