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

% Computer : n016.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:55 EDT 2023

% Result   : Unknown 140.43s 140.19s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.11  % Problem  : LAT349+4 : TPTP v8.1.2. Released v3.4.0.
% 0.00/0.12  % Command  : nanocop.sh %s %d
% 0.11/0.33  % Computer : n016.cluster.edu
% 0.11/0.33  % Model    : x86_64 x86_64
% 0.11/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.11/0.33  % Memory   : 8042.1875MB
% 0.11/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.11/0.33  % CPULimit : 300
% 0.11/0.33  % WCLimit  : 300
% 0.11/0.33  % DateTime : Thu May 18 14:42:03 EDT 2023
% 0.11/0.33  % CPUTime  : 
% 9.08/8.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.08/8.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.08/8.99  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 18.50/18.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.50/18.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.50/18.70  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 27.55/27.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.55/27.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.55/27.66  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 37.53/37.94  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.53/37.94  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.53/37.94  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 43.40/44.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.40/44.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.40/44.32  Peak sizes were: global stack 127896 kbytes, trail stack 4200 kbytes
% 52.90/54.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.90/54.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.90/54.02  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 62.15/63.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 62.15/63.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 62.15/63.14  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 73.42/74.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 73.42/74.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 73.42/74.39  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 89.89/90.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 89.89/90.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 89.89/90.78  Peak sizes were: global stack 127896 kbytes, trail stack 4200 kbytes
% 140.38/140.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 140.38/140.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 140.38/140.05  Peak sizes were: global stack 127896 kbytes, trail stack 4200 kbytes
% 140.43/140.19  Timeout
%------------------------------------------------------------------------------