The final way to contribute to Opus is by providing test cases. While not a software contribution in the strict sense, this form of contribution is both important and precious, and deserves its own article.

A test case is usually an industrial example showing the way in which the platform can be used to solve a real-life problem. The manner and production of such a test case is detailed in the Contribution Guide, but in a nutshell, the process should be along the lines of:

- Clearly define the problem that will be solved, as it was in real life prior to resolution: context, quantity of interest, available data, expected difficulties and possible solutions, expected results and corresponding interpretation...

- Gather the real-life data used in a format usable by Opus (ideally CSV);

- Explain the method used to solve the real-life problem, from raw data to the final quantity of interest and its interpretation;

- Identify the corresponding features from Opus and formulate the associated series of commands;

- Check that the results obtained meet the real-life results.

At this point the test case is ready to be submitted to the consortium, and, if accepted, will either be uploaded as a webpage with associated data files and command checklist or a demo script directly available from a single command in the software itself.

Last Updated (Monday, 26 September 2011 00:20)