Dear David,
the page you mentioned is just meant to give examples of how to write
and format a change log entry. We have no plans to reimplement Fast
Downward in another language as this would be a massive project with
unclear benefits.
Currently, writing files to disk and then calling the planner is a
reasonable way of using Fast Downward if you don't want to implement
your own interface for calling Fast Downward's C++ code. In some cases
it could make sense to skip the translation of PDDL to SAS^+ and write
the translator output format directly:
https://www.fast-downward.org/TranslatorOutputFormat. This way, you
could call the search component directly and skip the Python driver
code. If file I/O is a bottleneck, you can also pass the contents of
this file directly to the input stream of the search component (creating
it only in memory without writing it disk).
Cheers
Florian
> of Fast Downward wasreimplemented in C# in late 2019. Is that correct?
> Github reports the project is 75% Python and 25% C++ with no C#. When my
> own C# applications require planning, I've always written PDDL files to
> disk and then called FD on those files through an OS-level
> (command-line-like) call. Is any closer relationship possible?
>
> -david
>
> --
> You received this message because you are subscribed to the Google
> Groups "Fast Downward" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
fast-downwar...@googlegroups.com
> <mailto:
fast-downwar...@googlegroups.com>.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/fast-downward/293f4adb-05c7-4648-af3c-d6e3465261f5n%40googlegroups.com
> <
https://groups.google.com/d/msgid/fast-downward/293f4adb-05c7-4648-af3c-d6e3465261f5n%40googlegroups.com?utm_medium=email&utm_source=footer>.