This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi Vinit, My suggestion would be to run your model on both computers A and B in a debugger, or insert print statements to try to isolate where computer A starts getting different results than computer B. That may help to determine where the difference is coming from. Also, print out the variable names before using them in NCVDEF calls, to see which variable name is causing the problem. It may have nothing to do with netCDF, but instead be caused by an out-of-range array index causing the contents of a variable name to be overwritten by a number, for example. If you have a Fortran option to check all array indices to make sure they are within declaration bounds, try using that to see if an errant array index is the root cause of the problem. I know this is very general advice, but without a more specific description of the problem in a way we can reproduce, it's hard to offer better suggestions. --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: MON-411847 Department: Support netCDF Priority: Normal Status: Closed