back to new submissions

• check that PM has access
• project announcement

Pinged the PM on 2016-12-11 and got the following reply: ''I haven't had time to learn enough to deal with the repository for my codes on COIN-OR. Matt promised to help me with this. A lot of other codes developed by our team are getting ready to submit to QAPsolver.'' Since that is now like this for almost a year, I'll move this to the "inactive submissions".

• Project Description (short): solver for Quadratic Assignment Problem in Fortran
• Project Description (long): The QAP Solver project allows researchers that have interest in creating or improving QAP solvers to test new solution concepts and compare new solver performance with existing QAP solver codes. This project allows QAP researchers to contribute source or executable code of QAP bound calculators, exact solvers and heuristic solvers. Thus, this project helps QAP researchers to make comparisons between existing solving tools or to improve upon those tools, without having to waste time re-creating existing codes to mimic what other researchers have already accomplished. Ancillary goals of this project are (1) to encourage consideration of Reformulation Linearization Techniques for solving the QAP, (2) extending QAP research results to other Quadratic Assignment problems and (3) encouraging the use of Quadratic Assignment algorithms for solving real-world problems.
• Contributor: Peter Hahn, [email protected]
• Contact Date: October 2015, but there has also been attempts and discussions before (e.g., with Lou in May 2014)
• Handler: Stefan Vigerske
• Reviewer: Stefan Vigerske
• Sent instructions: (date)

• Received CSRO: yes (27th August 2015)
• Received DOL: yes (11th November 2015)
• OSI-approved license: Eclipse Public License The following is what Peter thinks what the license should cover: If a researcher uses a code from this project and publishes results using the downloaded project code, the researcher would be obligated to acknowledge in his/her published article the original source of the code, the fact that the project code was received from COIN-OR and describe how the project code was used. People improving a code from the project would be encouraged to submit improved versions to the project.

• Classified (Level 1-5): 3 (see ProjectCategories)

This is for the RLT-2 solver.

• README/LICENSE files: wrote a README.md file (9th November 2016), added LICENSE file (11th November 2015)
• Project Roadmap (Level 1 only): no (9th November 2015)
• AUTHORS/INSTALL files (Level 2 and above): created (9th November 2015)
• Code builds (Level 2 and above): yes (9th November 2015)
• Documentation (Level 3 and above): barely: just the README.md and an example input data (9th November 2015)
• Unit test (Level 4 and above): no (9th November 2015)
• Project binaries (Level 5): no (binary is problem-size-specific anyway) (9th November 2015)

• (Yes/No): Yes (11th November 2015)

• PM named: Peter M. Hahn (15th November 2015)
• PM familiar with Guidelines and Procedures for Project Management: (date)
  • Legal issues
  • Tracking contributions
  • Responding to bugs
  • Using SVN
  • Using Trac
  • Setting up a static Web page
  • Standard practices (versioning and release, build procedures)
• Parameters for project creation mailed to submission manager:

   # SVNPROJ  : QAPsolver
   # PROJDESC : solver for quadratic assignment problem
   # PM       : petermhahn
   # PM_EMAIL : <see above>

• PM subscribed to mailing list: (date)

• Code imported: (25th January 2016)

• PM given write access: (date)

• Trac page set up: (8th July 2016)

• XML page (projDesc.xml, see documentation in the file itself, which can be copied and adapted from here) set up: (25th January 2016)

• Project listed on projects list (howto following), with link to XML file: (26th January 2016)

  • Check out svn repo CoinWeb/projects.
  • Read projects.csv into your favourite spreadsheet (or text editor). Add an appropriate line for the new project and write out a revised projects.csv.
  • Run the command project_list_short.pl projects.csv. This'll produce the file index.html.new and modify the file coin-or-projects.xml.
  • Copy (or move) index.html.new to index.html.
  • Finally, commit the modified projects.csv, index.html, and coin-or-projects.xml.

• Project announcement: (date)

• PM invited for full membership of COIN-OR (contact coin secretary): (date)

• Moved this page to ArchivedChecklists: (date)