%------------------------------------------------------------------------------ % File : nanoCoP---2.0 % Problem : LAT321+4 : TPTP v8.1.2. Released v3.4.0. % Transfm : none % Format : tptp:raw % Command : nanocop.sh %s %d % Computer : n006.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:48 EDT 2023 % Result : Unknown 97.70s 101.94s % Output : None % Verified : % SZS Type : - % Comments : %------------------------------------------------------------------------------ %----No solution output by system %------------------------------------------------------------------------------ %----ORIGINAL SYSTEM OUTPUT % 0.00/0.11 % Problem : LAT321+4 : TPTP v8.1.2. Released v3.4.0. % 0.00/0.12 % Command : nanocop.sh %s %d % 0.12/0.33 % Computer : n006.cluster.edu % 0.12/0.33 % Model : x86_64 x86_64 % 0.12/0.33 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz % 0.12/0.33 % Memory : 8042.1875MB % 0.12/0.33 % OS : Linux 3.10.0-693.el7.x86_64 % 0.12/0.33 % CPULimit : 300 % 0.12/0.33 % WCLimit : 300 % 0.12/0.33 % DateTime : Thu May 18 14:23:11 EDT 2023 % 0.12/0.33 % CPUTime : % 6.10/6.14 *** Overflow of the global/trail stack in spite of garbage collection! % 6.10/6.14 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 6.10/6.14 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 12.00/12.13 *** Overflow of the global/trail stack in spite of garbage collection! % 12.00/12.13 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 12.00/12.13 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 17.90/18.51 *** Overflow of the global/trail stack in spite of garbage collection! % 17.90/18.51 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 17.90/18.51 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 23.84/24.71 *** Overflow of the global/trail stack in spite of garbage collection! % 23.84/24.71 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 23.84/24.71 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 27.65/28.80 *** Overflow of the global/trail stack in spite of garbage collection! % 27.65/28.80 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 27.65/28.80 Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes % 33.33/34.80 *** Overflow of the global/trail stack in spite of garbage collection! % 33.33/34.80 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 33.33/34.80 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 38.92/40.93 *** Overflow of the global/trail stack in spite of garbage collection! % 38.92/40.93 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 38.92/40.93 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 44.70/47.38 *** Overflow of the global/trail stack in spite of garbage collection! % 44.70/47.38 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 44.70/47.38 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 50.71/53.73 *** Overflow of the global/trail stack in spite of garbage collection! % 50.71/53.73 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 50.71/53.73 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 54.65/58.07 *** Overflow of the global/trail stack in spite of garbage collection! % 54.65/58.07 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 54.65/58.07 Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes % 60.58/64.01 *** Overflow of the global/trail stack in spite of garbage collection! % 60.58/64.01 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 60.58/64.01 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 66.54/70.32 *** Overflow of the global/trail stack in spite of garbage collection! % 66.54/70.32 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 66.54/70.32 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 72.41/76.41 *** Overflow of the global/trail stack in spite of garbage collection! % 72.41/76.41 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 72.41/76.41 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 97.61/101.29 *** Overflow of the global/trail stack in spite of garbage collection! % 97.61/101.29 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 97.61/101.29 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 97.70/101.94 Timeout %------------------------------------------------------------------------------