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

Discussion forum (or mailing list)? (Question about remote ABINIT) #182

Open
fhssn1 opened this issue Jun 28, 2019 · 0 comments
Open

Discussion forum (or mailing list)? (Question about remote ABINIT) #182

fhssn1 opened this issue Jun 28, 2019 · 0 comments

Comments

@fhssn1
Copy link

fhssn1 commented Jun 28, 2019

Does abipy have a discussion forum or mailing list, where ideas can be exchanged, and/or questions can be asked and answered?

I specifically have two questions:

  • Is there a way to utilize only the post-processing facilities of abipy on a local computer, assuming ABINIT calculations are completed on a remote cluster, and all the data has been transferred back to local computer?

  • In general, abipy has data managers that allow you to specify how to run ABINIT on a cluster. However, it appears that the assumption is that the whole python scientific stack, jupyter notebooks, as well as abipy is installed on the cluster. My use case is such that I only want ABINIT on the cluster, while everything related to python, notebooks, and abipy is on my local computer. How to make such a setup work? I know there will have to be some scripts on the cluster that manage the execution of ABINIT, but I want those scripts to be as minimal as possible, only there to manage the ABINIT execution, while all the input/flow preparation, and post-processing happens on local computer. Any comments?

Thanks in advance

@fhssn1 fhssn1 changed the title Discussion forum (or mailing list)? Discussion forum (or mailing list)? (Question about remote ABINIT) Jun 28, 2019
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

1 participant