even though there is a limit on the numeric input for sampling fractions, it is possible for a user to manually enter something absurd (0 or negative, or greater than 1).
now the value gets updated to a reasonable range if it's absurd and the estimation proceeds with the input values being updated as well (it only shows after the model is done running because of the code runs through reactivity...making it instantaneous to the click of the button to run the model would take much more work right now)
there's also a warning message returned to notify the user more explicitly that the input and used value were changed
even though there is a limit on the numeric input for sampling fractions, it is possible for a user to manually enter something absurd (0 or negative, or greater than 1). now the value gets updated to a reasonable range if it's absurd and the estimation proceeds with the input values being updated as well (it only shows after the model is done running because of the code runs through reactivity...making it instantaneous to the click of the button to run the model would take much more work right now) there's also a warning message returned to notify the user more explicitly that the input and used value were changed