source: issm/trunk/src/m/solutions/jpl/diagnostic.m@ 4028

Last change on this file since 4028 was 4028, checked in by Eric.Larour, 15 years ago

Thinking about shuffling analysis_type, sub_analysis_type and solution_type

File size: 973 bytes
Line 
1function md=diagnostic(md);
2%DIAGNOSTIC - compute the velocity field of a model
3%
4% Usage:
5% md=diagnostic(md)
6%
7 %timing
8 t1=clock;
9
10 solution_type=DiagnosticAnalysisEnum;
11 analysis_types=[DiagnosticHorizAnalysisEnum,DiagnosticVertAnalysisEnum,DiagnosticStokesAnalysisEnum,DiagnosticHutterAnalysisEnum,SlopecomputeAnalysisEnum];
12
13 displaystring(md.verbose,'%s',['create fem model']);
14 femmodel=CreateFemModel(md,solution_type,analysis_types);
15
16 %compute solution
17 if ~femmodel.parameters.QmuAnalysis,
18 if femodel.parameters.control_analysis,
19
20 %launch core of control solution.
21 md.results.DiagnosticAnalysis=control_core(femmodel);
22
23 else,
24
25 %launch core of diagnostic solution.
26 md.results.DiagnosticAnalysis=diagnostic_core(femmodel);
27
28 end
29 else
30 %launch dakota driver for diagnostic core solution
31 Qmu(femmodel);
32 end
33
34 %stop timing
35 t2=clock;
36 displaystring(md.verbose,'\n%s\n',['solution converged in ' num2str(etime(t2,t1)) ' seconds']);
Note: See TracBrowser for help on using the repository browser.