|Message: Re: where is the particle table?||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
On Tue, 31 May 2016 02:35:28 GMT, yicong liu wrote:
> Sorry, my English is not good enough, I should ask that I want to know > all string parameters of particle table. Such as "e-" represents > electron , "e+" represents positron and so on. Thanks for your help
In addition to Peter's answer, here's some additional guidance. You should only need the particle name strings if you are using macro (UI) commands. Within code, it is better to get and use the particle pointers directly (string comparisons take a lot of CPU time). For an electron, you would use
... G4ParticleDefinition* eminus = G4Electron::Definition(); G4ParticleDefinition* eplus = G4Positron::Definition();
and so on. These objects are singletons, so the pointers are guaranteed to be unique, and constant, across your whole job.
-- Michael Kelsey