Re: [scipion-users] different endianness at runtime

[Carlos O. S. <co...@cn...>]

Dear all,

xmipp_volume_align with the frm option is a complicated script that 
starts at the shell, calls a C++ program, from the C++ we call python, 
which in its turn calls C++ again. Under one of these calls, the 
libraries seen must be different from those seen when compiling. But it 
is difficult to tell which one. As an alternative, if the volumes are 
more or less aligned you may use the local align option, instead of the 
frm (which is a fast global alignment).

Kind regards, Carlos Oscar

El 09/12/2020 a las 9:07, Juha Huiskonen escribió:
> Dear All,
>
> I am getting a strange error with xmipp_volume_align. Otherwise xmipp 
> binaries work ok.
>
> xmipp_volume_align --i1 
> Runs/016895_XmippProtAlignVolumeParticles/extra/refVolume.vol --i2 
> Runs/016895_XmippProtAlignVolumeParticles/extra/inputVolume.vol 
> --apply 
> Runs/016895_XmippProtAlignVolumeParticles/extra/inputVolumeAligned.vol 
> --mask circular -80 --frm  --copyGeo 
> Runs/016895_XmippProtAlignVolumeParticles/extra/transformation-matrix.txt
> 00030:   RuntimeError: FATAL: module compiled as little endian, but 
> detected different endianness at runtime
> 00031: 
> /projappl/project_2000637/apps/scipion/3.0/software/em/xmipp/bin/xmipp_volume_align: 
> line 3: 65819 Segmentation fault 
>  $XMIPP_HOME/bin/xmipp_volume_align_prog "$@"
> 00032:   Traceback (most recent call last):
>
> Any advice on how to make this run?
>
> Best wishes,
> Juha
>
>
> _______________________________________________
> scipion-users mailing list
> sci...@li...
> https://lists.sourceforge.net/lists/listinfo/scipion-users