We are setting up a nesting suite case for S. America and require SST updates. We plan to use daily updates, but are starting by trying to get the default monthly updates to work.
Our first step is to run our suite to create new ancils, setting the sst_smc ancillary toggle to true. This creates the qrclim.sst etc.
The next step is to set the ancil mode to use a previous run of this suite. We need this step to swap in a CCI vegfrac ancil we created for our case. This all runs fine, but I noticed the sst_smc ancillary toggle disappears on the suite GUI. Expanding the info for this toggle it states “these extra ancillaries are not used by the default version of the nesting suite”. This suggests it can create them, but the nesting suite won’t use them.
I tested this by setting the model up to fail by changing the name of the newly created SST ancil so the model wouldn’t be able to find in, and ran it at the end of Jan 2010 into Feb so it should be looking for the new SST values. Frustratingly the model succeeded meaning in its current form not able to read the SST files.
This is running using the V11.7 nesting suite, and driven by ERA5 data.
If anyone has any experience with the below or a copy of a suite I could look at where you have got this to work much appreciated!
I’m sorry that I haven’t gone into your suite, but there is a more recent version (UM12.0) of the supported regional nested suite (by395):
It might be worth looking at this, in case someone has updated the functionality that you are looking for, so I have dropped a link here in case it’s useful.
Great to know v12 nesting is up and running as we’ve not yet started our simulations so the opportunity to upgrade our suite is appealing!
At first glance v12 nesting suite looks to have the same description (“these extra ancillaries are not used by the default version of the nesting suite”) and disappearing SST toggle. Although I won’t fully know until tested.
Thank you for the link below. I noticed that there is a ticket to update u-by395 to v13.0 – just wondering if you have timescales for this?
There is a branch at UM13.0:
(ie branch archer2_um12p0 , so I just used the same as above, which I know in hindsight is a badly chosen name).
You should be able to run this branch as it is (I hope), although I presume can’t get it into the trunk until other issues are resolved. It’s all change in the RNS and RAS (these functionalities are to be separated) etc.
But please try this branch if it helps,
I’ll give it a go! Many thanks,