-
Notifications
You must be signed in to change notification settings - Fork 345
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
How to predict current decision #12
Comments
adding in methods.py the following and calling it from a file similar to eval.py?
|
Hi, I've added predict_next to methods.py and created a similar script to eval.py - but get the following error: Traceback (most recent call last): Any suggestions? Thanks in advance, great project!
|
Hey, I'll have to look that up in the next days, but yes I had the same error. #ops.py
|
Very kind of you to respond, thanks so much.On 3/11/2020 22:20, Justin Güse <notifications@github.com> wrote:
Hey, I'll have to look that up in the next days, but yes I had the same error.
I think as a quick fix you could add sth along the lines of
#ops.py
def get_state(data, t, n_days):
"""Returns an n-day state representation ending at time t
"""
#blocks = []
#for feature in datan.columns:
#feature = "Close"
#data = list(datan[feature])
if len(data) == 0:
raise Exception("DATA IS ZERO!!! CHECK YFINANCE OUTPUT")
d = t - n_days - 1
block = []
if d >= 0:
block = data[d: t + 1]
else:
block = data[0:d] # pad with t0
res = []
for i in range(n_days - 1):
x = sigmoid(block[i + 1] - block[i]) # x is number
res.append(x)
return np.array([res])
—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or unsubscribe.
|
Hey, so to predict the current timestamp what would I need to do?
The text was updated successfully, but these errors were encountered: