Giter VIP home page Giter VIP logo

lifetime_value's Issues

Loss calculation

In the function to calculate ZILN loss,

The classification loss and regression loss is combined together, however, the scale of two loss is different meaning, the binary crossentropy loss is often much smaller than regression loss. Shouldn't we compensate for this difference in scale?

In addition, why do we take the negative of regression loss?

How are LTV distributions calculated?

Thank you for making the code for the loss function, metrics and example notebooks open source.

From the last paragraph in section 3:

Another key advantage of the ZILN loss is that it provides a full prediction distribution. We obtain not only the probability of returning but also the value distribution of LTV for returning customers. In addition to mean LTV prediction, the uncertainty of LTV predictions can be assessed using quantiles of a lognormal distribution as in general quantile regression.

To me it is unclear both from checking the code examples and the paper, how the LTV prediction distributions are calculated, can you get them both for a singel predictions and a group of prediction for example?

Thank you!

Question regarding simultaneous objectives

First of all, thank you for making the code for the loss function, metrics & example notebooks open source.

I am looking forward to trying this approach out. I have one question that I am a bit confused about.

The paper mentions that the model structure, in combination with the loss function used, allows for one model to capture both objectives: churn prediction and remaining lifetime value prediction.

First, it is capable of predicting the churn probability and LTV value simultane-
ously. It reduces the engineering complexity of building a two-stage model (Vanderveld et al., 2016)
— a binary classification model to predict repeat purchase propensity, followed by a regression model
to predict the LTV of returning customers predicted in stage 1.

Indeed, the loss function returns a composite of both churn & remaining value losses:

  return classification_loss + regression_loss

However, the notebooks are split up in two, one for each separate objective.

Can one trained model indeed perform both tasks: the notebooks are split up to illustrate a comparison between the churn and remaining value tasks to two separate models?

Or are did I completely misinterpret the paper? In which it is meant that the type of model can perform both tasks, but you need two trained models: one fine-tuned for each task.

Thanks, and I am looking forward to trying this out. :)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.