How to effectively report an issue to us.

Frequently asked questions

How to effectively report an issue to us.

Postby zhouxinwei » Mon May 21, 2018 10:18 pm

It's crucial to provide detailed information so we can diagnose the issue quickly.

An inadequate reporting can be "MARS just crashed, please tell me why", or "MARS gave a segmentation fault, what's going on?". Such reporting is too vague, we don't know where to begin with.

A good reporting should include, as a guideline, the following information as the minimum:
1) symptom: provide a screenshot of the latest printout when the issue happened.
2) version number of MARS library, you can find it in the printout when MARS starts
3) the platform MARS is executed, such as Mac/Windows or Linux
4) whether the MARS executable is the debug version, optimized OpenMP version or MPI version. For the MPI version, provide the number of processors used.
5) if user developed features are involved, such files are also needed; if such files are hosted on GitLab, provide the repository name and the commit hash (e.g. 5f8ad822...)
6) input files to reproduce the issue.

Thanks for your understanding and sorry for the inconvenience.
zhouxinwei
 
Posts: 208
Joined: Thu Jul 09, 2015 7:12 pm

Return to FAQs

Who is online

Users browsing this forum: No registered users and 1 guest

cron