TSTP Solution File: LAT360+4 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : LAT360+4 : TPTP v8.1.2. Released v3.4.0.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n015.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:58 EDT 2023
% Result : Unknown 158.63s 156.04s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12 % Problem : LAT360+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.12 % Command : nanocop.sh %s %d
% 0.12/0.34 % Computer : n015.cluster.edu
% 0.12/0.34 % Model : x86_64 x86_64
% 0.12/0.34 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.34 % Memory : 8042.1875MB
% 0.12/0.34 % OS : Linux 3.10.0-693.el7.x86_64
% 0.12/0.34 % CPULimit : 300
% 0.12/0.34 % WCLimit : 300
% 0.12/0.34 % DateTime : Thu May 18 14:42:31 EDT 2023
% 0.12/0.34 % CPUTime :
% 11.88/11.64 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.88/11.64 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.88/11.64 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 23.58/23.03 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.58/23.03 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.58/23.03 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 35.14/34.20 *** Overflow of the global/trail stack in spite of garbage collection!
% 35.14/34.20 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.14/34.20 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 46.80/45.80 *** Overflow of the global/trail stack in spite of garbage collection!
% 46.80/45.80 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.80/45.80 Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 53.71/52.62 *** Overflow of the global/trail stack in spite of garbage collection!
% 53.71/52.62 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 53.71/52.62 Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 65.40/64.47 *** Overflow of the global/trail stack in spite of garbage collection!
% 65.40/64.47 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 65.40/64.47 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 76.90/75.76 *** Overflow of the global/trail stack in spite of garbage collection!
% 76.90/75.76 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 76.90/75.76 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 88.52/87.13 *** Overflow of the global/trail stack in spite of garbage collection!
% 88.52/87.13 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 88.52/87.13 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 105.15/103.44 *** Overflow of the global/trail stack in spite of garbage collection!
% 105.15/103.44 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 105.15/103.44 Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 158.51/155.37 *** Overflow of the global/trail stack in spite of garbage collection!
% 158.51/155.37 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 158.51/155.37 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 158.63/156.04 Timeout
%------------------------------------------------------------------------------