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

View Problem - Process Solution

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

% Computer : n006.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:47 EDT 2023

% Result   : Unknown 97.55s 101.90s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.10/0.12  % Problem  : LAT317+4 : TPTP v8.1.2. Released v3.4.0.
% 0.10/0.12  % Command  : nanocop.sh %s %d
% 0.13/0.33  % Computer : n006.cluster.edu
% 0.13/0.33  % Model    : x86_64 x86_64
% 0.13/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.33  % Memory   : 8042.1875MB
% 0.13/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.33  % CPULimit : 300
% 0.13/0.33  % WCLimit  : 300
% 0.13/0.33  % DateTime : Thu May 18 14:23:56 EDT 2023
% 0.13/0.33  % CPUTime  : 
% 6.16/6.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.16/6.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.16/6.12  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 12.08/12.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.08/12.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.08/12.30  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 18.00/18.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.00/18.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.00/18.44  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 23.99/24.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.99/24.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.99/24.75  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 27.95/28.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.95/28.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.95/28.97  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 33.74/34.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.74/34.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.74/34.96  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 39.57/41.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.57/41.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.57/41.14  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 45.34/47.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.34/47.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.34/47.38  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 51.37/53.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.37/53.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.37/53.74  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 55.35/58.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.35/58.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.35/58.05  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 60.96/63.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.96/63.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.96/63.77  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 66.67/70.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 66.67/70.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.67/70.09  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 72.47/76.33  *** Overflow of the global/trail stack in spite of garbage collection!
% 72.47/76.33  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 72.47/76.33  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 97.51/101.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 97.51/101.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 97.51/101.02  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 97.55/101.90  Timeout
%------------------------------------------------------------------------------