MPS problem names often arbitrary
Many of the instances do not come with a meaningful problem name. We have had this discussion before, and I know that there are arguments against changing those names, e.g., because a longer/shorter name may influence the solver's memory layout.
However, I would like to quickly draw your attention, @bzfgamra, @bzfgleix, @bzfschuc , to this issue. The following occurrences are just the first 6 lines of a
grep "Problem name" results/*.out command, I did not do manual
sorting, and already four different problems become apparent:
- paths in a problem name
- simply "MPS" in a problem name
- missing problem name
- Identical problem names for different instances.
results/revised-submissions-v2.50v-10.scip.4threads.14400s.M610.out: Problem name : serge_bisaillon/50v_10.lp.gz results/revised-submissions-v2.aflow40b.scip.4threads.14400s.M610.out: Problem name : _MPS_ results/revised-submissions-v2.comp01-2idx.scip.4threads.14400s.M610.out: Problem name : (null) results/revised-submissions-v2.comp11-2idx.scip.4threads.14400s.M610.out: Problem name : (null) results/revised-submissions-v2.drayage-0-10.scip.4threads.14400s.M610.out: Problem name : ChassisSolved results/revised-submissions-v2.drayage-0-11.scip.4threads.14400s.M610.out: Problem name : ChassisSolved