%------------------------------------------------------------------------------ % File : nanoCoP---2.0 % Problem : LAT314+4 : TPTP v8.1.2. Released v3.4.0. % Transfm : none % Format : tptp:raw % Command : nanocop.sh %s %d % Computer : n008.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:46 EDT 2023 % Result : Unknown 99.47s 101.95s % Output : None % Verified : % SZS Type : - % Comments : %------------------------------------------------------------------------------ %----No solution output by system %------------------------------------------------------------------------------ %----ORIGINAL SYSTEM OUTPUT % 0.03/0.12 % Problem : LAT314+4 : TPTP v8.1.2. Released v3.4.0. % 0.03/0.13 % Command : nanocop.sh %s %d % 0.13/0.34 % Computer : n008.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:33:44 EDT 2023 % 0.13/0.34 % CPUTime : % 6.12/6.11 *** Overflow of the global/trail stack in spite of garbage collection! % 6.12/6.11 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 6.12/6.11 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 12.13/12.33 *** Overflow of the global/trail stack in spite of garbage collection! % 12.13/12.33 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 12.13/12.33 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 18.15/18.61 *** Overflow of the global/trail stack in spite of garbage collection! % 18.15/18.61 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 18.15/18.61 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 24.05/24.66 *** Overflow of the global/trail stack in spite of garbage collection! % 24.05/24.66 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 24.05/24.66 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 28.18/29.18 *** Overflow of the global/trail stack in spite of garbage collection! % 28.18/29.18 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 28.18/29.18 Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes % 34.06/34.98 *** Overflow of the global/trail stack in spite of garbage collection! % 34.06/34.98 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 34.06/34.98 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 40.19/41.44 *** Overflow of the global/trail stack in spite of garbage collection! % 40.19/41.44 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 40.19/41.44 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 46.07/47.46 *** Overflow of the global/trail stack in spite of garbage collection! % 46.07/47.46 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 46.07/47.46 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 52.14/53.87 *** Overflow of the global/trail stack in spite of garbage collection! % 52.14/53.87 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 52.14/53.87 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 56.23/58.16 *** Overflow of the global/trail stack in spite of garbage collection! % 56.23/58.16 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 56.23/58.16 Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes % 62.16/64.03 *** Overflow of the global/trail stack in spite of garbage collection! % 62.16/64.03 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 62.16/64.03 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 68.18/70.40 *** Overflow of the global/trail stack in spite of garbage collection! % 68.18/70.40 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 68.18/70.40 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 74.01/76.49 *** Overflow of the global/trail stack in spite of garbage collection! % 74.01/76.49 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 74.01/76.49 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 99.45/101.40 *** Overflow of the global/trail stack in spite of garbage collection! % 99.45/101.40 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 99.45/101.40 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 99.47/101.95 Timeout %------------------------------------------------------------------------------