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

% Computer : n021.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:57 EDT 2023

% Result   : Unknown 160.19s 158.30s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.06/0.12  % Problem  : LAT356+4 : TPTP v8.1.2. Released v3.4.0.
% 0.06/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n021.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:34:05 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 11.85/11.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.85/11.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.85/11.64  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 23.28/22.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.28/22.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.28/22.71  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 34.67/34.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.67/34.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.67/34.12  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 46.02/45.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.02/45.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.02/45.51  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 52.84/52.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.84/52.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.84/52.49  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 66.32/66.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 66.32/66.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.32/66.23  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 77.95/77.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 77.95/77.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 77.95/77.96  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 89.40/89.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 89.40/89.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 89.40/89.21  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 105.64/105.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 105.64/105.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 105.64/105.18  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 160.17/157.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 160.17/157.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 160.17/157.39  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 160.19/158.30  Timeout
%------------------------------------------------------------------------------