2. At least one of the participants presenting a solution must be registered for and attending the 23rd IMR.
3. Each contest entry must be a compressed archived file (created using ZIP, TAR or GZ) which contains:
4. The maximum size of mesh that can be entered into the contest is 20 million elements. In addition, the maximum file size for the uploaded tarball is 1 GB. While we expect that members of the community generate meshes bigger than this regularly, the limit is to make the logistics of judging the entries feasible for the organizing committee.
5. To submit an entry into the Meshing Contest, go to www.openconf.org/IMR23, and click on 3the link "Make Submission", Enter all the data and make sure to specify "Meshing Contest" at the top. After completing this form, make sure to go back to www.openconf.org/IMR23 and upload your contest submission file (ZIP, TAR, or GZ).
6. The deadline for submitting an entry is September 30, 2014.
7. If participants wish to be considered for the Meshing Maestro Award they must also present a contribution in the poster session. For more information visit the Poster Session page.
8. The awards will be announced at the banquet on October 14, 2014.
9. The best solution will be judged by this year's Meshing Roundtable Steering Committee. The committee will select the best solution taking into account the novelty of the approach, the complexity of the discretization, the quality of the mesh, and the usability of the proposed solution.
The following people/companies entered the meshing contest. View their entries by clicking on the links below. Thank you to all that participants.
Entry #1: Travis Carrigan, Michael Remotigue, Carolyn Woeber - Pointwise, Inc.
Zip Files for Mesh (588 MB)
Entry #3: Frederic Alauzet, Nicolas Barral, Adrien Loseille -
Zip Files for Mesh (149 MB)
Entry #4: James Clement, Tim Tautges, Scott Canann - CD-adapco
Zip Files for Mesh (1.1 GB)
Entry #5:Nick Leppard - BAE Systems
Zip Files for Mesh (834 MB)
[an error occurred while processing this directive] [an error occurred while processing this directive]