Skip to content

Commit

Permalink
Add link to domain visualizations in IPC docs [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
Maumagnaguagno committed Apr 8, 2024
1 parent 4b9ba7a commit d644be5
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions docs/IPC.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,7 @@ Due to a [limit](https://bugs.ruby-lang.org/issues/16616) in the amount of stack
Some large planning instances require more stack, which is possible with ``export RUBY_THREAD_VM_STACK_SIZE=$(($MEMORY * 512 * 1024))``.
HyperTensioN did not exploit the seed variable provided during the competition, although it is possible that randomizing parts of the planning instance may improve timing in certain domains.
A more detailed explanation is provided in the IPC paper [HyperTensioN: A three-stage compiler for planning](https://ipc2020.hierarchical-task.net/publications/IPC2020Booklet.pdf#page=14) and the extended paper [HyperTensioN and Total-order Forward Decomposition optimizations](https://arxiv.org/pdf/2207.00345.pdf).
The effects of each extension in the domain structures can be visualized online in the [HyperTensioN HTN IPC 2020 Explorer](https://maumagnaguagno.github.io/HyperTensioN_HTN_IPC_2020_Explorer/).

The [plan format output](https://ipc2020.hierarchical-task.net/data/format.pdf) required by the IPC to analyze plan correctness was different from the one used by HyperTensioN.
Some examples and tests expect the original non-IPC output, the reason why it is disabled by default.
Expand Down

0 comments on commit d644be5

Please sign in to comment.