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: > > > > > > I've been running *backwards* trajectories with IDV5.0 and noticed > > > that the trajectories are taking an unrealistic turn in the time step > > > that begins their backwards integration (see attached). It is especially > > > obvious when using datasets with longer time increments. In this case, > > > I'm using 3-h RAP data where I've aggregated the files by time when > > > loading them. > > > > > > This bug could have preceded 5.0. I just started running them > > > today and figured I'd use the new release. > > > > > > Jim > > > > Jim, > > > > This part of code not being changed for a while, I can reproduce in the 5.0 > > and I will fix it asap. > > > > > > YUan > > > Jim, > I did see a bug in the calculation of backward trajectory, and checked in a > fix. You can try the nightly in 20 minutes, which is 5.0u1 release. > > I can not find the dataset you were using, I used the NAM80km, see the > attached image. I will do some comparison with gempak next week. > Yuan Jim, I just committed another change and this should fix the bug you reported. I redo the 5.0 release, you should download and install the 5.0 release. It is kind of interesting that I wrote this part of code on the flight from Madison to Denver, and now I have fixed a bug on the flight from Denver to New York. Yuan > > > > > > > > > > > Ticket Details =================== Ticket ID: ABK-864576 Department: Support IDV Priority: Normal Status: Closed