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

View Problem - Process Solution

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

% Computer : n004.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:24 EDT 2023

% Result   : Unknown 109.10s 110.41s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.10  % Problem  : GRP637+4 : TPTP v8.1.2. Released v3.4.0.
% 0.00/0.10  % Command  : nanocop.sh %s %d
% 0.09/0.30  % Computer : n004.cluster.edu
% 0.09/0.30  % Model    : x86_64 x86_64
% 0.09/0.30  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.09/0.30  % Memory   : 8042.1875MB
% 0.09/0.30  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.09/0.30  % CPULimit : 300
% 0.09/0.30  % WCLimit  : 300
% 0.09/0.30  % DateTime : Fri May 19 01:35:44 EDT 2023
% 0.09/0.30  % CPUTime  : 
% 7.96/7.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.96/7.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.96/7.92  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 16.06/16.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.06/16.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.06/16.35  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 23.04/23.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.04/23.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.04/23.66  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 29.67/30.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.67/30.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.67/30.48  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 34.10/35.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.10/35.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.10/35.66  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 40.49/42.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.49/42.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.49/42.80  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 46.89/48.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.89/48.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.89/48.98  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 53.09/55.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 53.09/55.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 53.09/55.04  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 59.54/61.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 59.54/61.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 59.54/61.49  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 63.73/65.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 63.73/65.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 63.73/65.63  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 70.17/71.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 70.17/71.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 70.17/71.82  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 76.54/78.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 76.54/78.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 76.54/78.12  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 82.93/84.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 82.93/84.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 82.93/84.24  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 109.09/109.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 109.09/109.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 109.09/109.40  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 109.10/110.41  Timeout
%------------------------------------------------------------------------------