Users will often be in the situation where they have added many factors, but after a certain amount of experiments they suspect that one of the factors only has a very small impact on the response.
At the moment, the user has to either create a new experiment where they plug in the data again, or they can remove the factor and download the data as csv, remove a column, and upload the data again. Both solutions are slightly cumbersome. Also, it is a bit strange that one can remove a factor without actually removing the related column of data.
It would be great if the "remove a factor" button would also remove the measured data for this particular factor. I think there should be a pop-up window where where you have to click OK before the effect is taken.
In the ideal world there could be a possibility to disable a factor without deleting it - in order to try it out without tampering with the data. However, I am not sure if this is easily done in the frontend.
Users will often be in the situation where they have added many factors, but after a certain amount of experiments they suspect that one of the factors only has a very small impact on the response. At the moment, the user has to either create a new experiment where they plug in the data again, or they can remove the factor and download the data as csv, remove a column, and upload the data again. Both solutions are slightly cumbersome. Also, it is a bit strange that one can remove a factor without actually removing the related column of data.
It would be great if the "remove a factor" button would also remove the measured data for this particular factor. I think there should be a pop-up window where where you have to click OK before the effect is taken.
In the ideal world there could be a possibility to disable a factor without deleting it - in order to try it out without tampering with the data. However, I am not sure if this is easily done in the frontend.
This feature is slightly related to the bug reported here: https://github.com/BoostV/process-optimizer-frontend/issues/204