Hi Team, I am running the model over Auckland, New Zealand, using 1 km and 4 km domains. The boundary of the 4 km domain crosses the 180° meridian (International Date Line), which is causing an error. Could you please help resolve this issue? Please find the domain plot and the error files here: a…

Hi @Leena , just to finalize this post for others. The problem was actually that the ancillaries had missing values in them. The solution was to re-run the Regional Ancillary suite applying @mlipson ’s workaround ( AUS2200 vegetation fraction ancil creation issues - #20 by mlipson ).

Hi @Leena , The BICGstab error indicates that there are NaN’s in the input files. It is likely that there are NaN’s in your ancillary files. @Paul.Gregory has a package that can scan your ancillaries for you, otherwise you can send me your suite and I can diagnose and fix the ancillary for you. B…

Hi @cbengel , Thank you for your reply and help. Can you access suite here: /home/561/lk5320/roses/u-dx356_AUK_1.. ? or please let me know how can I share it. Thank you, Kind regards, Leena

I can’t but it is ok. Let’s talk offline with @mlipson about it. Sending you a message via W21C.

ACCESS-rAM3, error in simulation due to dateline (180 degree meridian)

Atmosphere rAM3/Regional Nesting Suite

cbengel (Chermelle Engel) 2 July 2026 05:20 5

see This post

Topic		Replies	Views
Issues with ACCESS-rAM: ocean domains (u-dg767) and NaNs in BICGstab (u-dg768) rAM3/Regional Nesting Suite help , access-ram	15	405	11 August 2025
Making domain beyond 60 S in ACCESS-rAM3 rAM3/Regional Nesting Suite	29	327	2 April 2026
Issues when changing domain in ACCESS-rAM3 rAM3/Regional Nesting Suite help	17	229	24 February 2026
Ancils for small test domain fail checking during reconfiguration due to longitude rounding errors rAM3/Regional Nesting Suite	21	297	3 July 2026
AUS2200 vegetation fraction ancil creation issues AUS2200	23	539	19 November 2024

ACCESS-rAM3, error in simulation due to dateline (180 degree meridian)

Related topics