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

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : GRP647+4 : TPTP v8.1.2. Released v3.4.0.
% Transfm  : none
% Format   : tptp:raw
% Command  : nanocop.sh %s %d

% Computer : n011.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:26 EDT 2023

% Result   : Unknown 110.46s 113.54s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.08/0.13  % Problem  : GRP647+4 : TPTP v8.1.2. Released v3.4.0.
% 0.08/0.14  % Command  : nanocop.sh %s %d
% 0.15/0.33  % Computer : n011.cluster.edu
% 0.15/0.33  % Model    : x86_64 x86_64
% 0.15/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.15/0.33  % Memory   : 8042.1875MB
% 0.15/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.15/0.33  % CPULimit : 300
% 0.15/0.33  % WCLimit  : 300
% 0.15/0.33  % DateTime : Fri May 19 01:49:42 EDT 2023
% 0.15/0.33  % CPUTime  : 
% 7.00/7.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.00/7.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.00/7.00  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 13.76/14.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.76/14.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.76/14.07  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 20.37/21.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.37/21.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.37/21.19  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 27.02/28.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.02/28.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.02/28.48  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 31.15/33.33  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.15/33.33  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.15/33.33  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 38.88/40.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.88/40.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.88/40.98  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 45.48/48.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.48/48.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.48/48.17  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 52.12/55.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.12/55.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.12/55.47  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 58.42/62.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.42/62.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.42/62.49  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 62.73/66.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 62.73/66.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 62.73/66.76  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 69.51/73.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 69.51/73.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 69.51/73.32  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 110.41/113.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 110.41/113.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 110.41/113.47  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 110.46/113.54  Timeout
%------------------------------------------------------------------------------