ICON Model Parameter Request: East Domain Discussion

by Editorial Team 53 views
Iklan Headers

Hey guys! Let's dive into setting up an ICON model with some specific external parameters for our East domain. This article will guide you through the process, ensuring you get the data you need. We'll cover everything from the initial request to understanding the status labels. Let's get started!

Instructions

First things first, make sure to give your issue a meaningful title. This helps keep things organized, especially when dealing with multiple requests. Think about including the domain name, grid specifications, and project details in the title.

Next, you'll need to paste your request into the designated area. Here’s an example of what that request looks like:

{
 "zonda": {
 "icontools_tag": "latest",
 "extpar_tag": "latest"
 },
 "basegrid": {
 "keep_basegrid_files": false,
 "grid_root": 3,
 "grid_level": 9,
 "outfile": "LE",
 "icorotation": 0,
 "icopole_lat": 90,
 "icopole_lon": 0,
 "centre": 78,
 "subcentre": 255
 },
 "domains": [
 {
 "domain_id": 1,
 "icontools": {
 "parent_id": 0,
 "region_type": 3,
 "center_lat": 51.1,
 "center_lon": 12.5,
 "hwidth_lat": 1.6,
 "hwidth_lon": 2.7,
 "lrotate": false,
 "pole_lat": 90,
 "pole_lon": -180
 },
 "extpar": {
 "use_array_cache": false,
 "iaot_type": 1,
 "ilu_type": 1,
 "ialb_type": 1,
 "isoil_type": 1,
 "itopo_type": 3,
 "it_cl_type": 1,
 "iera_type": 1,
 "iemiss_type": 1,
 "lradtopo": false,
 "enable_cdnc": false,
 "enable_edgar": false,
 "radtopo_radius": 40000,
 "nhori": 24,
 "enable_art": false,
 "l_use_corine": false,
 "ilookup_table_lu": 1,
 "tcorr_lapse_rate": 0.0065,
 "tcorr_offset": 0
 }
 }
 ]
}

Before submitting, hit the "Preview" tab to make sure your JSON is looking good. A correctly formatted JSON block is crucial for the request to be processed without issues. This step helps you catch any syntax errors or formatting problems early on.

Finally, click "Create" to submit your data request. The Zonda Request system will take it from here and process your data based on the specifications you provided. Once everything is set, Zonda will post a link in the issue, giving you access to your processed data. Remember, this link will be active for 7 days, so make sure to download your data promptly.

Also, if you need to resubmit the data request, just drop a comment with the phrase "rerun request". Keep in mind that the system will use the JSON snippet currently in the description, so any edits you make will impact the new submission. Resubmission is only available if the issue is open and the request isn't already running.

If you run into any snags, don't hesitate to ping a maintainer like @stelliom or @mjaehn. Include all relevant information from the log files directly in the issue. This helps them quickly diagnose and resolve any problems.

Understanding the JSON Structure

To effectively use the ICON external parameter request, it's essential to understand the structure of the JSON object. Let's break down the key components:

  • zonda: This section specifies the tags for icontools and extpar. These tags usually indicate the version or release of the ICON tools and external parameters you want to use. Using latest ensures you're working with the most up-to-date versions.
  • basegrid: This part defines the base grid configuration. Key parameters include grid_root and grid_level, which determine the resolution of the grid. The outfile parameter specifies the naming convention for the output files. The icorotation, icopole_lat, and icopole_lon parameters define the grid's rotation and pole coordinates. centre and subcentre are identifiers for the grid's location.
  • domains: This is an array that can contain one or more domain configurations. Each domain specifies parameters for a specific region. Within each domain, there are two main sections: icontools and extpar.
    • icontools: This section defines the parameters related to the ICON tools for the specific domain. parent_id indicates the parent domain (if any). region_type specifies the type of region (e.g., land, sea, or mixed). center_lat and center_lon define the geographical center of the domain. hwidth_lat and hwidth_lon specify the half-width of the domain in latitude and longitude. lrotate indicates whether the domain should be rotated, and pole_lat and pole_lon define the pole coordinates for the rotation.
    • extpar: This section defines the external parameters for the domain. use_array_cache determines whether to use an array cache for external parameters. iaot_type, ilu_type, ialb_type, isoil_type, itopo_type, it_cl_type, iera_type, and iemiss_type specify the types of various external parameter datasets. lradtopo enables or disables the use of radiation topography. enable_cdnc and enable_edgar enable or disable the use of cloud droplet number concentration and EDGAR emission data, respectively. radtopo_radius defines the radius for radiation topography calculations. nhori specifies the number of horizontal grid points. enable_art enables or disables the use of aerosol radiation and transport. l_use_corine enables or disables the use of CORINE land cover data. ilookup_table_lu specifies the lookup table for land use. tcorr_lapse_rate and tcorr_offset define the temperature correction lapse rate and offset.

Best Practices for Submitting Requests

  • Verify JSON Syntax: Always use a JSON validator to ensure your JSON is correctly formatted before submitting. Tools like JSONLint can help identify syntax errors.
  • Provide Detailed Comments: If you have specific requirements or modifications, add comments within the JSON or in the issue description to provide additional context.
  • Test with Small Domains: When experimenting with new configurations, start with smaller domains to reduce processing time and resource usage.
  • Monitor Resource Usage: Keep an eye on resource usage, especially if you're running multiple requests. Adjust your configurations to optimize performance.
  • Stay Updated: Regularly check for updates to the ICON tools and external parameters to take advantage of the latest features and improvements.

Status Labels

Here’s what the status labels mean:

  • Static Badge - Submitted: Your request is in the queue and is being processed. Just hang tight!
  • Static Badge - Completed: Woo-hoo! Your request was successful. Download your data from the provided link.
  • Static Badge - Failed: Uh oh, something went wrong. Check the log files in the zip file at the download link for more details.
  • Static Badge - Aborted: The request timed out or was stopped. Try again, and if it keeps happening, reach out for support.

By understanding these labels, you can quickly assess the status of your request and take appropriate action if needed.

Troubleshooting Common Issues

  1. JSON Formatting Errors: Ensure your JSON is valid using a validator tool. Common issues include missing commas, incorrect brackets, and unescaped characters.
  2. Invalid Parameter Values: Double-check that your parameter values are within the acceptable range. Refer to the ICON documentation for valid values.
  3. Resource Limits: If your request exceeds resource limits, try reducing the domain size or simplifying the configuration.
  4. Network Issues: Ensure you have a stable network connection when submitting and downloading data. Intermittent connectivity can cause requests to fail.
  5. Outdated Tools: Keep your ICON tools and external parameters up to date. Using outdated versions can lead to compatibility issues.

By following these troubleshooting tips, you can resolve common issues and ensure your requests are processed successfully.

Conclusion

And there you have it! A complete guide to submitting ICON external parameter requests for the East domain. By following these instructions and keeping the tips in mind, you’ll be well-equipped to get the data you need. Good luck, and happy modeling!