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

View Problem - Process Solution

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

% Computer : n020.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:28:42 EDT 2023

% Result   : Unknown 101.32s 104.19s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.08/0.13  % Problem  : LAT297+4 : TPTP v8.1.2. Released v3.4.0.
% 0.08/0.14  % Command  : nanocop.sh %s %d
% 0.14/0.35  % Computer : n020.cluster.edu
% 0.14/0.35  % Model    : x86_64 x86_64
% 0.14/0.35  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.35  % Memory   : 8042.1875MB
% 0.14/0.35  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.14/0.35  % CPULimit : 300
% 0.14/0.35  % WCLimit  : 300
% 0.14/0.35  % DateTime : Thu May 18 14:19:07 EDT 2023
% 0.14/0.36  % CPUTime  : 
% 6.55/6.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.55/6.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.55/6.52  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 12.79/12.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.79/12.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.79/12.58  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 19.31/19.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.31/19.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.31/19.07  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 25.93/26.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.93/26.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.93/26.46  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 30.21/31.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.21/31.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.21/31.48  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 36.61/37.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.61/37.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.61/37.68  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 42.48/43.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.48/43.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.48/43.39  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 48.39/49.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.39/49.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.39/49.60  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 54.23/55.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.23/55.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.23/55.81  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 58.43/60.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.43/60.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.43/60.49  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 64.16/66.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 64.16/66.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.16/66.08  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 70.11/72.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 70.11/72.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 70.11/72.48  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 76.04/78.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 76.04/78.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 76.04/78.67  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 101.31/103.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 101.31/103.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 101.31/103.51  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 101.32/104.19  Timeout
%------------------------------------------------------------------------------