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

% Result   : Unknown 169.61s 168.35s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.12  % Problem  : LAT364+4 : TPTP v8.1.2. Released v3.4.0.
% 0.11/0.13  % Command  : nanocop.sh %s %d
% 0.12/0.34  % Computer : n013.cluster.edu
% 0.12/0.34  % Model    : x86_64 x86_64
% 0.12/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.34  % Memory   : 8042.1875MB
% 0.12/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.34  % CPULimit : 300
% 0.12/0.34  % WCLimit  : 300
% 0.12/0.34  % DateTime : Thu May 18 14:36:45 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 11.45/11.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.45/11.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.45/11.27  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 22.80/22.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.80/22.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.80/22.63  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 34.06/33.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.06/33.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.06/33.97  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 48.55/48.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.55/48.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.55/48.58  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 56.37/56.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 56.37/56.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 56.37/56.45  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 69.47/69.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 69.47/69.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 69.47/69.89  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 82.93/83.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 82.93/83.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 82.93/83.71  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 95.44/96.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 95.44/96.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 95.44/96.35  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 112.53/113.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 112.53/113.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 112.53/113.21  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 169.54/168.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 169.54/168.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 169.54/168.29  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 169.61/168.35  Timeout
%------------------------------------------------------------------------------