Currently, the arguments passed when running the jar is hardcoded. Eventually, we will need support for passing arbitrary arguments.
Maybe not completely arbitrary. But we have issues open for varying the heap size (TeamAmalgam/dashboard#7), specifying the number of threads to use (TeamAmalgam/kodkod#30), and the type of algorithm to use (TeamAmalgam/kodkod#17).
At the minimum, we should support these options.
Also, with arbitrary arguments, it might be a good idea to create a file (that's tarballed) with the exact command used, so we know how much memory was allocated, etc.
Currently, the arguments passed when running the jar is hardcoded. Eventually, we will need support for passing arbitrary arguments.
Maybe not completely arbitrary. But we have issues open for varying the heap size (TeamAmalgam/dashboard#7), specifying the number of threads to use (TeamAmalgam/kodkod#30), and the type of algorithm to use (TeamAmalgam/kodkod#17).
At the minimum, we should support these options.
Also, with arbitrary arguments, it might be a good idea to create a file (that's tarballed) with the exact command used, so we know how much memory was allocated, etc.