%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : LAT378+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:29:03 EDT 2023

% Result   : Unknown 168.07s 168.09s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : LAT378+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/0.12  % Command  : nanocop.sh %s %d
% 0.13/0.33  % Computer : n016.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:51:04 EDT 2023
% 0.13/0.33  % CPUTime  : 
% 13.88/13.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.88/13.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.88/13.59  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 28.02/27.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.02/27.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.02/27.35  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 44.20/43.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.20/43.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.20/43.95  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 55.79/56.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.79/56.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.79/56.05  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 62.23/62.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 62.23/62.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 62.23/62.44  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 73.33/73.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 73.33/73.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 73.33/73.17  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 84.48/84.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 84.48/84.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 84.48/84.58  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 95.60/96.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 95.60/96.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 95.60/96.05  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 111.82/112.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 111.82/112.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 111.82/112.21  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 168.05/167.33  *** Overflow of the global/trail stack in spite of garbage collection!
% 168.05/167.33  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 168.05/167.33  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 168.07/168.09  Timeout
%------------------------------------------------------------------------------