Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Aug 13 12:56
  • Aug 05 12:04
    Badidzetai edited #105
  • Aug 05 12:04
    Badidzetai edited #105
  • Aug 05 07:14
    mrtreasurer synchronize #101
  • Aug 01 07:20
    mikeheddes commented #101
  • Jul 31 08:56
    mrtreasurer synchronize #101
  • Jul 29 15:13
    Badidzetai commented #105
  • Jul 29 13:36
    darioizzo commented #105
  • Jul 29 13:35
    darioizzo commented #105
  • Jul 29 11:16
    mrtreasurer commented #101
  • Jul 29 11:14
    mrtreasurer commented #101
  • Jul 29 09:47
    mrtreasurer synchronize #101
  • Jul 29 09:47
    Badidzetai opened #105
  • Jul 29 09:35
    mrtreasurer synchronize #101
  • Jul 29 08:50
    mrtreasurer synchronize #101
  • Jul 29 08:37
    mrtreasurer synchronize #101
  • Jul 29 08:12
    mrtreasurer synchronize #101
  • Jul 26 15:08
    mrtreasurer synchronize #101
  • Jul 26 15:04
    mrtreasurer synchronize #101
  • Jul 26 14:01
    mrtreasurer synchronize #101
Krzysztof Nowak
@krzysztof
export BOOST_ROOT=/path/to/boost/root
anurag95
@anurag95
@kiryx My boost_1_57_0 folder is in /usr/local/ What do I have to write in the export command? Because I restarted bash, still it did not work with /usr/local/
joey001
@joey001
hello everyone, I always have problem installing pykep.
I configured my boost 1_57_0, python 2.7.3, 4.6.3, and cmake ../ works fine. But when I execute make, and it always abort in '''[ 82%] Building CXX object PyKEP/core/CMakeFiles/_core.dir/core.cpp.o
cc1plus: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See file:///usr/share/doc/gcc-4.6/README.Bugs for instructions.
Preprocessed source stored into /tmp/ccsVwogo.out file, please attach this to your bugreport.
make[2]: [PyKEP/core/CMakeFiles/_core.dir/core.cpp.o] Error 1
make[1]:
[PyKEP/core/CMakeFiles/_core.dir/all] Error 2
make: * [all] Error 2
'''
BTW, my system is ubuntu12.04 LTS
Hope somebody can give me a hint
joey001
@joey001
When I use ccmake, ```
The boost_Dir parameter is a little weird, but oth
  Boost_DATE_TIME_LIBRARY          /usr/local/lib/libboost_date_time.so         
 Boost_DATE_TIME_LIBRARY_DEBUG    /usr/local/lib/libboost_date_time.so         
 Boost_DATE_TIME_LIBRARY_RELEAS   /usr/local/lib/libboost_date_time.so         
 Boost_DIR                        Boost_DIR-NOTFOUND                           
 Boost_INCLUDE_DIR                /usr/local/include                           
 Boost_LIBRARY_DIR                /usr/local/lib                               
 Boost_LIBRARY_DIRS               /usr/local/lib                               
 Boost_PYTHON_LIBRARY             /usr/local/lib/libboost_python.so            
 Boost_PYTHON_LIBRARY_DEBUG       /usr/local/lib/libboost_python.so
Dario Izzo
@darioizzo
@joey001 gcc version you are using is probably too old. Update gcc or use clang.
joey001
@joey001
@darioizzo Looks updating gcc and g++ from 4.6 to 4.9 works .
Dario Izzo
@darioizzo
For all the students interested in the PyKEP project on ephemerides and solar electric propulsion, we have just updated the description, check it out at https://github.com/esa/pagmo/wiki/SOCIS-2015#project-ideas
Essentially, the novelties are: 1) for the ephemerides we want to wrap the spice toolkit from JPL, 2) For the Electric Solar Propoulsion we give a starting pointer in a paper from Purdue and 3) We have a new mentor from JAXA (the Japanese Space Agency) who will be following this project together with me from the European Space Agency.
Dario Izzo
@darioizzo
Maybe, instead of SPICE (http://naif.jpl.nasa.gov/naif/spiceconcept.html), we may use the C code here available: http://www.projectpluto.com/jpl_eph.htm to get the planetary ephemerides .... SPICE seems, after all, too complex and most of its functionalities (utilities) are not needed
Manikanta Reddy D
@manikantareddyd

I'm unable to figure this out. Can someone please help me with building pykep in ubuntu.

[ 78%] Building CXX object src/CMakeFiles/keplerian_toolbox.dir/third_party/libsgp4/Observer.cpp.o
[ 80%] Building CXX object src/CMakeFiles/keplerian_toolbox.dir/third_party/libsgp4/Eci.cpp.o
Linking CXX shared library libkeplerian_toolbox.so
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libboost_date_time.a(greg_month.o): relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libboost_date_time.a: error adding symbols: Bad value
collect2: error: ld returned 1 exit status
make[2]: [src/libkeplerian_toolbox.so] Error 1
make1:
[src/CMakeFiles/keplerian_toolbox.dir/all] Error 2
make: * [all] Error 2

Dario Izzo
@darioizzo
@manikantareddyd We have a travis VM building pykep succesfully using ubuntu, check it ....
My guess is that you are messing up with boosts
Dario Izzo
@darioizzo
@manikantareddyd It could also be just one of those ubuntu madness ... tro just building again (yes really!! it worked on the Travis VM)
Manikanta Reddy D
@manikantareddyd
Its working, but only if I force it to use with python2.7. It builds and links fine with python2.7.
Dario Izzo
@darioizzo
@manikantareddyd I have investigated the problem a bit and after also checking with @bluescarni the problem is with linking to a static python library rather than a dynamic one. This, together with the VM limitetd memory, may bring a library relocation error. One should always link to the python dynamic library, but on the VM this is not the case .... Long story short .. if this happens again, either restart the build (we have now reduced compilation memory so this should not happen often) or try to manually link to the dynamic library instead
hellno
@hellno
Hey all,
I'm having problems installing PyKep on OS X. Is it supported?! (as it's UNIX underneath the whole colorful-clicky GUI) I am able to make the project without errors, but it unfortunately fails at the make install step. Error message is: make: *** No rule to make targetinstall'. Stop.`
Dario Izzo
@darioizzo
@hellno Yes it is supported. You probably forgot, in CMAKE, to activate the option build PyKEP. Without this you are only building a static library that is not installed.
We probably should have the static library installed anyway in these cases.
Dario Izzo
@darioizzo
I am finished with the new planet structure. Check my latest pull request esa/pykep#27 . You will find there also a new object deriving from planets::base and interfacing with the JPL SPICE toolbox. This allows to compute precise ephemerides for all planets and moons in the solar system, at the cost of downloading first some files (kernels) needed by SPICE. I am now working on some examples and tutorials for the new structure.
hellno
@hellno

