Hi Laura,
the method is called "dump_landmarks", you were close. :-) If you set
the log level to "debug", it will be called; "verbose" is not enough.
Here is an example (not a good configuration, just to illustrate the
dumping):
./fast-downward.py DOMAIN.PDDL PROBLEM.PDDL \
--evaluator \
"h=lmcount(lm_factory=lm_reasonable_orders_hps(lm_rhw(),verbosity=debug))" \
--search "lazy_greedy([h])"
It prints the landmarks and orderings in graphviz format, but
unfortunately it doesn't print the achievers, so it's not in the form of
disjunctive action landmarks. But perhaps it's a useful starting point?
You'll find the code easily by grepping for "dump_landmarks".
I should also point out that the lmcut heuristic is based on disjunctive
action landmarks (recomputed for every state), but doesn't use the
landmark factory framework of the code at all. It doesn't have a way of
printing the landmarks, but it should not be too difficult to add one.
Perhaps it could be useful to do this via the lmcut_constraints()
constraint generator for the operator-counting heuristic rather than
within the lmcut code itself, or perhaps not. Florian might have some
more advice on this.
Let us know if you have any followup questions.
Best,
Malte