Skip to content
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

Impact of run-time feature #26

Closed
My-Khan opened this issue Oct 4, 2016 · 4 comments
Closed

Impact of run-time feature #26

My-Khan opened this issue Oct 4, 2016 · 4 comments

Comments

@My-Khan
Copy link

My-Khan commented Oct 4, 2016

Hello Sir,
hope you will be fine
Would you please like to let me know the impact of run-time features on results, simply why we use run-time features?

@zhongkaifu
Copy link
Owner

Run-time features means RNNSharp uses the previous token's output (T-1) as feature for current token (T). Currently, this feature is only enabled for forward RNN, but not b-directional RNN.

@My-Khan
Copy link
Author

My-Khan commented Oct 8, 2016

Many thanks sir, but sir still confused,
Actually whats the logic behind its usage? SIMPLY why run-time features are being considered?

@zhongkaifu
Copy link
Owner

The idea of run-time feature is to provide previous output token as feature to current token. It extends feature we have.

@My-Khan
Copy link
Author

My-Khan commented Oct 9, 2016

ok sir got it

@My-Khan My-Khan closed this as completed Oct 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants