Repository navigation
Conversation
|
cc @jaingaurav |
| In particular, if you have 4 inputs to a hint stub, this will be the | ||
| node that you can use as an output. I.e. you have 4 timesteps from a | ||
| static rnn, then a fused UnidriecitonalLSTM will expect 1 input with | ||
| static rnn, then a fused UndirecitonalLSTM will expect 1 input with |
| std::string some_name = "something"; | ||
| // Don't test float in this case, because precision is hard to predict and | ||
| // match against, and we don't want a flakey test. | ||
| // match against, and we don't want a franky test. |
|
@renjie-liu Thank you for pointing them out. I addressed both of them. |
| namespace { | ||
|
|
||
| std::string GetMaxUnoolingKernelCode( | ||
| std::string GetMaxUnroolingKernelCode( |
| if (depth != 1) { | ||
| return InvalidArgumentError(absl::StrCat( | ||
| "SINGLE_TEXTURE_2D support only cnannels in range [1-4], but ", | ||
| "SINGLE_TEXTURE_2D support only chnannels in range [1-4], but ", |
| In particular, if you have 4 inputs to a hint stub, this will be the | ||
| node that you can use as an output. I.e. you have 4 timesteps from a | ||
| static rnn, then a fused UnidriecitonalLSTM will expect 1 input with | ||
| static rnn, then a fused UndirectionalLSTM will expect 1 input with |
There was a problem hiding this comment.
this does not seem to be changed?
this should be UnidirectionalLSTM
There was a problem hiding this comment.
You are right. sorry for my overlooking.
renjie-liu
left a comment
There was a problem hiding this comment.
thanks, looks good! please resolve the inline comments
|
@renjie-liu Thank you. Addressed your three comments. |
|
|
||
| Status MaxUnpooling::Compile(const CreationContext& creation_context) { | ||
| const auto code = GetMaxUnoolingKernelCode( | ||
| const auto code = GetMaxUnroolingKernelCode( |
There was a problem hiding this comment.
this should be changed as well?
There was a problem hiding this comment.
Thank you again, done
|
@kiszk Can you please address Ubuntu Sanity errors? Thanks! |
|
Thank you for pinging me. I overlooked pylint error. I have just pushed the fixes. |
|
@gbaned @mihaimaruseac Resolved a conflict again. |
mihaimaruseac
left a comment
There was a problem hiding this comment.
Probably it would be better to split this even more given that it keeps getting into conflicts.
Let's give it one more try but if we get new conflicts let's try splitting on the next directory level.
|
Manually imported the change and synced to head again. If this still fails to merge I'll suggest splitting it as per previous comment |
|
Turns out this fails to merge properly. I'm starting a new run to eliminate transient errors but I think it would be better to split it (and resync on master). Apologies for the extra work you'll have to do. |
mihaimaruseac
left a comment
There was a problem hiding this comment.
Should be split based on subdirectories of tensorflow/lite
|
@kiszk Can you please check mihaimaruseac's comments and keep us posted? Thanks! |
|
@gbaned thank you for pinging me. I overlooked the comments. I will split this PR into multiple PRs within next few days |
|
@kiszk Sure, Thank you very much for the update. |
|
You can ping me/assign to me all of the subsequent PRs. Thank you |
|
Once all subdirectories are fixed, we can sync this back on master to get the files that are left out. Or, we can just close it now and get the other PRs as needed. Thank you for all the fixes. |
|
I created all of sub-PRs. When they are closed, I think that it would be good to close this PR, too. |
|
Sounds good. Thank you |
|
Everything seems solved. Let's rebase this on master if there is still work left to do or close otherwise. Thank you |
|
@mihaimaruseac Thank you very much. It is the time to close this. |
|
Thank you for all the work and for the patience to carry on these PRs over 4 months |
This PR addresses minor spelling tweaks under
tensorflow/litedirectory.follow-on of #34958