CompEvol
BEAUti support for required fields that really need user input
There is a tendency of BEAUti users just using defaults, where user input is really required. Putting in silly looking values (like in the SNAPP template where beta is set to 109.73) does not raise sufficient suspicion from users to ask what is going on.
Instead, we should have fields in BEAUti that more obviously should make the user aware that input (hence thought) is required before proceeding. Any suggestions for implementation welcome.
In BEAST 1 we have some priors that do not have a default and the GUI makes it impossible to save the XML without explicitly setting the prior with a user action. A pop-up dialog says explicitly that the user must choose the priors and that there is no default.
Alexei
On 7/12/2018, at 10:30 AM, Remco Bouckaert [email protected] wrote:
There is a tendency of BEAUti users just using defaults, where user input is really required. Putting in silly looking values (like in the SNAPP template where beta is set to 109.73) does not raise sufficient suspicion from users to ask what is going on.
Instead, we should have fields in BEAUti that more obviously should make the user aware that input (hence thought) is required before proceeding. Any suggestions for implementation welcome.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/CompEvol/beast2/issues/823, or mute the thread https://github.com/notifications/unsubscribe-auth/AA3WSe2v0AIqZndbm_zKiwbrxHnczVYjks5u2YyFgaJpZM4ZHWhW.
