...
Therefore, it is imperative to make all bug reports as detailed as possible, with step-by-step information on repeating the error.
At a minimum, a good bug report should have the following information.
Jira
Simulator bugs are tracked using the SLIC Jira.
...
Information for the Bug Report
At a minimum, a good bug report should have the following information.
SLIC Version
The version is very important, because bugs (sometimes) get fixed in newer versions.
...
| No Format |
|---|
g++ |
And paste the last line into the report.
Run Log
On Unix, a command such as the following will create a log file.
| No Format |
|---|
slic [args] &> job_log.txt
|
Please attach this to the bug report.
Input StdHep File
It is vitally important that the StdHep file be listed in the bug report, because many types of errors can occur from malformed or incorrectly processed StdHep files.
If using a "standard" LCD StdHep file from the public data area, give the full FTP URL to that file.
| No Format |
|---|
ftp://ftp-lcd.slac.stanford.edu/lcd/ILC/ILC500/WW/cdcaug05/slcio/slic/panpyWW-0-500_SLIC_v1r9p4_cdcaug05.slcio |
If the StdHep file was produced by you, place it Place the file in an accessible location, such as a WWW directory or a publically readable AFS or SLAC NFS directory.List URL.
| No Format |
|---|
http://www.example.org/path/to/MyStdHepFile.stdhep
|
Additionally, include the name of the generator(s) (e.g. WHIZARD, PandoraPythia, GRACE, HERWIG, etc.) and the configuration(s) used to produce the file the full path to this file in the report.
Event Number or List
Oftentimes, errors will occur only on certain event numbers. Please list the event numbers that will reproduce the error in question.
...