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

% Computer : n005.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.62s 160.19s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.12/0.12  % Problem  : LAT357+4 : TPTP v8.1.2. Released v3.4.0.
% 0.12/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n005.cluster.edu
% 0.13/0.34  % Model    : x86_64 x86_64
% 0.13/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.34  % Memory   : 8042.1875MB
% 0.13/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.34  % CPULimit : 300
% 0.13/0.34  % WCLimit  : 300
% 0.13/0.34  % DateTime : Thu May 18 14:19:46 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 12.11/11.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.11/11.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.11/11.90  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 23.95/24.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.95/24.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.95/24.15  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 35.86/35.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.86/35.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.86/35.66  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 47.72/48.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.72/48.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.72/48.01  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 54.48/54.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.48/54.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.48/54.59  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 66.28/66.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 66.28/66.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.28/66.61  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 78.10/78.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 78.10/78.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 78.10/78.18  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 90.19/90.72  *** Overflow of the global/trail stack in spite of garbage collection!
% 90.19/90.72  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 90.19/90.72  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 106.73/107.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 106.73/107.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 106.73/107.55  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 160.56/159.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 160.56/159.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 160.56/159.95  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 160.62/160.19  Timeout
%------------------------------------------------------------------------------