How to get timely support
Please inform us when you know you will need our help well in advance, preferably as soon as possible, e.g. when you write the project proposal.
General idea about bugs
We know they are bugs. The important question is “Where are the bugs that affect you ?”
First, the help
A help should be displayed by running the executable with the --help
option.
Read it if there is one you can reasonably understand
You are kindly reminded to:
- read the constantly updated documentation
- check you are correctly using the executables
Otherwise report it
If:
- no documentation is displayed
- or the documentation is not understandable
then this is a bug that should be reported!
Then, the bug report or help request
The only reasonable way to report a bug is to give enough information to reproduce it. If you run an executable, it all boils down to this, in decreasing order of preference:
- if we share an access on the same machine
- email us
- the full command line
- with the directory where it was launched from
- preferably also with the path of the file where the standard output and error have been redirected
- and with as little irrelevant information as possible
- and make sure we have read access to at least the input files and the standard output and error
- email us
- otherwise email us
- the full command line
- with, in decreasing order of preference:
- if they are not too big, the input files
- if they are too big and if it is possible to make a subset, a subset of the input files
- otherwise at least the last 50 lines of output.
- and with as little irrelevant information as possible.
Failure to do as above will almost always result in your report being deprioritised!
If you do not update your sources, you will also have to:
- give us the revision you are having a problem with
- and expect not to get any help for free if we find it is too old.