|
Hi David, This has been on our list of improvements to make for a while, and the MODE UPCASE is a step towards full control over the case of variables in output files. There are just two entirely pieces of the underlying code that are doing things here. For netCDF files, we have introduced a step in the initialization of the file where Ferret saves information about the file. We store global attributes, variable attributes, and the original upper-or lower-case spelling of the variables and attributes, and we use that stored information when deciding what attributes to write and what case names are in. For user commands defining variables, the name of the variable is upcased almost right away. By default Ferret is case-insensive (and for almost everything there's no choice about treatment of case). If we say yes? use basin.nc yes? LET A1 = BASIN yes? let a1 1= 2*basin then we've defined only one variable, A1. The second definition replaces the first, and we cannot define two variables a1, and A1 (as Ferret is currently written). So there's more to the issue than just what the case will be upon output. It would be a small step, however, to change the Ferret code to save the case of the variable from the LET command each time a definition is made, and if CANCEL MODE UPCASE is in effect, we would output the variable using that case to netCDF files. In the above example yes? use basin.ncDoesn't work this way yet, but I'll add this to our planning. David Wang wrote: Hello Ferreters, -- ~> ~> ~> ~> ~> ~> ~> ~> ~> ~> ~> Ansley Manke, NOAA/PMEL ansley.b.manke@xxxxxxxx 7600 Sand Point Way NE, Seattle WA Phone 206-526-6246, FAX 206-526-6744 |