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

% Computer : n013.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:53 EDT 2023

% Result   : Unknown 157.23s 154.85s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.12  % Problem  : LAT340+4 : TPTP v8.1.2. Released v3.4.0.
% 0.11/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n013.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:33:58 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 10.59/10.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.59/10.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.59/10.44  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 22.17/21.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.17/21.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.17/21.79  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 34.89/34.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.89/34.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.89/34.40  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 46.58/45.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.58/45.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.58/45.81  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 54.79/53.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.79/53.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.79/53.95  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 64.28/63.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 64.28/63.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.28/63.37  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 77.01/75.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 77.01/75.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 77.01/75.87  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 89.52/88.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 89.52/88.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 89.52/88.20  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 106.01/104.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 106.01/104.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 106.01/104.38  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 157.15/154.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 157.15/154.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 157.15/154.26  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 157.23/154.85  Timeout
%------------------------------------------------------------------------------