You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The < cycle # > feature in the legend is very nice for rapidly comparing a sequence of runs. However, if a run is missing, e.g., for some reason the 06Z run isn't populated in apsviz, then the < > keys don't work. In this case it would be great if these keys could just skip over missing cycles so long as the model run data and cycle number are correct.
The text was updated successfully, but these errors were encountered:
i dont believe this is a bug. i have not found an issue with the website or data on this. note that there are some model runs that didnt start at cycle 01.
for example, the "veerRight100" runs (Type: veerRight100, Grid: egom_v20b, Instance: egom_al09_nopp_sapelo) started at cycle 008. if for instance you loaded the most recent "veerRight100" (adv 014) you can only go back to adv 008 for that type of run.
there are other runs (Type: ofcl, Grid: egom_v20b, Instance: egom_al09_nopp_sapelo), that admittedly have a listing that looks very similar to "veerRight100", started at adv 001 where you can scroll all the way latest to first.
The < cycle # > feature in the legend is very nice for rapidly comparing a sequence of runs. However, if a run is missing, e.g., for some reason the 06Z run isn't populated in apsviz, then the < > keys don't work. In this case it would be great if these keys could just skip over missing cycles so long as the model run data and cycle number are correct.
The text was updated successfully, but these errors were encountered: