Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error in Test Case #445

Open
PrateekSharma99 opened this issue Nov 21, 2023 · 10 comments
Open

Error in Test Case #445

PrateekSharma99 opened this issue Nov 21, 2023 · 10 comments

Comments

@PrateekSharma99
Copy link

While running my test case 1, I am facing the following error that is coming in the output log file.

---- read control file ---
---- read control file ---
<ancil_dir> --> ./ancillary_data/
<input_dir> --> ./input/
<output_dir> --> ./output/
<case_name> --> case1
---- read control file ---
<ancil_dir> --> ./ancillary_data/
<sim_start> --> 1950-1-1 12:00:00
<sim_end> --> 1950-12-31 12:00:00
<restart_write> --> monthly
--> single
--> daily
<ancil_dir> --> ./ancillary_data/
<input_dir> --> ./input/
<output_dir> --> ./output/
<case_name> --> case1
FATAL ERROR: init_model/read_control/unexpected text in control file provided:
(note strings in control file must match the variable names i
n public_var.f90)
<input_dir> --> ./input/
<output_dir> --> ./output/
<case_name> --> case1
<sim_start> --> 1950-1-1 12:00:00
<sim_end> --> 1950-12-31 12:00:00
<restart_write> --> monthly
--> single
--> daily
<sim_start> --> 1950-1-1 12:00:00
<sim_end> --> 1950-12-31 12:00:00
<restart_write> --> monthly
--> single
--> daily
FATAL ERROR: init_model/read_control/unexpected text in control file provided:
---- read control file ---
<ancil_dir> --> ./ancillary_data/
FATAL ERROR: init_model/read_control/unexpected text in control file provided:
(note strings in control file must match the variable names i
n public_var.f90)
<input_dir> --> ./input/
(note strings in control file must match the variable names i
n public_var.f90)
<output_dir> --> ./output/
<case_name> --> case1
<sim_start> --> 1950-1-1 12:00:00
<sim_end> --> 1950-12-31 12:00:00
<restart_write> --> monthly
--> single
--> daily
FATAL ERROR: init_model/read_control/unexpected text in control file provided:
(note strings in control file must match the variable names i
n public_var.f90)

I am not able to understand why this is coming up.

@nmizukami
Copy link
Collaborator

I believe your setting file has some lines NOT starting <tag_name>, or !
please look at this https://mizuroute.readthedocs.io/en/latest/Control_file.html (especially the beginning of this page to try to understand some of rules in the setting

@PrateekSharma99
Copy link
Author

Hi @nmizukami. Thankyou for replying. I rechecked my test case setting file. I am also attaching the test case setting, the output, and the public variable list here.
From the link you shared, I found that I have all the required data in the test case file. I am currently rechecking for any missed data. Please look into it once.
https://drive.google.com/drive/folders/1VyPtH1fVHfXRb_6roKHqOSQd0uCRkbyp?usp=sharing

@nmizukami
Copy link
Collaborator

Sorry, but the link to google drive does not look correct (when i hover the link). Can you directly post your setting file here? maybe format it to the code (highlight the posted text and click on <>

@PrateekSharma99
Copy link
Author

PrateekSharma99 commented Nov 22, 2023

Sure here are the files.
1: testcasesettings
image

2: route.out
image

3:Pblic_var.f90
public_varf90.txt

@PrateekSharma99
Copy link
Author

The issue has been resolved. Thankyou @nmizukami
It was a file path issue on my end.

@PrateekSharma99
Copy link
Author

image
While using a global dataset provided by Inne Vanderkelen, I encountered the following error.

FATAL ERROR: init_model/read_control/unexpected text in control file provided:
<is_lake_sim> (note strings in control file must match the variable names in p
ublic_var.f90)
FATAL ERROR: init_model/read_control/unexpected text in control file provided:
<is_lake_sim> (note strings in control file must match the variable names in p
ublic_var.f90)

I have certain doubts since public_var.f90 is already an existing file for the parameters when I compiled my model, how come some variable names are missing in that file? Do I add parameters in that file or is there something that I am missing?

@nmizukami
Copy link
Collaborator

<is_lake_sim> looks ok in the control file. <lake_model_D3> and <lake_model_H06> are obsolete (they are still in public_var.f90, but looks like forgot to remove them) and you can remove them from the control file. The types of the lake models now need to be specified in river-lake network netcdf. Inne's data may be old now, and I can try to find some example that works with the latest code.

That been said, the error is generated while reading control file (not from network netcdf). are you able to post your control file somewhere so I can retrieve it and look with my text editor.

@PrateekSharma99
Copy link
Author

PrateekSharma99 commented Nov 30, 2023

controlfile.txt
public_varf90.txt
These are the control file and the public_var.f90 file. Having some examples of that work would be of great help.
Thanks for telling me that the error is not from the network netcd.

@nmizukami
Copy link
Collaborator

thanks, just noticed that you are using main or develop branch based on public_varf90.txt. can you use cesm-coupling branch? Neither main or develop has the lake models.

cesm-coupling branch requires a few extra libraries now - MPI library (e.g., openmpi) and pnetcdf. can you go to https://mizuroute.readthedocs.io/en/cesm-coupling/testCase.html and use testCase V2.0 and see README file? are you working on some cluster computer? and do you have system admin??

we are trying to explore docker container so a user don't have to deal with libraries, but not quite yet.

@PrateekSharma99
Copy link
Author

Thank you. I tried the testCase V2.0 but it did not require the cesm-coupling branch. I wanted to use the cesm-coupling branch because I wanted to work on lakes. Also, I use a high-performance computing system and I don't have system admin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants