Possible error in TCPairs use case #2625
-
@mkavulich noted in a separate Discussions post: I did notice a minor error in the basic TCPairs use case: the provided conf file sets TC_PAIRS_DLAND_FILE, but this was not the correct setting; I had to instead set METPLUS_DLAND_FILE to get the run to complete. Should I open a separate issue for this correction? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Hi @mkavulich, Given the subject area of this Discussions topic, I'm going to pull in @mrinalbiswas as our SME. I know they'll be able to sort out why you're experiencing an issue with TC_PAIRS_DLAND_FILE and not METPLUS_DLAND_FILE. |
Beta Was this translation helpful? Give feedback.
-
Hi @mkavulich, The METplus config variable is TC_PAIRS_DLAND_FILE, so the TCPairs basic use case config file is correct. The environment variable that is set by the METplus wrappers before calling the tc_pairs tool is named If changing Could you please rerun METplus before changing |
Beta Was this translation helpful? Give feedback.
Hi @mkavulich,
The METplus config variable is TC_PAIRS_DLAND_FILE, so the TCPairs basic use case config file is correct. The environment variable that is set by the METplus wrappers before calling the tc_pairs tool is named
METPLUS_DLAND_FILE
, but setting this variable in either your METplus config file or the terminal will not have any effect on the value used by METplus wrappers.If changing
TC_PAIRS_DLAND_FILE
toMETPLUS_DLAND_FILE
in the METplus config file fixed the failure, then it sounds like there may be an issue finding the dland file. Your change may cause the use case to succeed, but it may not be using the dland file as intended.Could you please rerun METplus before changing
T…