-
Notifications
You must be signed in to change notification settings - Fork 30
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
Seeking clarifications #1
Comments
|
I agree with @shyuep on shunting MP-specific stuff to public packages. The idea of this public repository specifically is to shunt materials-science-agnostic stuff from pymatgen-db so that more eyes look at the code that essentially just builds on pymongo to manage database building and maintenance -- I couldn't find a good open library for this, and the audience is anyone who uses Mongo and Python (like https://github.com/materialsvirtuallab/flamyngo). The idea of https://github.com/materialsproject/emmet is to trim pymatpro and outsource stuff to a public repo. |
Since i dont have much experience doing the building stuff, could someone explain:
The drawbacks in the design of the current builder in pymatpro
what new features(other than mpi support and dependency specification capabilities) must the new builder support? As far as i understand the one in pymatpro implements the producer consumer model using the multiprocessing package.
It would help my understanding a lot if someone could give me a concrete fully sketched out example of a builder with complicated dependencies.
What package dependencies are allowed? for example the current get_db function in the helpers module is a reimplementaion of the function in matgendb.utils module. So should we use those from matgendb package or make everything self-contained?
Thanks
The text was updated successfully, but these errors were encountered: