Linear Regression: several error messages

Good morning!

I'm trying to predict the likelihood of product being rejected upon receiving based on weather conditions of the supplier location when filling orders. I'm experienced with Alteryx, but not with the predictive tools. I dabble in several programming languages, but not R. These errors make no sense to me. Can someone point me in the right direction for error resolution?

Linear rejection errors.JPG

Linear rejection configuration.JPG

Produce Rejections Predictor.yxmd

Error Message

Predictive Analysis

Accepted answers

RobertOdera

Hi, @cdahl001

It looks like all the predictor fields have a significant %missing values that are flowing through as Nulls.

I will offer that the Nulls are throwing the errors.

Kindly consider imputing the values.

It might also be that your data set lacks richness/ density (some of the fields have a very small number of value counts).

Kindly consider combining some values/ aggregations if and where it makes sense.

Finally (not sure if this is a factor), your field names have spaces.

In my experience, I've seen algorithms struggle with that.

Kindly consider using the Dynamic Rename tool by configuring it per the snippet below.

All comments

RobertOdera

Hi, @cdahl001

If you hadn't already done so, kindly wash the data and re-attach a sample file as a packaged workflow (so we can attempt to help you).

The current yxmd attached means that we can't run the workflows we can't path to the file location on your desktop/ laptop etc.,

A "subscript out of bounds" usually means that Alteryx is trying to access an object that isn't there.

Make sure that all the fields that you need as inputs are flowing into the process/ tool.

Maybe you have the wrong field type so the field dropped because (for example) the algorithm needs to ingest a string whereas you are providing a different field type. I will offer that you add a Select Tool before input node into Regression Tool and use it to inspect the fields and field types to see if something needs tweaking or added or dropped.

The best case, however, is to attach a sample so that we can work it for you.

cdahl001

@RobertOdera Oh! Sorry about that. Here you go:

Produce Rejections Predictor.yxzp

Quick Links

This months top contributors

atcodedog05 19598

Qiu 15867

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703