Apparently, it was quite popular among RasCAL-1 users to just give a value and not a minimum or maximum for a parameter that was not being fit (as the minimum/maximum don't matter there). This means that there may be many RasCAL-1 projects with invalid parameter values (i.e. value larger than min or smaller than max). r1ToProjectClass should allow these parameters, fix the minimum and maximum values, and provide a warning that it has done so.
Apparently, it was quite popular among RasCAL-1 users to just give a value and not a minimum or maximum for a parameter that was not being fit (as the minimum/maximum don't matter there). This means that there may be many RasCAL-1 projects with invalid parameter values (i.e. value larger than min or smaller than max).
r1ToProjectClassshould allow these parameters, fix the minimum and maximum values, and provide a warning that it has done so.