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

How can we support ILAMB v1 and v2 in WMT? #11

Open
mdpiper opened this issue Jan 27, 2017 · 0 comments
Open

How can we support ILAMB v1 and v2 in WMT? #11

mdpiper opened this issue Jan 27, 2017 · 0 comments
Assignees
@mdpiper

Comments

@mdpiper
Copy link
Member

mdpiper commented Jan 27, 2017

ILAMBv1 (the NCL version) currently takes the name "ILAMB" when componentized. We need to figure out how to allow both ILAMB v1 and v2 (the Python version) to live peaceably in the same WMT instance.

For a start, I propose using component names "ILAMBv1" and "ILAMBv2". But this is kinda clumsy, and ILAMB v1 is supposedly deprecated.
@mdpiper mdpiper self-assigned this Jan 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mdpiper mdpiper

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mdpiper