This issue applies to dev versions between 0.6.0-3 and 0.6.0-7.
This bug has now been resolved, but formal testing should be put in place for such scenario.
With the introduction of scaling vectors in place of scaling factors, some code omissions caused RATs to crash. The tests failed to pick up the crash at all. Probably because the breaking code is only executed when scaling is requested, and none of the old tests have a scaling scenario.
[x] Create scaling tests.
[x] Test more of the preparatory steps in rats.R. Direct testing of the functions only does not cover all sources of error.
This issue applies to dev versions between 0.6.0-3 and 0.6.0-7. This bug has now been resolved, but formal testing should be put in place for such scenario.
With the introduction of scaling vectors in place of scaling factors, some code omissions caused RATs to crash. The tests failed to pick up the crash at all. Probably because the breaking code is only executed when scaling is requested, and none of the old tests have a scaling scenario.
rats.R. Direct testing of the functions only does not cover all sources of error.