...
There are many possible sources of errors when the simulator crashes or exhibits "anomalous" or incorrect behavior. Also, some types of crashes, especially those that occur during batch jobs after a lot of events have been executed, can be difficult to producereproduce. Therefore, it is imperative to make all bug reports as detailed as possible, with including detailed platform configuration and step-by-step information on repeating the error.
...
This is preferable to an email, because the Jira automatically emails the SLIC project lead when a report is filed. (This saves time will save the developers from having to fill this out the bug report manually based on an email.)
...
The version is very important, because bugs (sometimes) can get fixed in newer versions.
...
And paste it into your bug report.
It is also printed when slic starts up.
Operating System.
On a Unix system, execute this command.
...
On Unix, a command such as the following will create a log file for your job.
| No Format |
|---|
slic [args] &> job_log.txt |
Please attach this to the bug report or paste in the relavent sections (if reasonably short).
Input StdHep File
It is vitally important that the StdHep file be listed specified in the bug report, because many types of errors can occur from malformed or incorrectly processed StdHep files.
...
Additionally, include the name of the generator(s) that were used (e.g. WHIZARD, PandoraPythia, GRACE, HERWIG, etc.) and the configuration(s) used to produce the file.
...
In the case where an LCIO file was produced, please point to it using the same conventions as listed given for the StdHep files.
Event Number or List
Oftentimes, errors will occur only on certain event numbers. Please list the event numbers that will reproduce produce the error in question.
Repeating the Error
...