alteryx / compose

A machine learning tool for automated prediction engineering. It allows you to easily structure prediction problems and generate labels for supervised learning.
https://compose.alteryx.com
BSD 3-Clause "New" or "Revised" License
492 stars 46 forks source link

Issue While Running a Example #273

Closed HAtheDataScientist closed 2 years ago

HAtheDataScientist commented 2 years ago

I'm running the example 'Next_Purchase_Prediction' getting an error with the creating entities: Screenshot (546)

thehomebrewnerd commented 2 years ago

@HAtheDataScientist The release of Featuretools 1.0 included many breaking changes to the API. We are in process of updating all of our demos and examples to use the new API, but many, including the example you show above, still use the old API. Thank you for bringing this issue to our attention.

It may take a bit of time to get the examples updated, but in the meantime, if you want to try to update this example on your own, you can look through this document that highlights the significant updates that will be required: Transitioning to Featuretools 1.0

HAtheDataScientist commented 2 years ago

Hi, So far I have cracked the error and been able to solve that problem, but having another issue below, I am following up with the example Example from compose https://compose.alteryx.com/en/stable/examples/predict_next_purchase.html and the installed dependencies are from the git doc Dependencies https://github.com/alteryx/open_source_demos/blob/main/requirements.txt. Getting an issue while running with the evalml, please find the error in the attachments. I guess there is an error with the older/newer arguments. please help me with the getting out with the proper Evalml arguments for

On Thu, Jan 13, 2022 at 7:29 PM Nate Parsons @.***> wrote:

@HAtheDataScientist https://github.com/HAtheDataScientist The release of Featuretools 1.0 included many breaking changes to the API. We are in process of updating all of our demos and examples to use the new API, but many, including the example you show above, still use the old API. Thank you for bringing this issue to our attention.

It may take a bit of time to get the examples updated, but in the meantime, if you want to try to update this example on your own, you can look through this document that highlights the significant updates that will be required: Transitioning to Featuretools 1.0 https://featuretools.alteryx.com/en/stable/resources/transition_to_ft_v1.0.html

— Reply to this email directly, view it on GitHub https://github.com/alteryx/compose/issues/273#issuecomment-1012161444, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXJBKLILHXMV3FB7KGP3TCDUV3LCZANCNFSM5L2Z3RUQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>

thehomebrewnerd commented 2 years ago

@HAtheDataScientist I will try to spend a little time updating this example so that it works, but it might take me a day or two.

thehomebrewnerd commented 2 years ago

@HAtheDataScientist We released an updated version of compose today that fixes this example. If you install compose 0.8.0, Featuretools 1.4.0, and EvalML 0.41.0, the demo in the updated documentation should now work: https://compose.alteryx.com/en/latest/examples/predict_next_purchase.html

I am going to close out this issue for now, but if you have additional problems, please reopen this issue or create a new issue.