Error messages on n_calchep

Bug #1626964 reported by Azeem
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
CalcHEP
New
Undecided
Unassigned

Bug Description

I am doing calculation in MSSM_10.4 of proton proton scattering to yield sparticles. The diagrams are fine along with the symbolic calculations. Upon compiling "C" code, no n_calchep file is generated for numerical output.
I linked the file "aLib.a" present in MSSM_10.4/lib/ and got the following error message
VandP.c:Undefined reference to calcLambdas, Lambda1, Lambda3,6, deltaMb,Ml.
Kindly guide me on this matter.

Tags: error message
Revision history for this message
Alexander Pukhov (pukhov) wrote : Re: [Bug 1626964] [NEW] Error messages on n_calchep

I just testes MSSM_10.4 and it works.
If you make standard model implementation described in the manual it
should work.
If you try to link executable independently then please look at
sequence of liked files presented in
CalcHEP/sbin/ld_n. Namely $EXTLIB ( aLib.a in your case) should be
disposed after $CALCHEP/include/VandPgate.c .

$CC $CFLAGS -o n_calchep $cLib/n_calchep.o $cLib/num_c.a
$cLib/sqme_aux.$SO \
proclib_0.a proclib_*.a $CALCHEP/include/VandPgate.c $EXTLIB
$cLib/dynamic_me.a $cLib/serv.a $cLib/libSLHAplus.a \
$cLib/dummy.a $cLib/ntools.a $LX11 -lm $lDL -lpthread

Best
    Alexander Pukhov

On 09/23/2016 01:30 PM, Azeem wrote:
> Public bug reported:
>
> I am doing calculation in MSSM_10.4 of proton proton scattering to yield sparticles. The diagrams are fine along with the symbolic calculations. Upon compiling "C" code, no n_calchep file is generated for numerical output.
> I linked the file "aLib.a" present in MSSM_10.4/lib/ and got the following error message
> VandP.c:Undefined reference to calcLambdas, Lambda1, Lambda3,6, deltaMb,Ml.
> Kindly guide me on this matter.
>
> ** Affects: calchep
> Importance: Undecided
> Status: New
>
>
> ** Tags: error message
>

Revision history for this message
Azeem (plasmagr-78) wrote :
  • ld_n Edit (416 bytes, text/plain; charset=UTF-8; name="ld_n")

Dear Sir

I am sending you the ld_n file used by my system. It is exactly as in
the same format as you suggested. I have included MSSM_10.4 "alib.a" in
my bashrc path. Do i need to include some other file needed by calchep
on the path? Kindly guide me on this matter.

Kind regards

Azeem

On 26/09/2016 17:38, Alexander Pukhov wrote:
> I just testes MSSM_10.4 and it works.
> If you make standard model implementation described in the manual it
> should work.
> If you try to link executable independently then please look at
> sequence of liked files presented in
> CalcHEP/sbin/ld_n. Namely $EXTLIB ( aLib.a in your case) should be
> disposed after $CALCHEP/include/VandPgate.c .
>
>
> $CC $CFLAGS -o n_calchep $cLib/n_calchep.o $cLib/num_c.a
> $cLib/sqme_aux.$SO \
> proclib_0.a proclib_*.a $CALCHEP/include/VandPgate.c $EXTLIB
> $cLib/dynamic_me.a $cLib/serv.a $cLib/libSLHAplus.a \
> $cLib/dummy.a $cLib/ntools.a $LX11 -lm $lDL -lpthread
>
>
> Best
> Alexander Pukhov
>
>
> On 09/23/2016 01:30 PM, Azeem wrote:
>> Public bug reported:
>>
>> I am doing calculation in MSSM_10.4 of proton proton scattering to yield sparticles. The diagrams are fine along with the symbolic calculations. Upon compiling "C" code, no n_calchep file is generated for numerical output.
>> I linked the file "aLib.a" present in MSSM_10.4/lib/ and got the following error message
>> VandP.c:Undefined reference to calcLambdas, Lambda1, Lambda3,6, deltaMb,Ml.
>> Kindly guide me on this matter.
>>
>> ** Affects: calchep
>> Importance: Undecided
>> Status: New
>>
>>
>> ** Tags: error message
>>

Revision history for this message
Azeem (plasmagr-78) wrote :

Dear Alexander

I have a hunch that i have not linked lib/aLib.a properly in calchep. I
have defined the path to said library in my bashrc using export
LD_LIBRARY_PATH but it is not working. Do i need to do some other steps
to make sure that this library is accessible to calchep on run.

Kind regards

On 26/09/2016 17:38, Alexander Pukhov wrote:
> I just testes MSSM_10.4 and it works.
> If you make standard model implementation described in the manual it
> should work.
> If you try to link executable independently then please look at
> sequence of liked files presented in
> CalcHEP/sbin/ld_n. Namely $EXTLIB ( aLib.a in your case) should be
> disposed after $CALCHEP/include/VandPgate.c .
>
>
> $CC $CFLAGS -o n_calchep $cLib/n_calchep.o $cLib/num_c.a
> $cLib/sqme_aux.$SO \
> proclib_0.a proclib_*.a $CALCHEP/include/VandPgate.c $EXTLIB
> $cLib/dynamic_me.a $cLib/serv.a $cLib/libSLHAplus.a \
> $cLib/dummy.a $cLib/ntools.a $LX11 -lm $lDL -lpthread
>
>
> Best
> Alexander Pukhov
>
>
> On 09/23/2016 01:30 PM, Azeem wrote:
>> Public bug reported:
>>
>> I am doing calculation in MSSM_10.4 of proton proton scattering to yield sparticles. The diagrams are fine along with the symbolic calculations. Upon compiling "C" code, no n_calchep file is generated for numerical output.
>> I linked the file "aLib.a" present in MSSM_10.4/lib/ and got the following error message
>> VandP.c:Undefined reference to calcLambdas, Lambda1, Lambda3,6, deltaMb,Ml.
>> Kindly guide me on this matter.
>>
>> ** Affects: calchep
>> Importance: Undecided
>> Status: New
>>
>>
>> ** Tags: error message
>>

Revision history for this message
Azeem (plasmagr-78) wrote :

Dear Alexander

I have linked "alib.a" and "suspect.exe" in calchep using "Edit Linker". Now i am getting new errors related to the suspect.exe.

In function `_start':(.text+0x0): multiple definition of `_start'

In function `_init':(.init+0x0): multiple definition of `_init'

In function `data_start':(.data+0x8): multiple definition of `__dso_handle'

..............

relocation 0 has invalid symbol index 11-21; relocation 0 has invalid symbol index 7-9

Note that i am getting problems in getting the numerical output only in MSSM models(SM work fine). The symbolic calculations do fine.

Further do i need to modify model parameters or include LHAPDF(have not included it, just testing MSSM with calchep).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.