-
Notifications
You must be signed in to change notification settings - Fork 7
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
Compilation fail #6
Comments
Same for me, when I tried to run the model over Christmas. I don't think that's due to kpp though. As far as I understood @JosueBock, this kpp version contains just a few bug fixes, e.g., the acknowledgement of the correct line length of fixed form fortran. I assume, it is missing a file with some definitions for when we define species in Mistra, but I didn't have the time to look into it, yet. |
I had another quick look over the weekend, there is a file atoms in |
I haven't tried. I will. |
It does not work with KPP 2.2.3 (the last official version on http://people.cs.vt.edu/asandu/Software/Kpp/). If I copy the If I do as you suggest (i.e., delete
@JosueBock do you have any clues on what is going on? |
I guess that something went wrong during your KPP installation, since I had no problem to install it from scratch. When using KPP, if it does not find this file, it means that the link is not correct, so I guess the problem might arise from your environment variables definitions: in your NB: the second error message that you get after deleting |
I will have another go and let you know. This also reminds me that the model seems to be using both bash and csh scripts, correct me if I am wrong. |
All scripts in mech subdirectory are csh scripts. |
Please reopen this issue in case of troubles when compiling. |
I am using the version of KPP provided with Mistra.
I tried to compile the model but it fails:
It seems
atoms
is required bysrc/mech/master.spc
but there is no file with that name in the directory. Is there a file missing?@pb866 did you manage to compile without errors?
The text was updated successfully, but these errors were encountered: