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

Mechanism file error #489

Closed
tanzinaakther opened this issue Mar 22, 2023 · 15 comments
Closed

Mechanism file error #489

tanzinaakther opened this issue Mar 22, 2023 · 15 comments

Comments

@tanzinaakther
Copy link

Hi, I was running the model fine. Now I wanted to add more mechanisms. So, I downloaded new mechanism file and I am getting this error. Any idea why I am getting this error?
mechanism file error
run error

@spco
Copy link
Collaborator

spco commented Mar 23, 2023

Reading your error message - please show us the contents of /home/takther/Model_03/AtChem2_Tanzina/model_rns/constratints/species/NC4H10 - if you're able to upload the file here that would be particularly helpful.

@rs028
Copy link
Collaborator

rs028 commented Mar 23, 2023

The first error is just a warning. It means that you have two species in your RO2 summation that are not actually peroxy radicals. This is an error of the MCM database. Manually delete IPRCHOO and IPRCHOOA from the RO2 summation in the .fac file and it will be okay.

@tanzinaakther
Copy link
Author

Hi, I removed IPRCHOO and IPRCHOOA. Mechanism file is ok now but still got this error.
run error

@tanzinaakther
Copy link
Author

Reading your error message - please show us the contents of /home/takther/Model_03/AtChem2_Tanzina/model_rns/constratints/species/NC4H10 - if you're able to upload the file here that would be particularly helpful.

I removed NC4H10 as there were 0 values in the file.

@spco
Copy link
Collaborator

spco commented Mar 23, 2023

The latest error indicates that the linear interpolation of one of the constraints has failed. This is usually because the time interval over which the constraints is defined does not contain the time at which interpolation is taking place.

Please check that all of your constraints files define a value from 0 until the end of the time interval being calculated. It is worth defining the constraints until a little after the end of the time interval, because occasionally the algorithm overshoots the desired end time by a small amount.

If NC4H10 is meant to be constrained, then please ensure it does have a file associated to it, and it is present in speciesConstrained.config. If it's not meant to be constrained, then make sure it doesn't have a file and isn't present in speciesConstrained.config. If you only have one of those 2 conditions, then you will get such an error.

@rs028
Copy link
Collaborator

rs028 commented Mar 23, 2023

@spco, this should probably be addressed somehow at some point. It is perhaps part of issue #348 - I will add a note there.

@tanzinaakther
Copy link
Author

I checked all the constrained species file. All has same time from -154800 to 363600.

NC4H10 isn't present in speciesConstrained.config Still have the same error.

@tanzinaakther
Copy link
Author

I thought maybe this problem is related to new mechanism file I downloaded. But I am getting the same error using my previous mechanism file. I even deleted all the constrained species name from the species constrained.config file and only wrote one speicies to check if it runs. But the same error.

@rs028
Copy link
Collaborator

rs028 commented Mar 27, 2023

Can you run the tests?

@tanzinaakther
Copy link
Author

which one you are referring as test? Today I only downloaded C3H8 mechanism and try to run but same problem.

@rs028
Copy link
Collaborator

rs028 commented Mar 28, 2023

You should be able to run make oldtests if the model is installed properly.

@tanzinaakther
Copy link
Author

The model is installed properly because I ran it before, and I have the results. Now I wanted to run same sample with more mechanism added in the mechanism file. After downloading the new MCM file, i encountered this issue. But now when I run with my previous mechanism file, I am facing the same issue.

@rs028
Copy link
Collaborator

rs028 commented Mar 28, 2023

Try make clean and recompile the model and see if it solves the issue

@tanzinaakther
Copy link
Author

Sure. Thank you

@rs028
Copy link
Collaborator

rs028 commented May 16, 2023

@tanzinaakther Did you manage to resolve this problem?

@rs028 rs028 closed this as completed Jul 14, 2023
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

3 participants