Re: Problem when running exgps example

Help: Forums, postings and threads

Forums, postings and threads

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.

Layout of the posting thread(s)

The posting threads can be shown with/without the text of the postings ("Inline depth"). In addition the depth of the thread can be controlled ("Outline depth"). For both cases several values are provided, which can be toggled. Note that the displayed values are those, which can be chosen, they do not correspond to the actual display status of the thread(s).

Add message

Add a new posting thread to this Forum

Show subscribers

Click "Show subscribers" to get the List of all subscribers, who receive e-mail from postings to this Forum, if they have not explictly unsubscribed from a posting thread. This includes:

Subscribers to the forum
Explicit subscribers to the posting or any of its ancestors
The author of the posting (if he has not unsubscribed)
The authors of any ancestor posting (if they have not unsubscribed)

Some browsers display old pages from the cache

Some browsers (e.g. Firefox) display a page from the cache even though the page has been updated. As a result, one may not get the latest messages in the forum's outline or the logon ID of the previous session appears on the upper right corner. If one suspects that he or she does not get the latest content of a page, try clearing up the personal data from the browser's cache as the following:

Tools -> Clear Private Data -> Clear Private Data (from browser Firefox)

Tools -> Delete Private Data (from browser Opera)

then reflesh the current page to get the latest content.

Details on "Inline depth" and "Outline depth"

Threads and the follow-up messages are numbered. There is one line per posting, normally starting with the posting number. The URLs of a posting and its responses reflect the depth of the follow-up postings. Watch the URLs to see how this is done. Depending on the chosen display options, the thread-display may be incomplete; the number of messages at the next level is, however, displayed, e.g. "…3 message(s)". You may not see all contributors unless you choose "All".

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.

Argument Default value Alternative Comment

1 0 1 no text / full text of posting

2 1 All text for level 1 only / text for All postings

Argument	Default value	Alternative		Comment
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.

Argument Default value Alternative Comment

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)

Argument	Default value	Alternative	Comment
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)

   Hello

 Then to sumup what had been said and done offline.

 This problem came from a syntax problem in the tuple booking string.
Instead of having "string Pname, double Energy, etc..." the booking string
appeared to be "std::string Pname, std::double Energy" which is definitely
not an agreed syntax. (The upper looks like as if having done some
automatic replace of string to std::string in the code...)

 We took the occasion to have a review of the AIDA related code. And then we :
- have fixed the upper
- have a good singleton pattern by :
    * privating constructor, destructor
  . * have a dispose method.
- use the dispose at end in the main.
- close the AIDA implementation properly (then osc_batch for me) in the EndOfRun.
- issuing message and protecting in case AIDA_createAnalysisFactory return 0 which
   may happen for good reasons.
- the same if the creation of the AIDA::ITree fails. Which may happen
   for exa if the requested file type is not supported by the implementation.
- do not have the histo and tuple factory as members since they are used
   locally. Check that they are deleted after usage.
- delete the plotter factory. (To have a good object balance at end).
- protect the usage of various pointers.
- supresse unused or not really needed methods.
- update the README concerning AIDA.

 In principle things hold now especially in case of multiple successive runs.
This is a very good test to check that things are done correctly concerning AIDA.
A lot of examples forget to delete or the tree or some factory or are not
in sync concerning creation / deletion of pointers in Begin/EndOfRun
and then crashes in case of doing multiple runs.

 The plotting had been checked with my osc_vis kit and is ok with my 
just released 16.8. A little advertisement here to say that there is new things
related to visualization and G4 in the 16.8. See my pages at :
    http://OpenScientist.lal.in2p3.fr
The pages had been strongly revisited to be "tutorial" and "how to" oriented now.
The AIDA, AIDA & Geant4 had been revisited in this way too.

 We have started to review also the exrdm, hadrontherapy, gammaray_telescope....
and it is interesting to note that the same "falltrap patterns" appear in
a lot of examples (not necessary written by the same people !). 
Then it may be a good idea also to have the upper "AIDA check list"
in head if having problems with other examples. At least I am going
to have a section with the upper in my new pages.

 Cheers

Guy