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

View Problem - Process Solution

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

% Computer : n018.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:19 EDT 2023

% Result   : Unknown 93.92s 102.01s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : GRP620+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n018.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 : Fri May 19 01:44:02 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 5.72/5.73  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.72/5.73  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.72/5.73  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 11.33/11.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.33/11.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.33/11.93  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 16.90/18.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.90/18.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.90/18.09  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 22.44/24.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.44/24.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.44/24.31  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 26.20/28.86  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.20/28.86  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.20/28.86  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 31.60/34.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.60/34.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.60/34.61  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 37.22/40.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.22/40.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.22/40.91  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 42.74/47.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.74/47.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.74/47.14  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 48.34/53.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.34/53.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.34/53.32  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 52.09/57.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.09/57.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.09/57.87  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 57.59/63.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 57.59/63.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 57.59/63.67  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 63.21/70.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 63.21/70.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 63.21/70.04  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 68.78/76.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 68.78/76.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 68.78/76.17  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 93.87/101.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 93.87/101.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 93.87/101.17  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 93.92/102.01  Timeout
%------------------------------------------------------------------------------