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

View Problem - Process Solution

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

% Computer : n026.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 99.41s 105.21s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.12  % Problem  : GRP619+4 : TPTP v8.1.2. Released v3.4.0.
% 0.00/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n026.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 02:01:18 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 5.95/5.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.95/5.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.95/5.99  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 14.26/14.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.26/14.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.26/14.57  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 21.09/21.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.09/21.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.09/21.45  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 26.61/27.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.61/27.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.61/27.31  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 30.37/31.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.37/31.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.37/31.92  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 35.86/37.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.86/37.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.86/37.74  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 41.63/44.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.63/44.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.63/44.21  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 47.37/50.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.37/50.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.37/50.40  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 52.98/56.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.98/56.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.98/56.55  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 56.81/61.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 56.81/61.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 56.81/61.07  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 62.84/67.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 62.84/67.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 62.84/67.31  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 68.53/73.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 68.53/73.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 68.53/73.29  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 74.27/79.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 74.27/79.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 74.27/79.50  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 99.36/104.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 99.36/104.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 99.36/104.23  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 99.41/105.21  Timeout
%------------------------------------------------------------------------------