- Timestamp:
- 07/12/06 11:52:09 (18 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/SRC/Documentation/idldoc_html_output/Interpolation/fromreg.html
r121 r138 328 328 table.variables td.image { width: 64px; } 329 329 330 div#file_comments { 330 div#file_comments { white-space: pre; 331 331 margin: 2em; 332 332 font-size: 80%; … … 696 696 </div> 697 697 698 <div id="file_comments"> interpolate data from a "regular/rectangular grid" to any grid. 699 2 metods availables: bilinear and imoms3 700 A "regular/rectangular grid" is defined as a grid for which each lontitudes lines have 698 <div id="file_comments"> 699 interpolate data from a "regular/rectangular grid" to any grid. 700 2 methods availables: bilinear and imoms3 701 A "regular/rectangular grid" is defined as a grid for which each lontitudes lines have 701 702 the same latitude and each latitudes columns have the same longitude. 702 703 </div> 703 704 704 705 … … 724 725 </div> 725 726 726 <h3>Return value</h3><div class="value"> 2D array the interpolated data 727 <h3>Return value</h3><div class="preformat"> 728 2D array the interpolated data 727 729 </div> 728 730 … … 742 744 </h4> 743 745 744 <div class="comments"> a string defining the interpolation method. 745 must be 'bilinear' or 'imoms3'</div> 746 <div class="comments"> 747 a string defining the interpolation method. 748 must be 'bilinear' or 'imoms3' 749 </div> 746 750 747 751 <h4 id="_fromreg_param_datain">datain … … 756 760 </h4> 757 761 758 <div class="comments"> a 2D array the input data to interpolate</div> 762 <div class="comments"> 763 a 2D array the input data to interpolate 764 </div> 759 765 760 766 <h4 id="_fromreg_param_lonin">lonin … … 769 775 </h4> 770 776 771 <div class="comments"> 1D or 2D array defining the longitude of the input data</div> 777 <div class="comments"> 778 1D or 2D array defining the longitude of the input data 779 </div> 772 780 773 781 <h4 id="_fromreg_param_latin">latin … … 782 790 </h4> 783 791 784 <div class="comments"> 1D or 2D array defining the latitude of the input data</div> 792 <div class="comments"> 793 1D or 2D array defining the latitude of the input data 794 </div> 785 795 786 796 <h4 id="_fromreg_param_lonout">lonout … … 795 805 </h4> 796 806 797 <div class="comments"> 1D or 2D array defining the longitude of the output data</div> 807 <div class="comments"> 808 1D or 2D array defining the longitude of the output data 809 </div> 798 810 799 811 <h4 id="_fromreg_param_latout">latout … … 808 820 </h4> 809 821 810 <div class="comments"> 1D or 2D array defining the latitude of the output data 822 <div class="comments"> 823 1D or 2D array defining the latitude of the output data 811 824 </div> 812 825 … … 843 856 844 857 <div class="comments"> 2D arrays, weig and addr are the weight and addresses used to 845 858 perform the interpolation: 846 859 dataout = total(weig*datain[addr], 1) 847 860 dataout = reform(dataout, jpio, jpjo, /over) 848 849 850 851 861 Those keywords can be set to named variables (that are undefined or equal to 0) into which the 862 values will be copied when the current routine exits. Next, they can be used to perform 863 the interpolation whithout computing again those 2 parameters. In that 864 case, lonin, latin, lonout and latout are not necessary. 852 865 </div> 853 866 … … 863 876 </h4> 864 877 865 <div class="comments"> 878 <div class="comments"></div> 866 879 867 880 <h4 id="_fromreg_keyword_NOSOUTHERNLINE">NOSOUTHERNLINE … … 876 889 </h4> 877 890 878 <div class="comments"> 879 activate if you don't w hant to take into account the northen/southern line891 <div class="comments"> 892 activate if you don't want to take into account the northen/southern line 880 893 of the input data when perfoming the interpolation. 881 894 </div> … … 883 896 884 897 885 <h3>Examples</h3><div class=" value">886 887 888 889 or 890 891 892 893 898 <h3>Examples</h3><div class="preformat"> 899 900 IDL> topa = fromreg('bilinear', tncep, xncep, yncep, glamt, gphit) 901 902 or 903 904 IDL> t1opa = fromreg('bilinear', t1ncep, xncep, yncep, glamt, gphit, WEIG = a, ADDR = b) 905 IDL> help, a, b 906 IDL> t2opa = fromreg('bilinear', t2ncep, xncep, WEIG = a, ADDR = b) 894 907 </div> 895 908 <h3>Version history</h3> 896 909 897 <h4>Version</h4><div class=" value"> $Id: fromreg.pro 118 2006-06-27 15:47:06Z pinsard $898 </div> 899 <h4>History</h4><div class=" value">900 November 2005: Sebastien Masson (smasson@lodyc.jussieu.fr) 910 <h4>Version</h4><div class="preformat"> $Id: fromreg.pro 136 2006-07-10 15:20:19Z pinsard $ 911 </div> 912 <h4>History</h4><div class="preformat"> 913 November 2005: Sebastien Masson (smasson@lodyc.jussieu.fr) 901 914 </div> 902 915 … … 906 919 907 920 908 <h4>Restrictions</h4><div class="value"> We supposed the data are located on a sphere, with a 909 periodicity along the longitude. 921 <h4>Restrictions</h4><div class="preformat"> 922 We supposed the data are located on a sphere, with a periodicity along the 923 longitude. 910 924 </div> 911 925
Note: See TracChangeset
for help on using the changeset viewer.