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

% Computer : n026.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.52s 160.25s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : LAT376+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n026.cluster.edu
% 0.12/0.33  % Model    : x86_64 x86_64
% 0.12/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.33  % Memory   : 8042.1875MB
% 0.12/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.33  % CPULimit : 300
% 0.12/0.33  % WCLimit  : 300
% 0.12/0.33  % DateTime : Thu May 18 14:26:14 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 11.99/11.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.99/11.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.99/11.74  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 23.67/22.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.67/22.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.67/22.97  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 35.15/34.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.15/34.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.15/34.21  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 47.13/46.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.13/46.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.13/46.04  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 54.13/53.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.13/53.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.13/53.78  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 66.14/65.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 66.14/65.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.14/65.81  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 77.89/78.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 77.89/78.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 77.89/78.08  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 89.78/89.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 89.78/89.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 89.78/89.61  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 106.28/106.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 106.28/106.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 106.28/106.38  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 160.36/159.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 160.36/159.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 160.36/159.26  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 160.52/160.25  Timeout
%------------------------------------------------------------------------------