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

% Computer : n003.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:01 EDT 2023

% Result   : Unknown 158.59s 156.02s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.08/0.12  % Problem  : LAT371+4 : TPTP v8.1.2. Released v3.4.0.
% 0.08/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.34  % Computer : n003.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:32:53 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 11.84/11.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.84/11.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.84/11.60  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 22.73/22.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.73/22.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.73/22.24  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 34.32/34.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.32/34.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.32/34.22  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 46.14/45.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.14/45.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.14/45.96  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 53.10/52.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 53.10/52.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 53.10/52.61  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 64.78/64.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 64.78/64.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.78/64.45  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 76.49/75.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 76.49/75.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 76.49/75.95  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 88.13/87.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 88.13/87.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 88.13/87.20  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 104.60/103.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 104.60/103.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 104.60/103.26  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 158.58/155.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 158.58/155.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 158.58/155.77  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 158.59/156.02  Timeout
%------------------------------------------------------------------------------