Simulation problem report form

Use this form to report problems in simulation codes or to make suggestions and feature requests. To report SLAC environment problems use the BaBar/SLAC computing environment problem report form. For other types of problem reporting and to track and edit problems see the generic BABAR REMEDY web page. Here is the REMEDY User's Guide.

Select the category for which you're reporting a problem or suggesting a change (if in doubt, select 'BBSIM General'):

BBSIM:

General

PEP

SVT

DCH

DRC

EMC

IFR

Digis:

General

SVT

DCH

DRC

EMC

IFR

Trig:

General

trgDC

trgEM

trgFrame

FcsData

FcsSim

TrgSim

gntrol

Gener:

General

BEGET

EvtGen

BMGAS

GELHAD

BHWIDE

BKQED

JETSET

KoralB

Geant4:

General

G4Global

G4Geom

Bogus

Utilities:

General

SimUtils

dbio

dbin

dbinPlain

euclid

XDR

STDHEP

UNT

Remedy

workdir

CERNLIB

CLHEP

Fast Sim:

General

Aslund

G4-based

What is your UnixId?

Software release number (if relevant)

Please enter a one-line problem description (used for summarizing all problems)

In answering the following questions, you may find it helpful to cut/paste parts of your command shell dialog from a terminal screen into this form.

Please describe the environment within which you observe the problem (e.g. copy the results of the "uname -a" command)

Please characterize the problem (include as much detail as you can which may prove useful for tracking it down and solving it)

Is this problem repeatable? (If so, could you describe the sequence (so that we my try to reproduce it ourselves?)

How severe do you consider this problem?

non-critical: The product, component or concept is working in general, but lacks features, has irritating behavior, does something wrong, or doesn't match its documentation
serious: The product, component or concept is not working properly. Problems that would otherwise be considered critical are rated serious when a workaround is known.
critical: The product, component or concept is completely non-operational. No workaround is known.

What is the suggested priority for solving this problem?

low: the problem should be solved in a future release.
medium: the problem should be solved in the next release.
high: a solution is needed as soon as possible.

What type of problem report is this?

Software: a bug in the software
Documentation: a problem with the documentation
Change request: a request for a new feature
Support: A support problem or a question

Derived from Torre's Simulation Problem Report form