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

Support for new parser deck is missing #75

Closed
blattms opened this issue Mar 27, 2014 · 4 comments
Closed

Support for new parser deck is missing #75

blattms opened this issue Mar 27, 2014 · 4 comments
Labels

Comments

@blattms
Copy link
Member

blattms commented Mar 27, 2014

With the old parser becoming obsolete (e.g. there is no way of using the WellsManager), I thorrowly need support to creat a CpGrid from a new parser deck.

Is there any plan of adding this and when will it happen?

@blattms blattms added the bug label Mar 27, 2014
@joakim-hove
Copy link
Member

Is there any plan of adding this and when will it happen?

The process has just started. Do not hold your breath - but hopefully during next week.

@joakim-hove
Copy link
Member

With the old parser becoming obsolete (e.g. there is no way of using the WellsManager), I thorrowly need support to creat a CpGrid from a new parser deck.

But as of just now you can still use the old parser (i.e. you have to instantiate both a new and an old deck instance, not very elegant but ...). Or do I misunderstand something?

@blattms
Copy link
Member Author

blattms commented Mar 27, 2014

But as of just now you can still use the old parser (i.e. you have
to instantiate both a new and an old deck instance, not very elegant
but ...). Or do I misunderstand something?

Yes, that thought crossed my mind, too. I will pursue this in the
meantime. Thanks.

@atgeirr
Copy link
Member

atgeirr commented Dec 23, 2014

This should be in place now, for some time. Closing.

@atgeirr atgeirr closed this as completed Dec 23, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants