TSTP Solution File: LAT372+4 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : LAT372+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:29:01 EDT 2023
% Result : Unknown 165.32s 158.00s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.06/0.11 % Problem : LAT372+4 : TPTP v8.1.2. Released v3.4.0.
% 0.06/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:21:00 EDT 2023
% 0.12/0.33 % CPUTime :
% 11.77/11.52 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.77/11.52 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.77/11.52 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 23.31/22.84 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.31/22.84 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.31/22.84 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 35.02/34.43 *** Overflow of the global/trail stack in spite of garbage collection!
% 35.02/34.43 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.02/34.43 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 46.98/46.01 *** Overflow of the global/trail stack in spite of garbage collection!
% 46.98/46.01 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.98/46.01 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 53.76/53.55 *** Overflow of the global/trail stack in spite of garbage collection!
% 53.76/53.55 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 53.76/53.55 Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 65.58/65.65 *** Overflow of the global/trail stack in spite of garbage collection!
% 65.58/65.65 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 65.58/65.65 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 77.09/76.77 *** Overflow of the global/trail stack in spite of garbage collection!
% 77.09/76.77 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 77.09/76.77 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 89.05/88.54 *** Overflow of the global/trail stack in spite of garbage collection!
% 89.05/88.54 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 89.05/88.54 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 105.46/105.28 *** Overflow of the global/trail stack in spite of garbage collection!
% 105.46/105.28 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 105.46/105.28 Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 165.28/157.72 *** Overflow of the global/trail stack in spite of garbage collection!
% 165.28/157.72 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 165.28/157.72 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 165.32/158.00 Timeout
%------------------------------------------------------------------------------