import CCF error

[sbrems]

Dear Rafael et al.,

thank you for that very nice ceres pipeline.
I was using it for quite some time, however now I tried to install it on a new cluster and do not get it to run. Whenever I try to run it, I get the error that CCF is not defined. To be precise, here is the error:

$ python2 ferospipe.py /mnt/fhgfs/RVSPY/archival_datasearch_oct18/sciencefiles/HD111103/
Traceback (most recent call last):
File "ferospipe.py", line 20, in
import ferosutils
File "/data/beegfs/astro-storage/RVSPY/ceres/feros/ferosutils.py", line 16, in
import GLOBALutils
File "../utils/GLOBALutils/GLOBALutils.py", line 23, in
import CCF
ImportError: No module named CCF

Thank you,
Stefan

[rabrahm]

Hi Stefan, Usually that kind of messages mean that the associated code was not properly compiled when installing CERES. Specifically, CCF is a fortan code that should have created a CCF.o file in ceres/utils/CCF after the installation. Rafael El mar., 23 oct. 2018 a las 11:00, sbrems (<[email protected]>) escribió:

…

Dear Rafael et al., thank you for that very nice ceres pipeline. I was using it for quite some time, however now I tried to install it on a new cluster and do not get it to run. Whenever I try to run it, I get the error that CCF is not defined. To be precise, here is the error: $ python2 ferospipe.py /mnt/fhgfs/RVSPY/archival_datasearch_oct18/sciencefiles/HD111103/ Traceback (most recent call last): File "ferospipe.py", line 20, in import ferosutils File "/data/beegfs/astro-storage/RVSPY/ceres/feros/ferosutils.py", line 16, in import GLOBALutils File "../utils/GLOBALutils/GLOBALutils.py", line 23, in import CCF ImportError: No module named CCF Thank you, Stefan — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#19>, or mute the thread <https://github.com/notifications/unsubscribe-auth/APktrNFcGcfozwIei_ZcV0bkh0sVCuJ-ks5unyD7gaJpZM4X1o7G> .

[nespinoza]

Hi Rafael,

We solved this with Stefan --- turns out the Fortran codes (Proceso_f2py) use f2py via subprocess, which in turn use the f2py installed by default which might be different than the python version used to run the install (e.g., an user with Python 3 by default, might use the pipeline with python2.7 by installing it in the computer, run the install.py code via 'python2.7 install.py' and then the subprocess call in the install.py file will run Proceso_f2py, which uses f2py BUT from Python 3 by default). What I did was to simply replace the f2py call in Proceso_f2py by f2py2.7 (which other f2py versions you have in your computer can be checked via whois f2py). Reminder to myself (or to you) to check which python version the user has by default to keep track of this? Add a warning? Perhaps at the very least put this in a FAQ in the README file.

Néstor