Closed anonymousDog12 closed 5 years ago
Thanks. This will be fixed in the next couple of days no doubt.
For the time being you can overcome this by:
t.x = np.zeros(500)
t.y = np.zeros(500)
The line of code where the issue arise is not really important even you override it this way as it merely stores a small sample of x and y data for reference purpose.
Thanks. This will be fixed in the next couple of days no doubt.
For the time being you can overcome this by:
t.x = np.zeros(500) t.y = np.zeros(500)
The line of code where the issue arise is not really important even you override it this way as it merely stores a small sample of x and y data for reference purpose.
Appreciate it!
This is also happening while saving CNN - it is not specific to RNN.
This issue would manifest in all cases where x (or y) is not 2d. Given there can be many different data formats, it's not a straightforward thing to resolve. I have to investigate this further.
For now, I've overcome this in v.0.6 by using the above "hack" i.e. simply not storing any data. Here it's important to note that we don't store the data for any other reason that having a small reference to what the data looks like, so it's not critically important to have it.
Closing here as this is already dealt with in v.0.6 onwards.
Keras RNN models require input data to be 3 dimensional, so I reshaped my training data to fit the RNN model. However, this forbids me from saving my model results because talo requires input to be 2-D.
Complete Trace: