Code indexing in gitaly is broken and leads to code not being visible to the user. We work on the issue with highest priority.

Skip to content
Snippets Groups Projects
Commit ee8a32ba authored by gsell's avatar gsell
Browse files

ippl: use f2c'd version of FFTPACK

parent 1ffdff43
No related branches found
No related tags found
No related merge requests found
Loading
  • Developer

    @gsell, @adelmann, @snuverink_j could someone test whether Opal runs with the C version of fftpack? I get segfaults when space charge solver is used. Works again fine if I revert this commit.

  • snuverink_j @snuverink_j ·
    Developer

    @kraus: Is there a regression test, or do you have an input file?

  • Developer

    I used two different regression-tests (OpalRingTest and RingCyclotron-Tests), both crashed.

  • snuverink_j @snuverink_j ·
    Developer

    I confirm that I get the same segfault for both tests:

    [pc12290:01336] Signal: Segmentation fault (11)
    [pc12290:01336] Signal code:  (128)
    [pc12290:01336] Failing at address: (nil)
    [pc12290:01336] [ 0] /lib64/libpthread.so.0[0x3ab660f7e0]
    [pc12290:01336] [ 1] opal(rffti1_+0x1c)[0x25b43ac]
    [pc12290:01336] [ 2] opal(rffti_+0x24)[0x25b4374]
    [pc12290:01336] [ 3] opal(_ZN3FFTI11RCTransformLj3EdEC1ERK7NDIndexILj3EES5_RKbi+0x2c7)[0x13109d7]
    [pc12290:01336] [ 4] opal(_ZN16FFTPoissonSolverC1EP16UniformCartesianILj3EdEP19CenteredFieldLayoutILj3ES1_4CellENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESC_+0xf5c)[0x130428c]
    [pc12290:01336] [ 5] opal(_ZN11FieldSolver10initSolverEP13PartBunchBaseIdLj3EE+0x7c5)[0x1038d35]
    [pc12290:01336] [ 6] opal(_ZN8TrackRun16setupFieldsolverEv+0x1ef)[0x13efb6f]
    [pc12290:01336] [ 7] opal(_ZN8TrackRun21setupCyclotronTrackerEv+0xbb)[0x13f3c2b]
    [pc12290:01336] [ 8] opal(_ZN8TrackRun7executeEv+0x632)[0x13f5d02]
    [pc12290:01336] [ 9] opal(_ZNK10OpalParser7executeEP6ObjectRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x35)[0xff7f35]
  • adelmann :reminder_ribbon: @adelmann ·
    Owner

    Here a though: if we invest time into the fft, we should also consider to get rid of this dinosaur and use for example fftw or other high performance libs: http://www.fft.report/FFT_BoF.html

  • Developer

    FFTE: Fortran

    Spiral: commercial

    Pfft.py: python

    nb3dfft: OpenMP

    PsFFT, cusFFT: OpenMP

    AccFFT: uses FFTW

    P3DFFT: Fortran

    ParallelFFT: uses FFTW

    Edited by kraus
  • snuverink_j @snuverink_j ·
    Developer

    Let's continue this in a proper issue. I'll make one.

  • snuverink_j @snuverink_j

    mentioned in issue #188 (closed)

    ·

    mentioned in issue #188 (closed)

    Toggle commit list
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment