cesm2.1.0_BHIST

[Jewel]

I recently tried to run cesm2.1.0_BHIST and encountered the following two problems:
1. When I compile the BHIST script, it reads the input data of ‘b.e21.B1850.f09_g17.CMIP6-piControl.001’. I would like to ask some special settings to allow it to read ‘b.e21.BHIST Input file for .f09_g17.CMIP6-historical.001’?
2. When I modify the initial time of mode operation (changing 1850-01-01 to 2000-01-01), I will encounter the problem of missing variables in pop, as mentioned in this forum (https://bb .cgd.ucar.edu/cesm/threads/running-the-cesm2-1-3-bhist-res-f09_g17-meet-some-errors-after-i-changed-the-startdate.7509/). How should I solve this problem?

Below is my script setup

./create_newcase --case $CASEROOT --mach $MACH --res f09_g17 --compset BHIST --compiler intel --queue mpi --walltime 01:00 --run-unsupported
./xmlchange --file env_run.xml --id RESUBMIT --val '0'
./xmlchange --file env_run.xml --id RUN_STARTDATE --val '1850-01-01'
./xmlchange --file env_run.xml --id STOP_N --val '3'
./xmlchange --file env_run.xml --id STOP_OPTION --val 'ndays'

 

[sacks]

(1) I think you mean that you would like to change the reference case ("refcase") for this run so that it starts with initial conditions from a different case. This can be done by changing the xml variable RUN_REFCASE. Also search for similar variables by doing ./xmlquery --partial REF.

(2) Sorry, I'm not sure about (2), but I would suggest giving more information in your post in the POP forum - giving full steps to reproduce the problem, as noted in Information to include in help requests . But first, see if the last few comments in POP aborting: Ocean tracer module problem in B1850 run help address this issue.

 

[Jewel]

(1) I think you mean that you would like to change the reference case ("refcase") for this run so that it starts with initial conditions from a different case. This can be done by changing the xml variable RUN_REFCASE. Also search for similar variables by doing ./xmlquery --partial REF.

(2) Sorry, I'm not sure about (2), but I would suggest giving more information in your post in the POP forum - giving full steps to reproduce the problem, as noted in Information to include in help requests . But first, see if the last few comments in POP aborting: Ocean tracer module problem in B1850 run help address this issue.

Thanks a lot for your help! Following your suggestions I have solved my problem