The flag for the number of operations used to construct AVL trees or binary search trees (-l) seems to be ignored. The actual number of operations used is always random, even though the task descriptions state:
The flag -l specifies how many operations should be performed on the tree for generated instances
Steps to reproduce in a bash (commands output the number of actual operations generated):
For AVL-Tree:
java -jar exercisegenerator.jar -a avltree -l 6 -t /dev/null | grep '\\item' | wc -l
For Binary Search Tree:
java -jar exercisegenerator.jar -a binsearchtree -l 6 -t /dev/null | grep '\\item' | wc -l
Expected output: 6
Actual output: Random
Furthermore, it can happen that no operations are generated at all, e.g. the commands output 0.
The flag for the number of operations used to construct AVL trees or binary search trees (-l) seems to be ignored. The actual number of operations used is always random, even though the task descriptions state:
The flag -l specifies how many operations should be performed on the tree for generated instances
Steps to reproduce in a bash (commands output the number of actual operations generated):
For AVL-Tree:
For Binary Search Tree:
Expected output:
6Actual output: Random
Furthermore, it can happen that no operations are generated at all, e.g. the commands output
0.