FAST-MAP: Bug Reports Instructions Page

How to send us bug reports

Since FAST-MAP is in its earliest releases, problems may arise. The following is the protocol that we would find most helpful in the event that problems arise.

In the event that FAST-MAP crashes while processing a gel, save the error message to a log file by typing:
```
	>> diary off
```
Email the log file "/gel/output/program.log" where "program" is the program that crashed to skng@cs.cmu.edu.
In the event that FAST-MAP failed silently without crashing, we can catch the error by re-running the program again, but calling the program name appended with either "_GEL" or "_STU", depending on whether it is a gel or study we are running the program on. For example, if
```
	>> allele_call STUDY1
```
failed, we can catch the error by re-running the program
```
	>> allele_call_STU STUDY1
```
For another example, if
```
	>> image_call GEL3
```
failed, then re-run with
```
	>> image_call_GEL GEL3
```
The second run will normally generate an error message and crash instead of failing silently. The error message generated will be tremenduously helpful in debugging the program. Again, save the error message to a log file by typing:
```
	>> diary off
```
and then email the log file "/gel/output/program.log" to skng@cs.cmu.edu. Currently, the programs that generate log files are: prep_call, image_call, allele_call, allele_results, and allele_printout.

Back to FAST-MAP