Remove simulate intro to align with good CLI practices

[J535D165]

No description provided.

[J535D165]

Remove

            _____ _____            _
     /\    / ____|  __ \          (_)
    /  \  | (___ | |__) |_____   ___  _____      __
   / /\ \  \___ \|  _  // _ \ \ / / |/ _ \ \ /\ / /
  / ____ \ ____) | | \ \  __/\ V /| |  __/\ V  V /
 /_/    \_\_____/|_|  \_\___| \_/ |_|\___| \_/\_/

---------------------------------------------------------------------------------
|                                                                                |
|  Welcome to ASReview LAB - AI-assisted systematic reviews software.            |
|  In simulation mode the computer will simulate how well ASReview LAB           |
|  could have accelerate the systematic review of your dataset.                  |
|  You can sit back and relax while the computer runs this simulation.           |
|                                                                                |
|  GitHub page:        https://github.com/asreview/asreview                      |
|  Questions/remarks:  asreview@uu.nl                                            |
|                                                                                |
---------------------------------------------------------------------------------

[jteijema]

I support this removal, but that doesn't say I won't miss the intro.

[jspaaks]

Out of interest, why was this considered a bad practice?

[J535D165]

It's opinionated, of course :) In large-scale simulation studies, this is overwhelming. Some guidelines I think that might apply:

Display output on success, but keep it brief. Traditionally, when nothing is wrong, UNIX commands display no output to the user. This makes sense when they’re being used in scripts, but can make commands appear to be hanging or broken when used by humans. For example, cp will not print anything, even if it takes a long time. (https://clig.dev/#output)

Reducing cognitive load is necessary for making an accessible product. (https://primer.style/cli/)

Also, help should be at the --help when I interpret these guides.

I see this change as the start of implementing a more informative interface (with progress bars for more model components as mentioned in other PRs).

[PeterLombaers]

Looks good to me. It does mean less scrolling when you are running multiple simulations and you are scanning the output.

[jspaaks]

Thanks for the explanation and links!