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

% Computer : n005.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 160.32s 157.16s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : LAT377+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n005.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:37:16 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 11.97/11.72  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.97/11.72  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.97/11.72  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 23.67/23.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.67/23.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.67/23.05  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 35.54/34.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.54/34.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.54/34.52  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 47.22/45.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.22/45.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.22/45.87  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 54.20/52.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.20/52.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.20/52.63  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 66.18/64.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 66.18/64.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.18/64.76  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 77.65/76.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 77.65/76.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 77.65/76.76  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 89.51/88.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 89.51/88.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 89.51/88.50  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 106.18/104.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 106.18/104.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 106.18/104.58  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 160.24/157.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 160.24/157.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 160.24/157.05  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 160.32/157.16  Timeout
%------------------------------------------------------------------------------