%------------------------------------------------------------------------------ % File : nanoCoP---2.0 % Problem : LAT296+4 : TPTP v8.1.2. Released v3.4.0. % Transfm : none % Format : tptp:raw % Command : nanocop.sh %s %d % Computer : n013.cluster.edu % Model : x86_64 x86_64 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 2.10GHz % Memory : 8042.1875MB % OS : Linux 3.10.0-693.el7.x86_64 % CPULimit : 300s % WCLimit : 300s % DateTime : Fri May 19 11:28:42 EDT 2023 % Result : Unknown 98.52s 102.13s % Output : None % Verified : % SZS Type : - % Comments : %------------------------------------------------------------------------------ %----No solution output by system %------------------------------------------------------------------------------ %----ORIGINAL SYSTEM OUTPUT % 0.06/0.12 % Problem : LAT296+4 : TPTP v8.1.2. Released v3.4.0. % 0.06/0.12 % Command : nanocop.sh %s %d % 0.13/0.34 % Computer : n013.cluster.edu % 0.13/0.34 % Model : x86_64 x86_64 % 0.13/0.34 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz % 0.13/0.34 % Memory : 8042.1875MB % 0.13/0.34 % OS : Linux 3.10.0-693.el7.x86_64 % 0.13/0.34 % CPULimit : 300 % 0.13/0.34 % WCLimit : 300 % 0.13/0.34 % DateTime : Thu May 18 14:03:11 EDT 2023 % 0.13/0.34 % CPUTime : % 5.90/5.95 *** Overflow of the global/trail stack in spite of garbage collection! % 5.90/5.95 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 5.90/5.95 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 11.94/12.28 *** Overflow of the global/trail stack in spite of garbage collection! % 11.94/12.28 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 11.94/12.28 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 17.88/18.50 *** Overflow of the global/trail stack in spite of garbage collection! % 17.88/18.50 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 17.88/18.50 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 23.72/24.62 *** Overflow of the global/trail stack in spite of garbage collection! % 23.72/24.62 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 23.72/24.62 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 27.74/29.08 *** Overflow of the global/trail stack in spite of garbage collection! % 27.74/29.08 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 27.74/29.08 Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes % 33.53/35.00 *** Overflow of the global/trail stack in spite of garbage collection! % 33.53/35.00 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 33.53/35.00 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 39.76/41.64 *** Overflow of the global/trail stack in spite of garbage collection! % 39.76/41.64 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 39.76/41.64 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 45.63/47.51 *** Overflow of the global/trail stack in spite of garbage collection! % 45.63/47.51 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 45.63/47.51 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 51.41/53.60 *** Overflow of the global/trail stack in spite of garbage collection! % 51.41/53.60 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 51.41/53.60 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 55.22/57.97 *** Overflow of the global/trail stack in spite of garbage collection! % 55.22/57.97 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 55.22/57.97 Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes % 61.14/64.16 *** Overflow of the global/trail stack in spite of garbage collection! % 61.14/64.16 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 61.14/64.16 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 67.05/70.40 *** Overflow of the global/trail stack in spite of garbage collection! % 67.05/70.40 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 67.05/70.40 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 73.15/76.76 *** Overflow of the global/trail stack in spite of garbage collection! % 73.15/76.76 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 73.15/76.76 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 98.44/101.45 *** Overflow of the global/trail stack in spite of garbage collection! % 98.44/101.45 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 98.44/101.45 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 98.52/102.13 Timeout %------------------------------------------------------------------------------