Hi,
the six examples are not running with the latest github version for me.

The error always looks something like this:
from PyKEP.planets import gtoc7 ImportError: No module named planets

Whereas from PyKEP import planet_gtoc7 is working.
Is this due to the recent change to the planets-class?
Am I missing something and this should work?
I wanted to start with the fixed, simple planet task.
If this is not working, should I begin with fixing the examples?
Thanks in advance =)

tonyVeco
@tonyVeco
I installed git, Cmake, and the boost libraries as required for pykep, then I followed exactly the instructions to install pykep, and up to the command line : make as explained in the page : https://esa.github.io/pykep/installation.html it is all ok, I obtained exactly the output it is showed. But when executing SUDO MAKE INSTALL the output I get is : " No rule to make target 'install'. What should I do?
Chris Andre
@ChrisAndre
Was 'BUILD PYKEP' selected in CMake?
tonyVeco
@tonyVeco
honestly I did not look at it because I thought it would have been automatically set to ON
then i should try the ccmake ../ again and set it?
tonyVeco
@tonyVeco
I am sorry but it is the first time I have to do with this kind of installation
Chris Andre
@ChrisAndre
Yes - the install target should install the python part of PyKEP in the proper place so that python will recognize it. Run ccmake again with 'BUILD PYKEP' on and continue from there.
tonyVeco
@tonyVeco
uff I made it, but I obtain then :

Unable to find the requested Boost libraries.

Boost version: 1.54.0

Boost include path: /usr/include

Could not find the following Boost libraries:

       boost_python3

Some (but not all) of the required Boost libraries were found. You may
need to install these additional Boost libraries. Alternatively, set
BOOST_LIBRARYDIR to the directory containing Boost libraries or BOOST_ROOT
to the location of Boost.
Call Stack (most recent call first):
CMakeLists.txt:64 (FIND_PACKAGE)

and I have installed the boost libraries..should I do it again?
Chris Andre
@ChrisAndre
I think that is one of the compiled libraries... it may be that only the header-only libraries were installed - how did you install the boost libraries?
Or you may have both python2 and python3- there are some extra instructions at the bottom of the installation page if that is the case
tonyVeco
@tonyVeco
No I put Ubuntu on a Virtual Machine to avoid any possible conflict with my python because I am working with it as Trainee at ESAC..
Chris Andre
@ChrisAndre
Ah - how did you install boost?
I've found that installing it through apt-get is the best way to go
tonyVeco
@tonyVeco
I followed another quite complicated way
I will try with apt-get then
Chris Andre
@ChrisAndre
Was it the ./bootstrap method? I've had issues with that
tonyVeco
@tonyVeco
yes it is
and it is the first time I have to do with such things so iam not used
if you have a link for the apt-get way
it would be great
Chris Andre
@ChrisAndre
Is it Ubuntu 14.04/10?
tonyVeco
@tonyVeco
14.04.2
Chris Andre
@ChrisAndre
sudo apt-get install libboost-all-dev should work
tonyVeco
@tonyVeco
ok