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

% Computer : n001.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:56 EDT 2023

% Result   : Unknown 157.78s 156.05s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.12  % Problem  : LAT352+4 : TPTP v8.1.2. Released v3.4.0.
% 0.13/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.33  % Computer : n001.cluster.edu
% 0.13/0.33  % Model    : x86_64 x86_64
% 0.13/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.33  % Memory   : 8042.1875MB
% 0.13/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.33  % CPULimit : 300
% 0.13/0.33  % WCLimit  : 300
% 0.13/0.34  % DateTime : Thu May 18 15:08:42 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 11.82/11.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.82/11.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.82/11.63  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 23.38/22.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.38/22.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.38/22.83  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 34.80/34.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.80/34.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.80/34.14  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 46.21/45.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.21/45.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.21/45.56  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 52.94/52.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.94/52.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.94/52.40  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 64.73/64.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 64.73/64.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.73/64.61  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 76.53/76.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 76.53/76.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 76.53/76.07  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 88.13/87.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 88.13/87.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 88.13/87.21  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 104.38/103.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 104.38/103.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 104.38/103.19  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 157.75/155.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 157.75/155.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 157.75/155.23  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 157.78/156.05  Timeout
%------------------------------------------------------------------------------