Change NUOPC default to unmappedaction=error#548
Conversation
* Forces end-user to handle unmapped points which fixes potential incorrect results due to zeroing unmapped cells * Non-backwards compatible for NUOPC applications that are not handling unmapped points * Previous behavior is replicated by adding ':unmappedaction=ignore' to NUOPC Connector options in run sequence * Other options include adding ':extrapmethod=<extrapmethod>' or ':unmappedaction=ignore:zeroregion=select' to Connector options
theurich
left a comment
There was a problem hiding this comment.
Changes look good to me. This will be good to have!
@danrosen25 I just restarted the one CI test combo that was failing. It looked like an unrelated hiccup.
Also, I am looking at the nuopc-apps-protos that need fixing. Will let you know how that goes in a bit.
|
@danrosen25 we might need this available via |
|
@theurich |
|
@danrosen25 thanks! Adjustments to this change for nuopc-app-prototypes are ready to go under esmf-org/nuopc-app-prototypes#14. Just waiting for esmf-org/nuopc-app-prototypes#13 to come in first so I can kick off a GH test run. |
:unmappedaction=ignoreto NUOPC Connector options in run sequence:extrapmethod=<extrapmethod>or:unmappedaction=ignore:zeroregion=selectto Connector optionsNotes