Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Using a column value for 'minimum_data' in label_maker.search()
See original GitHub issueI would like to pass the date when a customer was created as an input for the minimum_data in label_maker.search(). I understand minimum_data would require a lower bound for the series (per customer, in this case).
The data structure then would go from e.g. Transaction1-NoEvent-NoEvent-Transaction2 to NoEvent (customer creation date)-NoEvent-Transaction1 …
It seems it is not possible to refer to an existing column that is part of the dataframe used to generate the labels when specifying minimum_data.
Motivation: I don’t want to start off with the first transaction on record but the time when we acquired the customer record. In a later stage I would want to add e.g. marketing activities on the customer level. The hypothesis would be that customers who transition more quickly from creating an account to purchasing a product are generally more eager to engage with the brand.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
That’s what I had in mind. Would be nice to see this addition.
@S-UP this feature is available in the latest release 0.7.0. Sorry for the delay and thanks again for the feature request!