Replies: 5 comments 8 replies
-
Converted issue #418 into this Q&A discussion. #420 addresses the question of running two cases simultaneously. At the moment, I personally think it's best to do as a two-step process. Copied from my response in that discussion: The best solution is to run a |
Beta Was this translation helpful? Give feedback.
-
Thank you. I followed the example in https://github.com/E3SM-Project/zppy/blob/main/tests/integration/generated/test_complete_run_chrysalis.cfg I'm running model_vs_model comparison for a single year. I'm attaching a snippet of my code for the e3sm_diags section. e3sm_diags_atm_monthly_180x360_aave_mvm_model_vs_model_2010-2010 Code snippet: [e3sm_diags] [[ atm_monthly_180x360_aave ]] [[ atm_monthly_180x360_aave_mvm ]] climo_diurnal_subsection = "atm_monthly_diurnal_8xdaily_180x360_aave" |
Beta Was this translation helpful? Give feedback.
-
I think the error is also present in e3sm_diags model_vs_obs. Do you see red flags here in the code below? I tried with and without ref start year. active = True [[ atm_monthly_180x360_aave ]] |
Beta Was this translation helpful? Give feedback.
-
I tested the code for a single year using 1.8.1. I get a similar error in e3sm_diags model_vs_obs. It works when I input multiple years. I added dependency files in climatology and time series. |
Beta Was this translation helpful? Give feedback.
-
@forsyth2 and all, sorry this took a long time, but here's an example cfg that works for one-year runs: # [default]
# input = /global/cfs/cdirs/e3sm/mahf708/E3SMv3_dev/78a5ea1.nudged.mixPI.2DMS.10Nc.pm-cpu
# output = /global/cfs/cdirs/e3sm/mahf708/E3SMv3_dev/78a5ea1.nudged.mixPI.2DMS.10Nc.pm-cpu
# case = 78a5ea1.nudged.mixPI.2DMS.10Nc.pm-cpu
# www = /global/cfs/cdirs/e3sm/www/mahf708/E3SMv3_dev
# qos = preempt
# machine = pm-cpu
# environment_commands = "source /global/common/software/e3sm/anaconda_envs/test_e3sm_unified_1.9.0rc12_pm-cpu.sh"
# [climo]
# active = True
# nodes = 2
# walltime = "00:30:00"
# years = "2010:2010:1",
# [[ atm_monthly_180x360_aave ]]
# input_subdir = "run"
# input_files = "eam.h0"
# mapping_file = /global/cfs/cdirs/e3sm/zender/maps/map_ne30pg2_to_cmip6_180x360_aave.20200201.nc
# frequency = "monthly"
[default]
input = /global/cfs/cdirs/e3sm/mahf708/E3SMv3_dev/78a5ea1.nudged.clmPD.2DMS.10Nc.pm-cpu
output = /global/cfs/cdirs/e3sm/mahf708/E3SMv3_dev/78a5ea1.nudged.clmPD.2DMS.10Nc.pm-cpu
case = 78a5ea1.nudged.clmPD.2DMS.10Nc.pm-cpu
www = /global/cfs/cdirs/e3sm/www/mahf708/E3SMv3_dev
qos = preempt
machine = pm-cpu
environment_commands = "source /global/common/software/e3sm/anaconda_envs/test_e3sm_unified_1.9.0rc12_pm-cpu.sh"
[climo]
active = True
nodes = 2
walltime = "00:30:00"
years = "2010:2010:1",
[[ atm_monthly_180x360_aave ]]
input_subdir = "run"
input_files = "eam.h0"
mapping_file = /global/cfs/cdirs/e3sm/zender/maps/map_ne30pg2_to_cmip6_180x360_aave.20200201.nc
frequency = "monthly"
[e3sm_diags]
active = True
machine = pm-cpu
years = "2010:2010:1",
ts_num_years = 1
ref_start_yr = 1979
ref_final_yr = 2016
multiprocessing = True
num_workers = 128
[[ atm_monthly_180x360_aave_mvm ]]
climo_subsection = "atm_monthly_180x360_aave"
grid = '180x360_aave'
diff_title = "Difference"
ref_final_yr = 2010
ref_start_yr = 2010
reference_data_path = '/global/cfs/cdirs/e3sm/mahf708/E3SMv3_dev/78a5ea1.nudged.mixPI.2DMS.10Nc.pm-cpu/post/atm/180x360_aave/clim/'
ref_name = "78a5ea1.nudged.mixPI.2DMS.10Nc.pm-cpu"
ref_years = "2010-2010",
run_type = "model_vs_model"
years = "2010-2010",
short_ref_name = '78a5ea1.nudged.mixPI.2DMS.10Nc.pm-cpu'
short_name = '78a5ea1.nudged.clmPD.2DMS.10Nc.pm-cpu'
swap_test_ref = False
tag = "model_vs_model"
ts_num_years_ref = 1
ts_subsection = "atm_monthly_180x360_aave" Idea is to run the commented out stuff in isolation first to get those climos, then to run the currently uncommented stuff second to get the climos and run the mvm e3sm_diags. |
Beta Was this translation helpful? Give feedback.
-
Discussed in #293
Originally posted by forsyth2 August 9, 2022
How can I run model-vs-model diagnostics?
Hi,
I have a question about the model-vs-model comparisons. Can the zppy code directly create climatological outputs for both model simulations, or is it a two-step process ? 1. Create climatological outputs separately for each simulation, then, run zppy the reference_data_path in 'atm_monthly_180x360_aave_mvm' pointing to the climatological outputs from the other simulation. . if you have a reference code for model-vs-model comparison, that would be very helpful.
Beta Was this translation helpful? Give feedback.
All reactions