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

Should we have a JuLIPData package #133

Open
cortner opened this issue Jan 16, 2021 · 1 comment
Open

Should we have a JuLIPData package #133

cortner opened this issue Jan 16, 2021 · 1 comment

Comments

@cortner
Copy link
Member

cortner commented Jan 16, 2021

CC @jamesgardner1421

Maybe we should avoid keeping any data files in JuLIP, but load then all into a JuLIPData package. The next step might be to use that package to automatically download a large number of potential definition files. We experimented with this in our tightbinding code where it worked really well.

@jamesgardner1421
Copy link
Member

That seems sensible. It's not very neat to have them in here.

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

2 participants