%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : LAT362+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:58 EDT 2023

% Result   : Unknown 162.59s 160.10s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.06/0.12  % Problem  : LAT362+4 : TPTP v8.1.2. Released v3.4.0.
% 0.06/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:14:29 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 11.77/11.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.77/11.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.77/11.59  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 23.46/22.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.46/22.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.46/22.99  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 35.16/34.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.16/34.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.16/34.36  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 46.51/45.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.51/45.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.51/45.46  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 52.89/52.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.89/52.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.89/52.10  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 63.87/62.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 63.87/62.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 63.87/62.63  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 76.95/76.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 76.95/76.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 76.95/76.19  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 90.38/89.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 90.38/89.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 90.38/89.88  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 107.45/106.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 107.45/106.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 107.45/106.87  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 162.47/159.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 162.47/159.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 162.47/159.95  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 162.59/160.10  Timeout
%------------------------------------------------------------------------------