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

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : LAT282+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:38 EDT 2023

% Result   : Unknown 102.38s 104.97s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.06/0.12  % Problem  : LAT282+4 : TPTP v8.1.2. Released v3.4.0.
% 0.06/0.12  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n006.cluster.edu
% 0.13/0.34  % Model    : x86_64 x86_64
% 0.13/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.34  % Memory   : 8042.1875MB
% 0.13/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.34  % CPULimit : 300
% 0.13/0.34  % WCLimit  : 300
% 0.13/0.34  % DateTime : Thu May 18 14:17:41 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 6.03/6.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.03/6.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.03/6.02  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 11.26/11.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.26/11.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.26/11.65  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 18.49/18.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.49/18.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.49/18.71  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 25.57/25.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.57/25.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.57/25.80  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 29.87/30.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.87/30.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.87/30.36  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 36.77/37.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.77/37.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.77/37.92  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 43.25/44.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.25/44.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.25/44.87  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 49.68/52.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.68/52.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.68/52.09  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 55.92/58.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.92/58.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.92/58.15  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 60.33/62.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.33/62.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.33/62.57  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 66.67/69.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 66.67/69.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.67/69.56  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 71.62/74.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 71.62/74.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 71.62/74.50  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 76.60/79.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 76.60/79.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 76.60/79.64  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 102.32/104.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 102.32/104.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 102.32/104.83  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 102.38/104.96  Timeout
%------------------------------------------------------------------------------