Differences between revisions 68 and 85 (spanning 17 versions)
Revision 68 as of 2018-08-29 10:29:25
Size: 5391
Editor: GabiRoeger
Comment:
Revision 85 as of 2023-07-28 09:55:50
Size: 6640
Editor: MalteHelmert
Comment: avoid wiki links
Deletions are marked like this. Additions are marked like this.
Line 19: Line 19:
 * --(http://issues.fast-downward.org/issue688: replace GlobalOperator* by operator ids in successor generator and for preferred operators (code review, Florian, Jendrik))--  * --(http://issues.fast-downward.org/issue688: replace !GlobalOperator* by operator ids in successor generator and for preferred operators (code review, Florian, Jendrik))--
Line 26: Line 26:
 * --(http://issues.fast-downward.org/issue725: Use OperatorID instead of GlobalOperator* more often (code review, Florian))--
 * --(http://issues.fast-downward.org/issue726: Change StateRegistry::get_successor_state from GlobalOperator to OperatorProxy (code review, Florian))--
 * --(http://issues.fast-downward.org/issue725: Use OperatorID instead of !GlobalOperator* more often (code review, Florian))--
 * --(http://issues.fast-downward.org/issue726: Change !StateRegistry::get_successor_state from !GlobalOperator to !OperatorProxy (code review, Florian))--
Line 33: Line 33:
 * --(http://issues.fast-downward.org/issue700: RootTask class (code review, Florian))--  * --(http://issues.fast-downward.org/issue700: !RootTask class (code review, Florian))--
Line 36: Line 36:
 * http://issues.fast-downward.org/issue731: remove legacy hash functions (analyze experiment results, Jendrik)
 * https://bitbucket.org/malte/autonice/pull-requests/1: Python autonice (code review, Jendrik)
 * http://issues.fast-downward.org/issue749: allow putting plugins into sections in the documentation (code review, Jendrik)
 * http://issues.fast-downward.org/issue740: Make translator output file configurable (code review, Guillem)
 * http://issues.fast-downward.org/issue766: convert Heuristic options to Evaluator (code review, Manuel)
 * http://issues.fast-downward.org/issue774: move axiom evaluator and state packer into task interface (code review, Florian)
 * http://issues.fast-downward.org/issue198: issues when using multiple heuristics (code review, Salomé)
 * http://issues.fast-downward.org/issue786: prepare code base for code from saturated cost partitioning papers (code review, Jendrik)
 * http://issues.fast-downward.org/issue790: fix various minor problems in headers (code review, Jendrik)
 * http://issues.fast-downward.org/issue784: use clearer and/or more consistent parameter names in a few places (code review, Jendrik)
 * http://issues.fast-downward.org/issue791: Use task interface for StateRegistry (code review, Florian)
 * http://issues.fast-downward.org/issue792: Get rid of g_successor_generator (code review, Florian)
 * http://issues.fast-downward.org/issue793: Introduce/collect utility methods for printing proxy objects (code review, Florian)
 * http://issues.fast-downward.org/issue794: Reduce code duplication in axiom evaluator (code review, Florian)
 * http://issues.fast-downward.org/issue802: add support for time limit and computing partial abstractions in general (code review, Silvan)
 * --(http://issues.fast-downward.org/issue731: remove legacy hash functions (analyze experiment results, Jendrik))--
 * --(https://bitbucket.org/malte/autonice/pull-requests/1: Python autonice (code review, Jendrik))--
 * --(http://issues.fast-downward.org/issue749: allow putting plugins into sections in the documentation (code review, Jendrik))--
 * --(http://issues.fast-downward.org/issue740: Make translator output file configurable (code review, Guillem))--
 * --(http://issues.fast-downward.org/issue766: convert Heuristic options to Evaluator (code review, Manuel))--
 * --(http://issues.fast-downward.org/issue774: move axiom evaluator and state packer into task interface (code review, Florian))--
 * --(http://issues.fast-downward.org/issue198: issues when using multiple heuristics (code review, Salomé))--
 * --(http://issues.fast-downward.org/issue786: prepare code base for code from saturated cost partitioning papers (code review, Jendrik))--
 * --(http://issues.fast-downward.org/issue790: fix various minor problems in headers (code review, Jendrik))--
 * --(http://issues.fast-downward.org/issue784: use clearer and/or more consistent parameter names in a few places (code review, Jendrik))--
 * --(http://issues.fast-downward.org/issue791: Use task interface for !StateRegistry (code review, Florian))--
 * --(http://issues.fast-downward.org/issue792: Get rid of g_successor_generator (code review, Florian))--
 * --(http://issues.fast-downward.org/issue793: Introduce/collect utility methods for printing proxy objects (code review, Florian))--
 * --(http://issues.fast-downward.org/issue794: Reduce code duplication in axiom evaluator (code review, Florian))--
 * --(http://issues.fast-downward.org/issue802: add support for time limit and computing partial abstractions in general (code review, Silvan))--
 * --(http://issues.fast-downward.org/issue849: separate merge-and-shrink algorithm from heuristic (code review, Silvan))--
 * --(http://issues.fast-downward.org/issue802: add time limit for merge-and-shrink (review by Florian done, proper printing of time stamps done (cf. discussion @bitbucket), waiting for confirmation to merge/further reviewing if deemed necessary, Silvan))--
 * --(http://issues.fast-downward.org/issue780: add code from saturated cost partitioning papers (think about how to change cost functions in projections, Jendrik))--
 * Discuss changing the interface of !PatternInformation and !PatternCollectionInformation (my current idea is to let these classes own the result of pattern (collection) generators which is then passed onto the user of such generators) http://issues.fast-downward.org/issue911 and http://issues.fast-downward.org/issue906 (Silvan)
 * http://issues.fast-downward.org/issue780: add code from saturated cost partitioning papers (code review, Jendrik)
 * http://issues.fast-downward.org/issue927: M&S: change how locally equivalent labels are represented in transition systems (code review, Silvan)

Review queue

Why a queue and how to use it?

  • The queue is intended as a TODO list for Malte. We hope that it can be a useful tool for Malte to keep track of who wants want and to keep the waiting times reasonably fair.
  • Use the queue for code reviews, discussions and other Fast Downward things that Malte should work on.
  • As of now, the queue is intended to be used by the Basel AI group only. If you think this should be changed, please get in touch.
  • Add new items to the end of the queue. Usually, Malte will work from the front of the queue, but there may be reasons to promote/demote things.
  • There is no need to put everything into the queue. It is intended for things that you would ideally like to get done right now, but that are not terribly urgent.

  • The queue should be easy to use and useful for everyone involved. If it turns out that this is not the case, we should get rid of it again.

The queue

FastDownward: ForDevelopers/ReviewQueue (last edited 2023-07-28 09:55:50 by MalteHelmert)