make missing forcing data an error instead of a warning? #1781
|
Is there a namelist or other option to cause LIS to stop running if forcing files are missing for that time period? The reason I ask is that we were noticing some strange output in our near-real-time LIS runs, and upon looking further noticed that the forcing files (NLDAS-2) were not downloading properly because I needed to reset my login credentials for the NASA server. However, LIS continues to run with just a warning even if there are no forcing files available, which gives incorrect results. Is it possible to change this from a warning to an error? Thanks! |
Replies: 1 comment 1 reply
|
Yes, it's possible, but it will require a code change, not a namelist option. It will be specific to the metforcing used. You may be using a container version of LIS instead of compiling it, correct? If you are compiling it, I can point you to where to make the code changes. |
|
Yes, we've got a container version. It's not a huge deal - I can just set up a different check for the forcing files in my script to ensure they are there before launching LIS. Was just wondering if there was already a switch to flip somewhere. |
Hi @russ-schumacher
Yes, it's possible, but it will require a code change, not a namelist option. It will be specific to the metforcing used. You may be using a container version of LIS instead of compiling it, correct? If you are compiling it, I can point you to where to make the code changes.