-
Notifications
You must be signed in to change notification settings - Fork 2
genie_python Troubleshooting
Genie_python writes its logs to ...\Instrument\var\logs\genie_python
.
The following is written to the log when a virtual circuit disconnects from the IOC side:
2018-05-21T15:21:31 (CA) (15712) ERROR: CAException: type=-1 state=192 op=5 file=..\cac.cpp lineNo=1223
2018-05-21T15:21:31 (CA) (15712) ERROR: CAException: type=6 state=192 op=0 file=..\getCopy.cpp lineNo=92
The time stamp on these are for the first get_pv
call or equivalent after a disconnect.
Have you pulled and rebuilt the latest version of the repository under \Apps\Python
?
If genie_python
crashes on start with a windows error but the underlying Python appears to start ok try importing numpy
. We have a problem with the latest CPUs (skylakex
) running under the hypervisor which means that the OPENBLAS
library has an unknown instruction in it. The current fix is to set the environment variable so it appears it is running a different core type. Do this with:
OPENBLAS_CORETYPE=Haswell
This is set within the system environment on the PC; currently, this fix is only needed on RIKENFE
and MUONFE
.
If you get an error message similar to
*** Cannot find GENIE-PYTHON 3 - some things are not likely to work ***
on running config_env.bat
, you need to ensure you have both python 2 and python 3 available on your system.
When running dev_build_python.bat
, you may get an error when Windows tries to apply a patch to the CaChannel.py
file.
If this happens, comment out the patch
command in common_build_python.bat
, then run the script again. Once it's finished, open a Git Bash window, cd
to /c/Instrument/Apps/Python/package_builder
and run the same patch
command you commented out, changing the Windows paths to UNIX paths (\
-> /
and C:
-> /c
). Then, check the CaChannel.py
file to ensure it was patched properly.