utf-8 error, when load par file
When I try to run libstempo-toasim-demo.ipynb, it shows utf-8 error. The detail info pasted below. Could you help me to check this problem? Thanks. @vallis @mattpitkin
Python version : 3.7.12 libstempo version: 2.4.5 Tempo2 version : 2022.5.1
UnicodeDecodeError Traceback (most recent call last)
/tmp/ipykernel_27615/1593190486.py in
libstempo/libstempo.pyx in libstempo.libstempo.tempopulsar.cinit()
libstempo/libstempo.pyx in libstempo.libstempo.tempopulsar._readflags()
libstempo/libstempo.pyx in libstempo.libstempo.lambda1()
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 0: invalid continuation byte
Hi, I just noticed that I had the same error. My solution was using the previous version of libstempo: 2.4.3?
It was working for me
Hi, I just noticed that I had the same error. My solution was using the previous version of libstempo: 2.4.3?
I installed the previous version of libstempo=2.4.3, but when I tried to load J1909-3744_NANOGrav_dfg+12.par and the corresponding timfile, there is another error message showing up "Segmentation fault (core dumped)". Did you encounter this error before?
Python version=3.10.4, Tempo2 version: 2021.7.1.
Hi, I just noticed that I had the same error. My solution was using the previous version of libstempo: 2.4.3?
I installed the previous version of libstempo=2.4.3, but when I tried to load J1909-3744_NANOGrav_dfg+12.par and the corresponding timfile, there is another error message showing up "Segmentation fault (core dumped)". Did you encounter this error before?
Python version=3.10.4, Tempo2 version: 2021.7.1.
For those who have the same issue, you can conda install an older version of libstempo=2.4.0 (which will automatically installed an old version of Tempo2=2020.111) to solve the above error. It seems that the incompatibility between the new version of Tempo2 and the version of the Python wrapper libstempo causes the error.
By the way, in my conda environment, the Python version = 3.6.13.
@jlzhang001 @F-W-Yang can you confirm whether this is still an issue with the latest versions of libstempo/tempo2?