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

% Computer : n028.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:54 EDT 2023

% Result   : Unknown 145.30s 145.59s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : LAT344+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n028.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:13:25 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 12.02/11.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.02/11.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.02/11.83  Peak sizes were: global stack 128032 kbytes, trail stack 4192 kbytes
% 23.19/23.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.19/23.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.19/23.48  Peak sizes were: global stack 128032 kbytes, trail stack 4192 kbytes
% 32.31/32.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.31/32.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.31/32.97  Peak sizes were: global stack 128032 kbytes, trail stack 4192 kbytes
% 41.68/42.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.68/42.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.68/42.49  Peak sizes were: global stack 128032 kbytes, trail stack 4192 kbytes
% 47.43/48.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.43/48.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.43/48.29  Peak sizes were: global stack 128032 kbytes, trail stack 4192 kbytes
% 57.40/58.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 57.40/58.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 57.40/58.67  Peak sizes were: global stack 128032 kbytes, trail stack 4192 kbytes
% 66.60/68.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 66.60/68.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.60/68.27  Peak sizes were: global stack 128032 kbytes, trail stack 4192 kbytes
% 76.96/78.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 76.96/78.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 76.96/78.61  Peak sizes were: global stack 128032 kbytes, trail stack 4192 kbytes
% 92.83/94.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 92.83/94.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 92.83/94.32  Peak sizes were: global stack 128032 kbytes, trail stack 4192 kbytes
% 145.25/145.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 145.25/145.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 145.25/145.02  Peak sizes were: global stack 128032 kbytes, trail stack 4192 kbytes
% 145.30/145.59  Timeout
%------------------------------------------------------------------------------