Improve usability of configuration form elements

[david-chapela]

Currently, the configuration of each algorithm is set through generic HTML form elements with no customization. For example, thresholds (a value between 0 and 1) are set through a generic "number" element that allows to increase/decrease the quantity by "1", without any limit, which makes no sense. Parameters such as the number iterations of the optimization (positive integer) allow negative numbers.

SIMOD:

• Depict "evaluation metrics" only when "Perform final evaluation" is clicked.
• Depict "evaluation metrics" as a radio button, or a list of metrics that can be toggled as selected or not.
• Remove "Clean Intermediate Files", as this is irrelevant to the user, but set it always to true in the .yaml form.
• Show "Enable time concurrency threshold" (float between 0 and 1) only if selected log has no "enabled time" column, and explain that is the threshold to detect concurrency when computing the enabled time of each activity instance.
• Show the three "Concurrency Thresholds" (floats between 0 and 1) only when the selected log has no "start time" column, and explain that these are the thresholds to estimate the start time of each activity instance, based on the Heuristics Miner concurrency oracle.
• "Number of iterations" and "Number of evaluations per iteration" are integers ranging from 1 to infinite.
• Depict "gateway probabilities" as a radio button, or two elements, one of each option, allowing the user to select one or both.
• Both "Epsilon" and "Eta" can be either a value (no parameter optimization) or a range (parameter optimization within that range) between 0.0 and 1.0. Allow the user to pick between a single value or a range (in a prettier way than the current one if possible).
• Only depict "Replace OR-joins" and "Prioritize Parallelism" if "SM1" is selected, no values in the .yaml otherwise. Also, this is a parameter with three options, either i) replace them (true), ii) do not replace them (false), or iii) both, list with "false" and "true" in the .yaml so it tries with any of them during the parameter optimization.
• "Granularity" can be a single value or a range, from 1 to 1440 (number of minutes in a day).
• "Confidence", "Support", and "Participation" can be a single value or a range, always between 0.0 and 1.0.
• Move "discover prioritization rules" and "discover batching rules" to the top of the section.
• Only display "Fuzzy Angle" if "differentiated by resource fuzzy" is selected. Also, this can be a value or a range, always between 0.0 and 1.0.
• Only depict "number of iterations" and "number of evaluations per iteration" when "complex" is selected as "discovery method".
• Remove "Version" as it is irrelevant to the user, this version of config parameters is always 4, so set it in the background transparently to the user.

PROSIMOS:
Lots of fields to fix here, especially numeric ones. Some important ones:

• "Branching probabilities" they need to be floats in between 0.0 and 1.0 that all together sum 1.0. Currently, they are just number elements with arrows to increase/decrease the value in 1 unit.
• Duration distribution values, currently float in seconds, could be changed by a field that allows to specify the unit (sec, min, hour).
• Calendars currently choosing a "from" and "to" for the days of the week, could be more intuitive if each line defines "begins at" and "ends at" as the hours, and then the line has the 7 week days to toggle (like alarm apps do). In this way, each line established a time interval, and selects the week days that contain it.