NCAR / NCAR/DART

WRF with threed_cartesian?

Open
#751 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

wrf
Dominant language
Fortran
Stars
263
Forks
182
Avg merge
11d 12h
Merged PRs (30d)
7

Description

Hi,
I appreciate your support of the DART software.

What's the issue?

I don't know whether this is a bug or a missing feature:
I tried to compile DART with WRF and threed_cartesian but received an error about non-existing VERTISUNDEF, VERTISSURFACE, VERTISHEIGHT, and so on. These names don't exist in location/threed_cartesian/location_mod.f90, but they are defined in location/threed_sphere/location_mod.f90.

Do you know if this is supposed to work? If not, it could be noted in the documentation. Can you estimate what's necessary to make it work?

Anything else we should know?

I used DART-v10.9.2.

I noticed that location/threed_cartesian/location_mod.f90 contained VERTISHEIGHT at some point: https://github.com/NCAR/DART/commit/f900c4d50bc39cb0b519ea7f45360dfa487bc8ad

My goal would be to use periodic horizontal coordinates for an idealized WRF limited area domain.
Terminal output: cmdline.txt

Thank you!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the DART-v10.9.2 WRF build using the command line in cmdline.txt. Compare location/threed_cartesian/location_mod.f90 with location/threed_sphere/location_mod.f90 and review commit f900c4d50bc39cb0b519ea7f45360dfa487bc8ad. Done means establishing whether threed_cartesian is supported for WRF and either documenting the limitation or defining the required implementation scope.

Written by the indexing model from the issue text.

Assessment

Tech stack
fortran
Domain
data
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.