-
Notifications
You must be signed in to change notification settings - Fork 371
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
SeeDot-dev.py only working for fastgrnn #251
Comments
@affot The code pertaining to |
Hello @ShikharJ |
Hmm, in that case, could you look at |
I don't see no output folder in |
Okay, I must apologize for leading you astray. It seems that the nomenclature that is being followed internally is |
I did it, but I get the same Error :-(
|
Could you share the |
|
@affot Sorry for the late reply. You're using the DSL code pertaining to
Please note that the |
Hello @ShikharJ And then: I also tried |
@affot Sorry for the delay once more :) Nearly all of the debugging regarding SeeDot can be done by looking at |
I have similar issue. In my case, however, the dataset is a custom dataset which has been properly converted into .npy files. The input array to the fastgrnn model is 550*6. Note that I am trying to modify fastgrnn.sd to account for the shapes, but I am not sure what the two values in between the two 'ins', e.g., |
@swapnilsayansaha The values in the square brackets are the floating-point ranges of the concerned tensors. So for example, if your
|
Thanks a lot. That really helped. I have a few more questions @ShikharJ If X = (550,6), what should be XX be reshaped to (probably the decomposition is due to memory efficiency)? I can provide some intuition. In the example of Seedot, we have:
This comes from the fact the USPS dataset input is a 256*1 array (assuming batch size of 1). The input dim was 16 and hidden dim was 32. The output is binary, which explains (1,2) in the output (?) In my case: my input dim is [550,6] and hidden dim is 50. the output is (1,9). I was wondering how to properly select the parameters in reshape line of XX. (For matrix multiplication intuition, my W is 6*50 (for the line |
@swapnilsayansaha The hidden dimension has got nothing to the shape of X, it is the second dimension of
The first tuple in the reshape operation depicts the final shape of the reshape output (or simply, the shape of |
When I cast
and in build.txt: exec.txt is empty. |
Can confirm I have the same error. |
I see, |
This is correct, the dimensions of the
If you want to understand what happened here, I just followed the example to train the bonsai algorithm, nothing has been changed on my side. |
@affot Okay, this seems like a major issue then. I'll need time to look into it. Sorry for the inconvenience. |
No Problem, thanks a lot for taking care! |
What I understood from trying to run anything apart from the USPS-10 tutorial given in the repo, even training the model for 1 epoch less (the USPS-10 fastgrnn model) causes Seedot compilation to fail (sometimes Seedot says X cannot be quantized properly, sometimes it says test accuracy object not found, sometimes it can't find quantization functions). I think a lot of things are internally hard-coded to work for the specific example given. Maybe a more general tutorial on what things to modify for a custom model and a custom dataset might help. While I did manage to solve the matrix dimension issues later after some fiddling, the compilation still failed during converting the model to .h files. |
Hello,
the SeeDot explanation is working for the Fastgrnn.
But when I transfer the same steps for Bonsai or ProtoNN, the workaround makes some problems.
For example:
python SeeDot-dev.py -a bonsai -e fixed -d usps10 -n 1 -t arduino -m red_disagree -l info
It starts with an Error for the assignment in line 227: acc = obj.testingAccuracy with the information, that the Main-Object has no "testingAccuracy".
Is there an easy way to fix this an do the same quantization for bonsai and protoNN?
The text was updated successfully, but these errors were encountered: