-
Notifications
You must be signed in to change notification settings - Fork 61
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
Script Engine: Access to financial functions/Indicators #985
Comments
@all-contributors add @AwooOOoo for feature requests |
I couldn't determine any contributions to add, did you specify any contributions? |
@all-contributors add @AwooOOoo for ideas |
I've put up a pull request to add @AwooOOoo! 🎉 |
@badgerwithagun, |
No need to do anything! I just add people when they make contributions. |
Currently working on integrating https://github.com/ta4j/ta4j so we have programmatic access to indicators etc. Any objections to this package or do you have any other preferences? |
I believe there's already an issue open (a very early one) covering this. |
No objections |
Is your feature request related to a problem? Please describe.
Expose interface to the financial functions/Indicators that are available in the chart window.
Describe the solution you'd like
There are a lot of great functions/indicators drop-down in the chart window that I don't want to have to reinvent to build trading algorithms around so it would be good if there was a way to take advantage of them via the scripting interface. Perhaps we can expose a bunch of function handles you could call with their associated parameters.
First expose an indicators object;
Each function would take 1 'parameters' object which contains all of the parameters for that function. The description of the parameters for each function would be described in documentation.
Documentation
The indicator would have access to all of the historic data so that the indicator provides a valid response for the specific inputs.
Describe alternatives you've considered
It may be better to create an instance of the indicator and provide a callback so it is persistent as opposed to essentially creating it with each call which would likely use a lot more resources
Additional context
Script Access to all of these =D
The text was updated successfully, but these errors were encountered: