It would be simplest if you downloaded the bundles from the ChimeraX toolshed using your regular web browser. The downloaded files are Python wheels. Then they can be installed using the "toolshed install" command. You could prepare a defaults.cxc file that would install all of the default bundles from the shared location. If the bundles depend on a package from pypi.org, then you will need to download those too, but install using the "pip install" command. For example (untested): # load pypi packages first pip install /path/to/pandas-2.2.1-cp311-cp311-manylinux_2_27_x86_64.manylinux_x86_64.whl # next load bundles toolshed install /path/to/ChimeraX_BundleName-Version-PythonTag-ABITag-PlatformTag.whl Then "ChimeraX defaults.cxc" would run the command script, or the command script could be opened (either on the command line or in Open dialog). The difference between "toolshed install" and "pip install" is that that "toolshed install" reads the added ChimeraX metadata in the wheel. So the commands, file formats, and tools get integrated into the interface. A totally untested alternative is to run your own pypi server, put the wheels you downloaded there, and use the --toolshed command line argument to point to it. The toolshed has some additional APIs that a pypi server doesn't, but it might work HTH, Greg On 4/8/2024 7:13 AM, Ricardo Righetto via ChimeraX-users wrote:
Hi,
We are setting up a new cluster at our university, and I stumbled upon the following problem: our nodes used for remote visualization don't have access to the internet. Therefore, users running an interactive graphical session won't be able to install bundles by themselves, which was the case in our old cluster. One workaround is to start ChimeraX either without GUI or with X forwarding over SSH on one of the normal login nodes (no high-end visualization capability) just for the purpose of downloading and installing bundles from the toolshed. This is however inconvenient to most users. Another approach is to install using the 'toolshed' command with a pre-downloaded wheel, but also not ideal.
My thought would be to preinstall the most common plugins we use (like ArtiaX and ISOLDE) into a shared location, and ChimeraX would then find the bundles installed there upon startup. Therefore, my question is: is any other path other than the user's home folder supported for installing bundles? If yes, what is the order of search paths? Alternatively, is there some environment variable or other setting that I can use to tell ChimeraX where to find installed bundles?
Thanks in advance,
-- Ricardo Diogo Righetto
_______________________________________________ ChimeraX-users mailing list --chimerax-users@cgl.ucsf.edu To unsubscribe send an email tochimerax-users-leave@cgl.ucsf.edu Archives:https://mail.cgl.ucsf.edu/mailman/archives/list/chimerax-users@cgl.ucsf.edu/