pip version of tick is behind this repo. Update needed?

[HaochenWang1243]

Hi. I noticed many differences between this repo's tick directory and the pip version of tick, which make many examples un-runnable. For example, qq_plots in tick/plot/plot_point_processes.py isn't implemented in the pip version, making examples/plot_hawkes_estimated_intensity.py un-runnable.

[PhilipDeegan]

the pip version is quite old, the most update to date branch can be found at https://github.com/PhilipDeegan/tick/tree/releases

there are some test failures which I would appreciate help with, you can see them here for instance

to build this branch see the actions files

[HaochenWang1243]

Thank you. The pip version will updated in the future after there's a stable release right?

[HaochenWang1243]

Hi. I have a question particularly for the workflows you showed: It seems that the workflows are configured by the yml files in .github/workflows in your forked version of this repo instead of the one on this original repo. However, the action history is only available in this original repo, not in your forked repo. May I ask why? I searched for hours but didn't get any answer.

[PhilipDeegan]

The branch from my fork is a PR on this main repo

so the actions are on this repo

[HaochenWang1243]

Hi. Yes, I understand. Assuming these actions are triggered by the PR from your forked repo, why are they configured by the .github/workflows files in your forked repo, not the config files in this repo?

[PhilipDeegan]

this repo already uses something similar in the workflow files

when the PR is merged, this repo will be updated to be the same as my fork, I could just work on a branch on this repo, but I rather keep things isolated until merging

[HaochenWang1243]

Thank you

[HaochenWang1243]

When I tried to follow the steps in build_osx.yml on my (Intel) Mac, the very last command failed:

Do you have any idea how to fix this? Thanks

[PhilipDeegan]

cereal is a submodule of this repository

you can use git submodule update --init to initialize submodules

or you can get they while cloning with something like

git clone $URL --recursive