-
Notifications
You must be signed in to change notification settings - Fork 128
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
adios2.so not built. Docs not up-to-date in terms of python bindings from source? #4007
Comments
I just found #3813. It made me look at the newer examples in the docs, Doc Examples, which differ substantially from the examples in the examples directory: Repo Examples Note that the doc examples also have errors in them Which I assume is due to the update from low-level to high-level API in #3813 . |
The python interface is being redesigned and there is no adios2.so anymore there. You should find plenty of .py files under This is in the master and release_210 branch. Your existing python codes for processing adios files need to be revised. See e.g. |
Oops, did not see your last comment. Exactly, as you say, the examples haven't been worked on yet. |
Thanks for confirming, @pnorbert! Since I realize, it is a work in progress, I think this can be closed for now. Unless you want to keep it open for later closing. |
Okay. I will keep open to track the outdated examples and documentatio |
Just a note: examples are up to date with the new API now. |
I am working on a cluster. So, before cmake building. I do, module load conda openmpi/4.1.5_gcc-10.4.0
conda create -n adios2 python=3.10
conda activate adios2
conda install numpy
conda install -c conda-forge mpi4py openmpi As a workaround while working with conda envs, I set the prefix to the conda env's prefix cmake -DCMAKE_INSTALL_PREFIX=$CONDA_PREFIX .. Then, conda will load all the shared >>> import adios2
>>> adios2
<module 'adios2' from '/home/apurandare/.conda/envs/adios2/lib/python3.10/site-packages/adios2/__init__.py'>
>>> adios2.is_built_with_mpi
True |
Closing this issue. The python documentation should be up to date now. |
Describe the bug
Docs not up to date in terms of Parallel Python bindings? adios2.so not built.
I'm trying to install parallel ADIOS2 bindings for Python on Frontier and everything in the CMake log looks alright. It finds the right python executable
To Reproduce
Loaded modules
This is where it becomes slightly tricky because you will have to install your own miniconda/mamba. Which I will not delineate here. Then, create clean environment for the installation.
Finally, clone adios2 from github and use cmake
3.20.4
to configure and install adios2The configuration, compilation and installation all seem to be successful. No errors, but a missing adios2.so.
Expected behavior
I expect the
../install/lib/python3.11/{site-packages/,site-packages/adios2}
to contain aadios2.so
file, as described in the docs, but that's not happening. I also tried adding the../install/lib/python3.11/site-packages/adios2/bindings
to that PYTHONPATH, but the bindings have completely different names compared to what's described in the docs. Am I missing something?This used to work flawlessly on Summit with cmake and then
conda develop ../install/lib/python3.11/site-packages/
but conda develop is also being deprecated.I feel like I'm overcomplicating things, and the installation docs are not overly descriptive for the python portion from source. Is there something that I can do to simplify this? E.g. define the python site-packages for my environment as installation location at CMake configuration time?
Desktop:
The text was updated successfully, but these errors were encountered: