1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
|
<html>
<body BGCOLOR="FFFFFF">
<table border="0" width="100%">
<tr>
<td width="60%">
<h1> Questions and Bug Reports</h1>
</td>
<td width="40%"><img border="0" src="../images/headbang.gif" width="113" height="113"></td>
</tr>
</table>
The PETSc maintenance e-mail, <a href="mailto:petsc-maint@mcs.anl.gov">petsc-maint@mcs.anl.gov</a>, is intended for
users to <ul>
<li>report bugs, </li>
<li>ask for clarification, </li>
<li>ask for help in tracking down bugs, and </li>
<li>request new features within PETSc. </li>
</ul>
<p>We respond to almost all email the same day and many within the hour. <em>Please do not
send maintenance requests to the individual PETSc authors; all e-mail to</em> <strong><a href="mailto:petsc-maint@mcs.anl.gov">petsc-maint@mcs.anl.gov</a></strong> <em>is
automatically distributed to all of the PETSc authors, so our response time using this
address will be fastest. </em></p>
<p><!--webbot bot="PurpleText" PREVIEW="Do we want an archive of these available?
" -->Before
sending a bug report, please consult the following:<ul>
<li><a href="http://www.mcs.anl.gov/petsc/petsc-2/download/petsc-patches.html">patches</a>,</li>
<li><a href="troubleshooting.html">troubleshooting guide</a>, and </li>
<li><a href="faq.html">FAQ</a></li>
</ul>
<p>to determine whether a fix or work-around to the problem already exists. Also, see the
chapter "Hints
for Performance Tuning" in the PETSc users manual for guidelines on achieving
good efficiency within PETSc codes. </p>
<p align="center"><strong><font size="4">Guidelines for Bug Reports</font></strong></p>
<p>The more information that you convey about a bug, the easier it will be for us to
target the problem. We suggest providing the following information: <ul type="disc">
<li>If the problem involves installation, send <u><strong>the entire log file from
running make</strong></u>.</li>
<li>Machine type: (e.g., sun4) </li>
<li>OS Version: (run <em>uname -a</em> to get the version number) </li>
<li>PETSc Version: (run PETSc program with -v, or look in <a href="petscversion.h">include/petscversion.h</a>)
</li>
<li>MPI implementation: (e.g., MPICH, LAM, IBM, SGI) </li>
<li>Compiler: (e.g., Gnu C, Gnu g++, native C) </li>
<li>Probable PETSc component: (for example, <em>Mat, Vec, Draw, KSP</em>, etc.) </li>
<li>Problem description: Also, please cut and paste error messages from the compiler,
program, etc.</li>
</ul>
<p align="center"><strong><big>Tracking Down Problems</big></strong></p>
<p>If you report a bug or problem and we are unable to figure out the problem by email, we
may be able to offer remote help via <a href="http://www.microsoft.com/netmeeting">Microsoft's
Netmeeting Software</a>. For this service you must have access to a PC running
Windows and have installed the free Netmeeting software. If the problem involves a
Unix system, you must be able to telnet or rlogin into the Unix machine from the Windows
machine. If the problem involves the PETSc graphics, you must be running a X-server on the
PC such as Exceed or X-win.</p>
<p>Netmeeting allows us to remotely run commands on your machine as you watch. Usually,
due to our complete knowledge of PETSc and experience with many different machine
architectures, we can track down many problems quickly. <u><strong>We can provide help
only based on our availability; we may not have time to provide this service, and we can
only try this after several iterations of email have failed to track down the problem</strong></u>.
</body>
</html>
|
