TSTP Solution File: GRP650+4 by nanoCoP---2.0

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : GRP650+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:16:27 EDT 2023

% Result   : Unknown 108.58s 111.35s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.13/0.13  % Problem  : GRP650+4 : TPTP v8.1.2. Released v3.4.0.
% 0.13/0.14  % Command  : nanocop.sh %s %d
% 0.14/0.34  % Computer : n013.cluster.edu
% 0.14/0.34  % Model    : x86_64 x86_64
% 0.14/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.34  % Memory   : 8042.1875MB
% 0.14/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.14/0.34  % CPULimit : 300
% 0.14/0.34  % WCLimit  : 300
% 0.14/0.34  % DateTime : Fri May 19 01:55:11 EDT 2023
% 0.14/0.34  % CPUTime  : 
% 7.91/7.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.91/7.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.91/7.83  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 15.46/15.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.46/15.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.46/15.98  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 23.55/24.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.55/24.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.55/24.64  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 30.84/32.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.84/32.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.84/32.25  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 35.62/37.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.62/37.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.62/37.09  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 42.07/43.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.07/43.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.07/43.85  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 48.28/49.86  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.28/49.86  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.28/49.86  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 54.64/56.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.64/56.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.64/56.25  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 61.23/62.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.23/62.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.23/62.70  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 65.25/67.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 65.25/67.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 65.25/67.44  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 71.25/73.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 71.25/73.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 71.25/73.52  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 77.11/79.62  *** Overflow of the global/trail stack in spite of garbage collection!
% 77.11/79.62  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 77.11/79.62  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 83.09/85.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 83.09/85.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 83.09/85.93  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 108.55/110.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 108.55/110.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 108.55/110.81  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 108.58/111.35  Timeout
%------------------------------------------------------------------------------