-
|
I am having trouble running the TCPairs basic use case for tropical cyclones. The conf file provided for running the example case does not correspond to the sample data provided (https://dtcenter.ucar.edu/dfiles/code/METplus/METplus_Data/v5.1/sample_data-tc_and_extra_tc.tgz): the dates and storms in the When I change the dates and storm variables manually I do get a bit further, but then I hit another barrier: I see references in the conf file to a "gen_dland" utility that should be producing a file I am running on Jet and referencing the METplus build that was installed by EPIC here: Let me know if there's any other information I can provide. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 3 replies
-
|
Hello, And thank you for your question. I think the solution to this issue might be a better explanation of the use case you're trying to get to run. The "basic use cases", demonstrating METplus wrapper usage (including the TCPairs_tropical configuration file you linked to) are located in the met_tool_wrapper directory of the repository. The link here shows all of these configuration files gathered together, under the common category name "MET tools". As such, these examples rely on data located in met_test, a separate directory from the data necessary to run the other use cases, which are gathered under the common category name "Model Applications". So the link you provided to the sample data for tc and extra tc does not contain the necessary dataset for the TCPairs_tropical met_tool example to run properly; it contains data for the model applications use cases and you need the dataset for MET tools. You correctly saw that the configuration file needs data from 2018 while the data in the .tgz file contains data from 2021. A quick way to tell which data directory the correct datasets are in is to check the _INPUT_DIR variables of the configuration file. For the TCPairs_tropical configuration file, it's Note how both variable settings start with the user's {INPUT_BASE}, but are immediately followed by "met_test": this says the correct dataset will be in the met_test data folder. On JET, I see that all test data (for both "MET tools" and "Model Applications") should be located in /lfs1/HFIP/dtc-hurr/METplus/METplus-5.1_sample_data. Setting this path for your {INPUT_BASE} with no changes to the configuration file should correctly pull from the met_test directory instead of the model_applications. If you need help with setting this, please let me know. For a little more background context, the biggest difference between these two categories of use cases, "MET tool" and "model applications", is that the MET tool category serves as a example of how to run the wrapped tool only; it is not meant to produce meaningful data, nor does it represent any scientific meaningfulness aside from how to use the tool. The model applications category contains examples of how one or more wrapped tools were used to answer scientific objectives, using real data and producing statistics that were useful to the parties involved with creating the use case. As such, it made sense to separate these two data categories into separate directories. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @mkavulich, I wanted to reach out again to see if you had any further questions related to this Discussions topic. If not, I will select an answer and lock the topic from any further comments. |
Beta Was this translation helpful? Give feedback.
-
|
@j-opatz Thanks for the replies, sorry I haven't gotten around to trying your solution yet. I was planning to try again today but unfortunately the Jet file system I need (lfs4) is down and there is no ETA for restoration. As one follow-up question, does this mean that if I do need to download sample data for these "Model Application" cases, I'll need to |
Beta Was this translation helpful? Give feedback.
-
|
There is an easier way, luckily! If you go to the parent directory of the link you provided (this one here) you'll see that all of the "sample_data_xyz" tgz files are available. These will contain data for all of the model application use cases of that specific type. For example, "sample_data-precipitation.tgz" contains all of the data to run the 10 precipitation-type use cases. In a similar way, "sample_data-met_tool_wrapper-5.1.tgz" contains all of the files necessary to run the "met tool wrapper" examples. This tgz would contain the necessary data for the TC example you were trying to run. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @mkavulich, I wanted to reach out and see if the above suggestions have answered your questions. If it has, please mark an answer and I'll go ahead and lock the question from further discussions. If you still have questions related to this topic or the suggestions didn't quite solve the issue, please reach out and let me know! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your help @j-opatz, I was able to run the case successfully once I was able to use the correct data. While I have you, I did notice a minor error in the basic TCPairs use case: the provided conf file sets |
Beta Was this translation helpful? Give feedback.
-
|
That's a good question I'd like to look into with a separate Discussions topic. I've gone ahead and created a new one here: #2625 |
Beta Was this translation helpful? Give feedback.
Hello,
And thank you for your question. I think the solution to this issue might be a better explanation of the use case you're trying to get to run. The "basic use cases", demonstrating METplus wrapper usage (including the TCPairs_tropical configuration file you linked to) are located in the met_tool_wrapper directory of the repository. The link here shows all of these configuration files gathered together, under the common category name "MET tools". As such, these examples rely on data located in met_test, a separate directory from the data necessary to run the other use cases, which are gathered under the common category name "Model Applications". So the link you provided to the sample…