error in prcoesses link

[Di LI]

Hi everyone,

In my .inp file, I set a reaction:

e + N    => e + e + N^+                            !   BOLSIG N -> N^+

which refers to 

IONIZATION

N -> N^+

 1.454000e+1

SPECIES: e / N

PROCESS: E + N -> E + E + N+, Ionization

PARAM.:  E = 14.54 eV

COMMENT: [e + N(4S) -> e + e + N(+,gnd), Ionization] Wang Y, Zatsarinny O, Bartschat K 2014

COMMENT: Phys. Rev. A 89 062714 extended up to 1000eV.

UPDATED: 2017-11-14 13:22:31

COLUMNS: Energy (eV) | Cross section (m2)

-----------------------------

 1.454000e+1 0.000000e+0

 1.750000e+1 1.362000e-21

 2.000000e+1 2.556500e-21

 2.500000e+1 4.786700e-21

But the solver always said cannot find the processes link N -> N^+

Could anyone help me to find where is the problem?

Thank you

[Francisco C. Parra-Rojas]

Hello,

I have also found this problem several times but I cannot give you a solution.

Perhaps your bolsig cross sections file has too many electron impact reactions. I believe there is a maximum number of processes in bolsig section.

Please, if you find the solution, don't hesitate to tell me

Best regards

--
You received this message because you are subscribed to the Google Groups "ZDPlasKin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zdplaskin+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/zdplaskin/8bf4109c-57c8-445b-9e76-18cbda91a40dn%40googlegroups.com.

[Di LI]

Hello Fran,

I have solved this problem. I forgot to claim N in bolsig section of .inp file. You can check that.

Now I have a new problem:

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

Backtrace for this error:

#0  0xffffffff

#1  0xffffffff

#2  0xffffffff

#3  0xffffffff

#4  0xffffffff

#5  0xffffffff

#6  0xffffffff

#7  0xffffffff

#8  0xffffffff

#9  0xffffffff

#10  0xffffffff

#11  0xffffffff

#12  0xffffffff

#13  0xffffffff

#14  0xffffffff

#15  0xffffffff

#16  0xffffffff

#17  0xffffffff

#18  0xffffffff

#19  0xffffffff

#20  0xffffffff

#21  0xffffffff

I don't know where is the problem located