Rot_compress tutorial encounters Boost.Python.ArgumentError

Asked by Kahlil Fredrick Cui

Hi everyone!

I apologize ahead for this seemingly basic question.

I have just recently started learning esysparticle and was doing the tutorials on rot_compress.py. For starters I simply copied the code in the tutorials, but when I tried to run it I encountered the following error:

CSubLatticeControler::initMPI()
slave started at local/global rank 0 / 1
Traceback (most recent call last):
  File "rot_compress.py", line 84, in <module>
    meanR_scaling = True
Boost.Python.ArgumentError: Python argument types in
    FrictionPrms.__init__(FrictionPrms)
did not match C++ signature:
    __init__(_object*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > name, double A, double youngsModulus, double poissonsRatio, double dynamicMu, double staticMu, double damp, double cutoff, bool rigid, bool meanR_scaling)
    __init__(_object*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > name, double A, double youngsModulus, double poissonsRatio, double dynamicMu, double staticMu, double damp, double cutoff, bool rigid)
    __init__(_object*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > name, double A, double youngsModulus, double poissonsRatio, double dynamicMu, double staticMu, double damp, double cutoff)

My inputs are (which I simply copied from the tutorial):
sim.createInteractionGroup (
 FrictionPrms(
  name="friction",
  youngsModulus=100000.0,
  poissonsRatio=0.25,
  dynamicMu=0.4,
  staticMu=0.6,
  rigid = False,
  meanR_scaling = True
  )
)

The Esys version I'm using is v.2.3.1

I have tried adding the damp and cutoff parameters to FrictionPrms but it still gives me the same error. Any enlightenment you can shed on this problem is greatly appreciated.

Kahlil Cui

Question information

Language:
English Edit question
Status:
Expired
For:
ESyS-Particle Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Launchpad Janitor (janitor) said :
#1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.