%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : CSR097+3 : TPTP v8.1.2. Bugfixed v7.3.0.
% Transfm  : none
% Format   : tptp:raw
% Command  : nanocop.sh %s %d

% Computer : n027.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:04:33 EDT 2023

% Result   : Unknown 148.66s 149.67s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : CSR097+3 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.03/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n027.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 : Fri May 19 01:03:20 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 10.98/10.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.98/10.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.98/10.79  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 22.60/22.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.60/22.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.60/22.95  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 33.41/33.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.41/33.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.41/33.55  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 44.37/44.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.37/44.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.37/44.93  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 48.34/49.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.34/49.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.34/49.84  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 59.47/60.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 59.47/60.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 59.47/60.74  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 70.53/72.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 70.53/72.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 70.53/72.08  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 81.64/83.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 81.64/83.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 81.64/83.52  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 95.44/97.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 95.44/97.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 95.44/97.58  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 148.61/148.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 148.61/148.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 148.61/148.76  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 148.66/149.67  Timeout
%------------------------------------------------------------------------------