STASH: radar reflectivity and COSP output

[dsergeev]

Hi,

I'm trying to validate UM against the radar and lidar products from Cloudsat and CALIPSO satellites, so I'd like to include such diagnostics as
s02i351 COSP: CLOUDSAT REFLECTIVITY
s02i341 COSP: CALIPSO TOTAL BACKSCATTER
in the output.

Is there any guide on how to switch on these STASH diagnostics correctly? I tried simply rerunning my experiment with COSP model switched on (Model Selection → Atmosphere → Scientific Parameters and Sections → Section by section choices → Section 2: LW Radiation), but it fails on the first time step.

I also searched for any other relevant diagnostics in ​http://reference.metoffice.gov.uk/um/stash and found some in the section 4, such as

s04i118 TOTAL RADAR REFLECTIVITY 3D (dBZ)

but this STASH code does not appear in the list of diagnostics. Is it possible to make it available?

The experiment ids are xlce on ARCHER (and another option is xlpi on MONSooN).

Thank you,
Denis

[willie]

Hi Denis,

You might find some info on ​Cloud Feedback Model Intercomparison Project.

The radar reflectivity is only available at UM9.1 and later.

I hope that helps.

Regards

Willie

[grenville]

Denis

Please point us to a leave file - there are 13 possible jobs in xlce and xlpi

Grenville

[dsergeev]

Grenville,

The .leave file for the unsuccessful experiment with COSP is
/home/n02/n02/dsergeev/output/xlcea000.xlcea.d15290.t175427.leave

It was launched with options "Run with COSP": "CLOUDSAT simulator" and "CALIPSO simulator".

Denis

[grenville]

Denis

xlcea doesn't have COSP diags on (currently) - is this the configuration used to produce /home/n02/n02/dsergeev/output/xlcea000.xlcea.d15290.t175427.leave?

You don't specify output domains for the COSP diagnostics.

Grenville

[dsergeev]

Grenville,

Do you mean COSP diagnostics in the STASH table or COSP run options in Section 2: LW Radiation)? Do they both have to be switched on for a successful model run? The .leave file was produced when I only switched on COSP in LW Radiation section, but left diagnostics in STASH to "not used".

As for the COSP domains, I'm not sure what levels are required and I couldn't find any example.

Thanks,
Denis

[grenville]

Denis

Where does /work/n02/n02/dsergeev/xlcea/xlcea.astart come from - it appears to be corrupted?

Grenville

[dsergeev]

That's odd, because I've been using this start file for several runs. It was generated by the same job, but in the reconfiguration mode.

[grenville]

OK - that's odd — could be xconv.

Grenville

[grenville]

Denis

It appears that um vn8.2 does not properly support COSP. UM 8.6 may be a better option.

If use of COSP is essential for you, I think you'd be best to contact the COSP code developers at the MO. We can put you in touch if needed.

Grenville

[dsergeev]

Grenville,

I also have an option of using UM8.5 (Monsoon nesting suite), so does COSP work with vn8.5?

Thanks,
Denis

[grenville]

Denis

Could you try running the 8.5 job - its not clear what is the status of COSP at 8.5?

Let us know the jobid.

Grenville

[dsergeev]

Hi Grenville,

I recently moved to MONSooN and started using the new Nesting Suite, so I modified the ticket.

I'm still willing to have an output of CloudSat? radar reflectivity, but the main problem is that I don't know what domain to use for COSP diagnostics. The STASH entries has no description.

Thank you,
Denis