Challenge Overview
Project Overview
We have taken open source code call "NEMOH" from https://github.com/lawsonro3/Nemoh - and made a few tweaks and improvments. NEMOH is code for frequency-domain potential flow hydrodynamic.
Contest Objective
The goal of this competition is to discover and document any issues related to the assembly deliverable.
Any issues the reviewer missed and the bugs caused by the improvement of Nemoh (compiling, configuration, documentation, descriptive text) are in scope.
But we consider Technical bugs more valuable than Descriptive bugs.
In this bug hunt, the competitor who reports the most technical bugs wins. If competitors report the same amount of technical bugs, then who reports most descriptive bugs wins.
Contest Guidelines
The guidelines for this contest are given below:
- As issues are identified they need to be logged in Jira.
- Issues must include clear descriptions, test cases and steps to reproduce and expected vs. actual results in order to be counted.
- First competitor to find an issue gets credit, duplicates will not be counted.
- Reviewers will accept, reject or mark the issues as duplicate.
- Please DO take a look at the reported bugs, duplicated bugs cost your work time and the reviewer's time.
Important Notice:
You must also be the first person to report the issue and submit it while submission phase is open. JIRA will allow you to file issues before and after the submission phase, but these will NOT be counted.
Technologies
- Fortran
Provided Resources
Documentation Provided
The following documentation will be available in the contest forum:
- The previous assembly details. Please note the challenge scope, some competitors don't even read the scope!
- Dipoles Implementation in NEMOH - ���http://www.topcoder.com/challenge-details/30047583/?type=develop&noncache=true
- Source code - Provided in the forum
Contest Prize Eligibility
The submitter with the most accepted technical bugs will win the contest.
If competitors report the same amount of technical bugs, who reports the most descriptive bugs wins.
Final Submission Guidelines
Bug Report Format
For each report of a limitation or bug, we need the following information:
- Steps to reproduce, including any needed information
- Screen shots (if applicable)
- Expected results after the bug is fixed
- Current results, before the bug is fixed
Important Notice:
- If you do not properly document your bug reports, they will likely be rejected due to lack of information or documentation. Also, make sure your bug reports are reasonably general.
- If you submit the same bug that is seen in multiple screens, for instance, you will likely only get credit for the original bug report. The others will all be closed as duplicates.
Ticket Logging
You will log your tickets here: https://apps.topcoder.com/bugs/browse/DOEOW and when creating a bug you MUST select the NemohBugHunt 3 component. Bugs will not be counted if a selection is not made.
Scoring
The Scoring guidelines followed for the contest are given below:
- For scoring, the submitter with the most accepted bugs will win.
- For submitters who submit but don't take first, if they submit bugs that aren't covered in the first place submission, they will receive $5 for each techincal bug reported and $2 for descriptive bug reported.
Important Notice:
If two submitters submit the same bug report, the submitter who submitted the report first into JIRA will get credit for the bug.
Tips
Some of the tips helpful for the contest are:
- Submitting what is obviously the same issue multiple times with small variations will only annoy the reviewer that has to sort through all the issues and will only count as one issue anyway. If it's less obvious if it is the same issue or not, use your best judgment and the reviewers will do the same.
- Put an eye on the issues being submitted by other members to minimize the time you may be spending on duplicate efforts. Knowing what has already been reported will allow you to better focus your time on finding yet undiscovered issues.
- Double check your steps to reproduce and test cases to make sure they are clear. Make sure your steps include creation of any necessary data.
Submission Deliverables
You need report your issues in JIRA. Please submit a text file contains the bugs you reported to OR.
Final Submission
- For each member, the final submission should be uploaded to the Online Review Tool.
- You must not include any identifying information, such as your handle, in your submission. Your submission should be anonymous and you will be scored down in screening for not complying.