New package: VpinEstimation v0.1.0

[JuliaRegistrator]

• Registering package: VpinEstimation
• Repository: https://github.com/jinyunfan/VpinEstimation.jl
• Created by: @jinyunfan
• Version: v0.1.0
• Commit: 95ea205b4e4aee760ee35d4181f6f7e9f94a8f9b
• Git reference: main
• Description: With reference to Easley et al(2014), the volume synchronized probability of informed trading is estimated under high-frequency environment, and the index VPIN(volume synchronized probability of informed trading) is calculated.

[github-actions]

Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human.

1. New package registration

Please make sure that you have read the package naming guidelines.

2. AutoMerge Guidelines are all met! ✅

Your new package registration met all of the guidelines for auto-merging and is scheduled to be merged when the mandatory waiting period (3 days) has elapsed.

3. To pause or stop registration

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.

[goerz]

Thank you for resubmitting. This still needs a little bit more documentation in order to be registered. Packages in General are intended to be useful to a wider audience, which requires enough documentation to be able to figure out how to use the package. As a minimum, an initial registration might provide a usage example (with some explanations) in the README. Of course, a more complete Documenter-based documentation with tutorials etc. is always a good idea, and usually a requirement in the long term (for a v1.0 release) at least for more complex packages.

[jinyunfan]

Ok, I changed the version number to v0.1.0. Is it OK now? @goerz

[goerz]

No… Didn’t you see my comment?

[jinyunfan]

Sorry,I misunderstood. So I will add a usage example and function descriptions before submitting.