The first concern is not to use a name that is already being used. To check if the name exists on the /ys tree on an Ultrix machine, you can use the symbol `chk_name'. Here is an example (note that the .PRO portion is required): % chk_name yodat.proOn a VMS machine, the following command should work: $ dir ys:[...]yodat.proIt is possible to do the search from within IDL on any of the machines using a command like: IDL> print, path_lib('yodat') IDL> print, path_lib('yo*') ;for all routines beginning with `yo'IDL> pr_path_lib, 'yo*'The second concern is use care when chosing the name. It should not be general enough to cause conflicts or confusion between all of the other instrument teams. For example, the original name of SXT_DECOMP was DECOMP. Every instrument has a decompression routine, so the name of the instrument needs to be incorporated in the name of the routine for general routines. The name of the routine should not be shorter than four letters and less than 14 characters (so that IDL can compile it properly). Underscores are acceptable, and the file name should be all lower case.
The GT_ routines are a unique set of routines meant solely for the extraction of data out of a Yohkoh data structure. Normally, routines should have the name GET_ unless it is designed to extract data from one fo the Yohkoh data structures.