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.

Sign up for GitHub

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

Jump to bottom

Keith's dynet fork needs to be moved to clulab #31

Open
kwalcock opened this issue Feb 15, 2021 · 0 comments
Open

Keith's dynet fork needs to be moved to clulab #31

kwalcock opened this issue Feb 15, 2021 · 0 comments
Assignees
@kwalcock

Comments

@kwalcock
Copy link
Member

That it isn't is an artifact, in both senses of the word: historical and unintentional result of a procedure. Moving it from the kwalcock repo to clulab probably isn't difficult. From there I'm wondering whether it should be referenced by fatdynet as a submodule, but I'm still reading about that.
@kwalcock kwalcock self-assigned this Feb 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kwalcock kwalcock

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kwalcock