-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when building sequential segments #142
Comments
Hey Abi, Looks like there is something wrong with the |
Hey Abi, Just a quick bump here. I'm still working out the solution. The embarrassing truth is that I left out the option to build segments with metrics. I've almost got a working solution but it probably won't be ready until the end of next week. |
Hi Ben - no problem, thanks for the update. This isn't urgent for me, just excited to use the package and wanted to try a bunch of example use cases, so that timing is more than adequate for me. |
Hey Abi! I realize it's been about 18 months (where did the time go?) since I got back to you but I think I have it working now. I've got a few more tests to run and need to finish up a few more edits across some other package improvements before publishing to CRAN. Hopefully you haven't given up all hope yet! If you would like to give it a test on your side, let me know. Other than that, I'll make sure to reply when I publish the new updates to CRAN. |
Hi there - thanks for your work on this package! I'm especially excited to see that you've exposed the ability to create segments via API and would love to see the capability to do calculated metrics as well.
I haven't been able to find examples for the segment-related functions in the docs yet (I assume you haven't gotten there) and I'm getting tripped up on creating sequential segments. I think there must be something wrong with my input below that's resulting in the error, maybe in what I'm supplying to the "sequences" argument of seg_build. If anyone can help I would much appreciate it!
Input:
Output:
The text was updated successfully, but these errors were encountered: