We have several open issues regarding grounding and the integration of the ASP models that we already have in the FS planner to do that task (See #15, #16, #17, #19). Just to add to the wishlist, I think when we implement that we should use the opportunity to provide basic reachability-analysis capabilities to the Tarski user. With this I simply mean having some class / methods that are able to tell whether a certain atom is ever reachable from a given state / compute the set of all atoms reachable from a certain state. We don't want to reinvent the wheel here, just adapt the ASP generator code that we already have in a modular manner.
This would probably be restricted to some fragment of FSTRIPS without function symbols, but still useful.
We have several open issues regarding grounding and the integration of the ASP models that we already have in the FS planner to do that task (See #15, #16, #17, #19). Just to add to the wishlist, I think when we implement that we should use the opportunity to provide basic reachability-analysis capabilities to the Tarski user. With this I simply mean having some class / methods that are able to tell whether a certain atom is ever reachable from a given state / compute the set of all atoms reachable from a certain state. We don't want to reinvent the wheel here, just adapt the ASP generator code that we already have in a modular manner. This would probably be restricted to some fragment of FSTRIPS without function symbols, but still useful.