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

% Computer : n026.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:29:00 EDT 2023

% Result   : Unknown 179.15s 170.61s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : LAT368+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/0.12  % Command  : nanocop.sh %s %d
% 0.14/0.34  % Computer : n026.cluster.edu
% 0.14/0.34  % Model    : x86_64 x86_64
% 0.14/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.34  % Memory   : 8042.1875MB
% 0.14/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.14/0.34  % CPULimit : 300
% 0.14/0.34  % WCLimit  : 300
% 0.14/0.34  % DateTime : Thu May 18 14:18:45 EDT 2023
% 0.14/0.34  % CPUTime  : 
% 12.78/12.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.78/12.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.78/12.49  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 25.76/25.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.76/25.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.76/25.29  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 37.17/37.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.17/37.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.17/37.26  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 61.44/61.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.44/61.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.44/61.07  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 76.67/76.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 76.67/76.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 76.67/76.23  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 90.36/90.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 90.36/90.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 90.36/90.27  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 102.90/102.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 102.90/102.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 102.90/102.60  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 119.08/118.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 119.08/118.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 119.08/118.60  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 179.13/170.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 179.13/170.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 179.13/170.31  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 179.15/170.61  Timeout
%------------------------------------------------------------------------------