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

View Problem - Process Solution

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

% Computer : n017.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:46 EDT 2023

% Result   : Unknown 98.56s 102.08s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : LAT313+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.34  % Computer : n017.cluster.edu
% 0.12/0.34  % Model    : x86_64 x86_64
% 0.12/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.34  % Memory   : 8042.1875MB
% 0.12/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.34  % CPULimit : 300
% 0.12/0.34  % WCLimit  : 300
% 0.12/0.34  % DateTime : Thu May 18 13:26:35 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 6.06/6.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.06/6.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.06/6.10  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 12.12/12.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.12/12.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.12/12.31  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 17.98/18.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.98/18.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.98/18.44  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 23.89/24.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.89/24.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.89/24.68  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 27.85/29.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.85/29.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.85/29.07  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 33.73/34.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.73/34.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.73/34.99  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 39.73/41.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.73/41.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.73/41.40  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 45.56/47.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.56/47.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.56/47.47  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 51.47/53.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.47/53.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.47/53.77  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 55.36/58.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.36/58.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.36/58.06  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 61.33/64.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.33/64.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.33/64.12  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 67.28/70.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 67.28/70.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 67.28/70.41  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 73.26/76.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 73.26/76.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 73.26/76.67  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 98.50/101.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 98.50/101.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 98.50/101.31  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 98.52/102.08  Timeout
%------------------------------------------------------------------------------