Hi to everyone in the list, I've got three small suggestions which may make sense to add, or at least to discuss: 1) I don't get the point why the RESET test is not a category of modtest but stands for itself alone as "reset". I think it is more intuitive to put it as modtest --reset.

2) Add the "--silent" option to modtest. If one runs a MC simulation the output of of a battery of model tests can become really massive... 3) The same issue corresponds to the "coint" command where no --silent option is available.

On Mon, 23 Jun 2014, Artur T. wrote: > I've got three small suggestions which may make sense to add, or at least > to discuss: > > 1) I don't get the point why the RESET test is not a category of modtest > but stands for itself alone as "reset". I think it is more intuitive to put > it as modtest --reset. I agree it makes sense in principle. The problem is that "modtest" already has tons of options, and it would be tricky to avoid collisions when adding an option for reset in is own right plus the two additional options it takes.

> 2) Add the "--silent" option to modtest. If one runs a MC simulation the > output of of a battery of model tests can become really massive... > > 3) The same issue corresponds to the "coint" command where no --silent > option is available. OK, in CVS you now have the --silent option for both "modtest" and "coint".