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

pyDOE2 non-functional with python 3.12, appears to be unsupported. #470

Closed
robfalck opened this issue Oct 20, 2023 · 5 comments
Closed

pyDOE2 non-functional with python 3.12, appears to be unsupported. #470

robfalck opened this issue Oct 20, 2023 · 5 comments

Comments

@robfalck
Copy link

Hello SMT team,

We've noticed on the OpenMDAO side that pyDOE2 does not work with python 3.12, and despite a pull request to fix it, it appears that the lead developer is non-responsive.

Supporting the DOE capability of pyDOE2 isn't necessarily in our teams area of expertise or bandwidth at the moment. Can we talk sometime about someone making an "official" fork of the project, or integrating its capabilities? It seems like SMT sampling methods might be an appropriate fit, but I'm open to ideas.

@relf
Copy link
Member

relf commented Oct 23, 2023

Hi Rob,

Yes, sampling methods API in SMT is exactly the topic of pyDOE2. In SMT we just provide random, fullfactorial and optimized LHS sampling methods and we depend on pyDOE2 as well. Even if we have a nice API, at the moment the sampling methods are more a utility for testing and showing surrogates capabilities than being the core of the library which is acually the purpose of pyDOE.
So should pyDOE2 not be maintained, we could :
a - Just copy/adapt the relevant part under sampling methods (ie doe_lhs, bbdesign) to just keep current SMT in shape
b - or fork pyDOE2 under SMTOrg and package it as let say pyDOEtoo and just use it,
c - or integrate all pyDOE2 methods under sampling methods, with tests, documentation, etc.
Ignoring the selfish option a), I think we could implement b) and if there is a compelling need maybe gradually implement c) with the help of the community ?

@robfalck
Copy link
Author

If you're willing to accept the management of it, then I'd say option B probably makes the most sense. pyDOE3? 🙂

@relf
Copy link
Member

relf commented Oct 25, 2023

pyDOE3 1.0 is out!

@robfalck
Copy link
Author

Thank you!

@gedeck
Copy link

gedeck commented May 7, 2024

Thank you

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

3 participants