Previously, I confronted a similar issue to the one under discussion in this thread Error in GCR Scoring. Despite implementing the recommended updates, the issue persists. Kindly find the attached input file and error files for your review and further assistance. GCR_TEST_04005.err (806 Bytes) GCR_TEST.inp (1.8 KB)
The issue (logical error preventing range evaluation in an actually legitimate scenario), which was identical indeed to the one reported in this thread last year, has been spotted and fixed.
The fix shall be included in the next public release of the code.