Index: /issm/trunk-jpl/test/NightlyRun/test2001.m =================================================================== --- /issm/trunk-jpl/test/NightlyRun/test2001.m (revision 15026) +++ /issm/trunk-jpl/test/NightlyRun/test2001.m (revision 15027) @@ -9,17 +9,9 @@ %% define loading history -md.timestepping.start_time=2400000; %2,400 kyr +md.timestepping.start_time=2400000; %2,400 kyr :: EVALUATION TIME +% to get rid of default final_time: make sure final_time>start_time md.timestepping.final_time=2500000; %2,500 kyr -% In order to run Ivins1999 benchmarks, for now, we do things manually as follows: -% 1. numtimes is fixed to be five -% 2. final_time given above is hard-coded in "GiaDeflectionCorex.cpp" -% 3. evaluation time = start_time -% 4. define new load times, according to the chosen evaluation time (care that general load history is not altered). This is really important, because of #1 and also becasue of the fact that futre loading times are not recognized. -% 5. Ice thickness assoiated with evaluation time is actually the same at final_time md.geometry.thickness=[... - [md.geometry.thickness*0.0; 0.0],... - [md.geometry.thickness/2.0; 0.1],... - [md.geometry.thickness; 0.2],... - [md.geometry.thickness; 1.0],... + [md.geometry.thickness; 0.0],... [md.geometry.thickness; md.timestepping.start_time],... ]; Index: /issm/trunk-jpl/test/NightlyRun/test2051.m =================================================================== --- /issm/trunk-jpl/test/NightlyRun/test2051.m (revision 15026) +++ /issm/trunk-jpl/test/NightlyRun/test2051.m (revision 15027) @@ -11,10 +11,4 @@ md.timestepping.start_time=2002100; % after 2 kyr of deglaciation md.timestepping.final_time=2500000; % 2,500 kyr -% In order to run Ivins1999 benchmarks, for now, we do things manually as follows: -% 1. numtimes is fixed to be five -% 2. final_time given above is hard-coded in "GiaDeflectionCorex.cpp" -% 3. evaluation time = start_time -% 4. define new load times, according to the chosen evaluation time (care that general load history is not altered). This is really important, because of #1 and also becasue of the fact that futre loading times are not recognized. -% 5. Ice thickness assoiated with evaluation time is actually the same at final_time md.geometry.thickness=[... [md.geometry.thickness*0.0; 0.0],... Index: /issm/trunk-jpl/test/NightlyRun/test2052.m =================================================================== --- /issm/trunk-jpl/test/NightlyRun/test2052.m (revision 15026) +++ /issm/trunk-jpl/test/NightlyRun/test2052.m (revision 15027) @@ -11,10 +11,4 @@ md.timestepping.start_time=2005100; % after 5 kyr of deglaciation md.timestepping.final_time=2500000; % 2,500 kyr -% In order to run Ivins1999 benchmarks, for now, we do things manually as follows: -% 1. numtimes is fixed to be five -% 2. final_time given above is hard-coded in "GiaDeflectionCorex.cpp" -% 3. evaluation time = start_time -% 4. define new load times, according to the chosen evaluation time (care that general load history is not altered). This is really important, because of #1 and also becasue of the fact that futre loading times are not recognized. -% 5. Ice thickness assoiated with evaluation time is actually the same at final_time md.geometry.thickness=[... [md.geometry.thickness*0.0; 0.0],... Index: /issm/trunk-jpl/test/NightlyRun/test2053.m =================================================================== --- /issm/trunk-jpl/test/NightlyRun/test2053.m (revision 15026) +++ /issm/trunk-jpl/test/NightlyRun/test2053.m (revision 15027) @@ -11,10 +11,4 @@ md.timestepping.start_time=2010100; % after 10 kyr of deglaciation md.timestepping.final_time=2500000; % 2,500 kyr -% In order to run Ivins1999 benchmarks, for now, we do things manually as follows: -% 1. numtimes is fixed to be five -% 2. final_time given above is hard-coded in "GiaDeflectionCorex.cpp" -% 3. evaluation time = start_time -% 4. define new load times, according to the chosen evaluation time (care that general load history is not altered). This is really important, because of #1 and also becasue of the fact that futre loading times are not recognized. -% 5. Ice thickness assoiated with evaluation time is actually the same at final_time md.geometry.thickness=[... [md.geometry.thickness*0.0; 0.0],... Index: /issm/trunk-jpl/test/NightlyRun/test2061.m =================================================================== --- /issm/trunk-jpl/test/NightlyRun/test2061.m (revision 15026) +++ /issm/trunk-jpl/test/NightlyRun/test2061.m (revision 15027) @@ -11,10 +11,4 @@ md.timestepping.start_time=2002100; % after 2 kr of deglaciation md.timestepping.final_time=2500000; %2,500 kyr -% In order to run Ivins1999 benchmarks, for now, we do things manually as follows: -% 1. numtimes is fixed to be five -% 2. final_time given above is hard-coded in "GiaDeflectionCorex.cpp" -% 3. evaluation time = start_time -% 4. define new load times, according to the chosen evaluation time (care that general load history is not altered). This is really important, because of #1 and also becasue of the fact that futre loading times are not recognized. -% 5. Ice thickness assoiated with evaluation time is actually the same at final_time md.geometry.thickness=[... [md.geometry.thickness*0.0; 0.0],... Index: /issm/trunk-jpl/test/NightlyRun/test2062.m =================================================================== --- /issm/trunk-jpl/test/NightlyRun/test2062.m (revision 15026) +++ /issm/trunk-jpl/test/NightlyRun/test2062.m (revision 15027) @@ -11,10 +11,4 @@ md.timestepping.start_time=2005100; % after 5 kr of deglaciation md.timestepping.final_time=2500000; %2,500 kyr -% In order to run Ivins1999 benchmarks, for now, we do things manually as follows: -% 1. numtimes is fixed to be five -% 2. final_time given above is hard-coded in "GiaDeflectionCorex.cpp" -% 3. evaluation time = start_time -% 4. define new load times, according to the chosen evaluation time (care that general load history is not altered). This is really important, because of #1 and also becasue of the fact that futre loading times are not recognized. -% 5. Ice thickness assoiated with evaluation time is actually the same at final_time md.geometry.thickness=[... [md.geometry.thickness*0.0; 0.0],... Index: /issm/trunk-jpl/test/NightlyRun/test2063.m =================================================================== --- /issm/trunk-jpl/test/NightlyRun/test2063.m (revision 15026) +++ /issm/trunk-jpl/test/NightlyRun/test2063.m (revision 15027) @@ -11,10 +11,4 @@ md.timestepping.start_time=2010100; % after 10 kyr of deglaciation md.timestepping.final_time=2500000; %2,500 kyr -% In order to run Ivins1999 benchmarks, for now, we do things manually as follows: -% 1. numtimes is fixed to be five -% 2. final_time given above is hard-coded in "GiaDeflectionCorex.cpp" -% 3. evaluation time = start_time -% 4. define new load times, according to the chosen evaluation time (care that general load history is not altered). This is really important, because of #1 and also becasue of the fact that futre loading times are not recognized. -% 5. Ice thickness assoiated with evaluation time is actually the same at final_time md.geometry.thickness=[... [md.geometry.thickness*0.0; 0.0],... Index: /issm/trunk-jpl/test/NightlyRun/test2071.m =================================================================== --- /issm/trunk-jpl/test/NightlyRun/test2071.m (revision 15026) +++ /issm/trunk-jpl/test/NightlyRun/test2071.m (revision 15027) @@ -11,15 +11,8 @@ md.timestepping.start_time=0.3; % for t \approx 0 kyr : to get eleastic response! md.timestepping.final_time=2500000; % 2,500 kyr -% In order to run Ivins1999 benchmarks, for now, we do things manually as follows: -% 1. numtimes is fixed to be five -% 2. final_time given above is hard-coded in "GiaDeflectionCorex.cpp" -% 3. evaluation time = start_time -% 4. define new load times, according to the chosen evaluation time (care that general load history is not altered). This is really important, because of #1 and also becasue of the fact that futre loading times are not recognized. -% 5. Ice thickness assoiated with evaluation time is actually the same at final_time md.geometry.thickness=[... [md.geometry.thickness*0.0; 0.0],... [md.geometry.thickness/2.0; 0.1],... [md.geometry.thickness; 0.2],... - [md.geometry.thickness; 0.25],... [md.geometry.thickness; md.timestepping.start_time],... ]; Index: /issm/trunk-jpl/test/NightlyRun/test2072.m =================================================================== --- /issm/trunk-jpl/test/NightlyRun/test2072.m (revision 15026) +++ /issm/trunk-jpl/test/NightlyRun/test2072.m (revision 15027) @@ -11,15 +11,8 @@ md.timestepping.start_time=1000.3; % for t \approx 1 kyr md.timestepping.final_time=2500000; % 2,500 kyr -% In order to run Ivins1999 benchmarks, for now, we do things manually as follows: -% 1. numtimes is fixed to be five -% 2. final_time given above is hard-coded in "GiaDeflectionCorex.cpp" -% 3. evaluation time = start_time -% 4. define new load times, according to the chosen evaluation time (care that general load history is not altered). This is really important, because of #1 and also becasue of the fact that futre loading times are not recognized. -% 5. Ice thickness assoiated with evaluation time is actually the same at final_time md.geometry.thickness=[... [md.geometry.thickness*0.0; 0.0],... [md.geometry.thickness/2.0; 0.1],... [md.geometry.thickness; 0.2],... - [md.geometry.thickness; 0.25],... [md.geometry.thickness; md.timestepping.start_time],... ]; Index: /issm/trunk-jpl/test/NightlyRun/test2073.m =================================================================== --- /issm/trunk-jpl/test/NightlyRun/test2073.m (revision 15026) +++ /issm/trunk-jpl/test/NightlyRun/test2073.m (revision 15027) @@ -11,15 +11,8 @@ md.timestepping.start_time=2400000; % for t \approx \infty md.timestepping.final_time=2500000; % 2,500 kyr -% In order to run Ivins1999 benchmarks, for now, we do things manually as follows: -% 1. numtimes is fixed to be five -% 2. final_time given above is hard-coded in "GiaDeflectionCorex.cpp" -% 3. evaluation time = start_time -% 4. define new load times, according to the chosen evaluation time (care that general load history is not altered). This is really important, because of #1 and also becasue of the fact that futre loading times are not recognized. -% 5. Ice thickness assoiated with evaluation time is actually the same at final_time md.geometry.thickness=[... [md.geometry.thickness*0.0; 0.0],... [md.geometry.thickness/2.0; 0.1],... [md.geometry.thickness; 0.2],... - [md.geometry.thickness; 0.25],... [md.geometry.thickness; md.timestepping.start_time],... ]; Index: /issm/trunk-jpl/test/NightlyRun/test2081.m =================================================================== --- /issm/trunk-jpl/test/NightlyRun/test2081.m (revision 15026) +++ /issm/trunk-jpl/test/NightlyRun/test2081.m (revision 15027) @@ -11,15 +11,8 @@ md.timestepping.start_time=0.3; % for t \approx 0 kyr : to get eleastic response! md.timestepping.final_time=2500000; % 2,500 kyr -% In order to run Ivins1999 benchmarks, for now, we do things manually as follows: -% 1. numtimes is fixed to be five -% 2. final_time given above is hard-coded in "GiaDeflectionCorex.cpp" -% 3. evaluation time = start_time -% 4. define new load times, according to the chosen evaluation time (care that general load history is not altered). This is really important, because of #1 and also becasue of the fact that futre loading times are not recognized. -% 5. Ice thickness assoiated with evaluation time is actually the same at final_time md.geometry.thickness=[... [md.geometry.thickness*0.0; 0.0],... [md.geometry.thickness/2.0; 0.1],... [md.geometry.thickness; 0.2],... - [md.geometry.thickness; 0.25],... [md.geometry.thickness; md.timestepping.start_time],... ]; Index: /issm/trunk-jpl/test/NightlyRun/test2082.m =================================================================== --- /issm/trunk-jpl/test/NightlyRun/test2082.m (revision 15026) +++ /issm/trunk-jpl/test/NightlyRun/test2082.m (revision 15027) @@ -11,15 +11,8 @@ md.timestepping.start_time=1000.3; % for t \approx 1 kyr md.timestepping.final_time=2500000; % 2,500 kyr -% In order to run Ivins1999 benchmarks, for now, we do things manually as follows: -% 1. numtimes is fixed to be five -% 2. final_time given above is hard-coded in "GiaDeflectionCorex.cpp" -% 3. evaluation time = start_time -% 4. define new load times, according to the chosen evaluation time (care that general load history is not altered). This is really important, because of #1 and also becasue of the fact that futre loading times are not recognized. -% 5. Ice thickness assoiated with evaluation time is actually the same at final_time md.geometry.thickness=[... [md.geometry.thickness*0.0; 0.0],... [md.geometry.thickness/2.0; 0.1],... [md.geometry.thickness; 0.2],... - [md.geometry.thickness; 0.25],... [md.geometry.thickness; md.timestepping.start_time],... ]; Index: /issm/trunk-jpl/test/NightlyRun/test2083.m =================================================================== --- /issm/trunk-jpl/test/NightlyRun/test2083.m (revision 15026) +++ /issm/trunk-jpl/test/NightlyRun/test2083.m (revision 15027) @@ -11,15 +11,8 @@ md.timestepping.start_time=2400000; % for t \approx \infty md.timestepping.final_time=2500000; % 2,500 kyr -% In order to run Ivins1999 benchmarks, for now, we do things manually as follows: -% 1. numtimes is fixed to be five -% 2. final_time given above is hard-coded in "GiaDeflectionCorex.cpp" -% 3. evaluation time = start_time -% 4. define new load times, according to the chosen evaluation time (care that general load history is not altered). This is really important, because of #1 and also becasue of the fact that futre loading times are not recognized. -% 5. Ice thickness assoiated with evaluation time is actually the same at final_time md.geometry.thickness=[... [md.geometry.thickness*0.0; 0.0],... [md.geometry.thickness/2.0; 0.1],... [md.geometry.thickness; 0.2],... - [md.geometry.thickness; 0.25],... [md.geometry.thickness; md.timestepping.start_time],... ];