esrf-bliss / Lima-camera-pilatus

Lima pilatus plugin
lima.blissgarden.org
GNU General Public License v3.0
0 stars 9 forks source link

problem with liblibconfig++.so when declearing new device and starting ./LimaCCDs 1 #6

Open qinwenming opened 1 year ago

qinwenming commented 1 year ago

We are trying to set up lima-camera-pilatus-tango at our MX beamlines for communication between mxcube and pilatus detector. We got problem when we declearing a new device for pilatus detector with "server wizard". When we start the Databaseds, it shows "ready to accept request" with "device tango/admin/nada not defined in the database". When we start "Starter dec2236", it shows "ready to accept request" with "/proc/**/cmdline No such file or directory". When we created and start " LimaCCDs 1", it shows "ImportError: liblibconfig++.so: cannot open shared object file : No such file or derectory". I serched with google and can't find the liblibconfig++.so Liberery. Should it be libconfig++.so? What should I do to figure it out?

We are setting up the lima-camera-pilatus-tango on the DCU (detector server). And we are aware of that this may could cause problem of camserver, which we don't have spare and can't setup ouself. Could we setup the Lima-camera-pilatus-tango on another server with centos7 system and only incharge of the communication between mxcube and pilatus detector? What should we do? Thanks a lot.

laurent-claustre commented 1 year ago

No a lima issue, just a installation problem with conda packages. I move the issue to pilatus plugin project instead.

laurent-claustre commented 1 year ago

Here my answer, already sent to you by email last week:

DEar Wenming,

it seems you have some mismatching with conda packages and versions. Could you execute a "conda list" in your environment and send us the list of the installed packages?

You should have the package libconfig from conda-forge installed, the latest version is 1.7.2

Otherwise you can create a new conda environment from scratch, for instance:

conda create -n pilatus -c conda-forge -c esrf-bcu lima-camera-pilatus-tango

To get fast installation you may use mamba tool, but you need to install it in your "base" environment first of all, then just run the same command above with mamba:

mamba create -n pilatus -c conda-forge -c esrf-bcu lima-camera-pilatus-tango

qinwenming commented 1 year ago

Dear Laurent,

Thank you very much. Here are the packages in our py37 environment with conda list. The version of libconfig is 1.7.2. And the problem repeats.

Best Regards,

874fecae6574153ba2569cfabcef721 0753a8296861e8862fdbdc0c6d90e09
qinwenming commented 1 year ago

Dear Laurent,

We created a new environment with "mamba create -n pilatus -c conda-forge -c esrf-bcu lima-camera-pilatus-tango", which is much faster than conda. When we registrated the instance and start ./LimaCCDs 1, it shows "Unknown exception while trying to fill database cache..." as following pics.

We repeated the Server Wizard steps several times, but never worked. Here are the procedures we did. Would you please have a look for us. Thanks a lot.

0336f8681c78873f2023038aa943b45

After we go through the "Server Wizard" step and decleared device for Pilatus detector, We started ./LimaCCDs 1, it shows "Can't get detector info" in the terminal and "No IOR found in database for lima/lilmaccd/1" in jive.

image image image image image
laurent-claustre commented 1 year ago

yes, the lima plugin needs to get some info from the detector configuration file, like the detector width and height. This is missing and you have to add it manually (~det/p2_det/config/cam_data/camera.def) has described in our documentation: https://lima1.readthedocs.io/en/latest/camera/pilatus/doc/index.html

You will have to create a ramdisk mounted as "/lima_data" as well to make the lima device server accessing the images saved by camserver program. Again you have some useful instruction in our documentation: https://lima1.readthedocs.io/en/latest/camera/pilatus/doc/index.html For the ramdisk size (in our example we set it to 8GB) we now typically allocate 16GB depending how much the DCU have in total.