-
Notifications
You must be signed in to change notification settings - Fork 63
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
Testing Error from the twoD_detonationH2 case with DNN #316
Comments
Hi there! Thank you for reaching out and providing the details. To run DeepFlame with DNN, please follow these steps:
Regarding your specific case, please note that the mechanism file named Feel free to reach out if you have any further questions or need additional assistance. We're here to help! |
Thank you very much for your careful guidance! I followed the above steps and ran the However, I meet a new error😭. The initial phase of calculation is fine, but about I used the I have not found a solution to this problem on the web. |
Thank you for the reply. I will check the settings of each file and hope to solve this problem. Thanks again.🤗 |
Sorry for the late response. DNN is curently not available for dfHighSpeedFoam, so variables are not be solved (You can see in the log.mpi that iterations are 0). That's why cantera throw error when calculating chemistry. You can only use cvode when using this solver. |
Thanks to the DeepFlame team for answering my previous questions, please forgive me for asking another question.
I downloaded the DNN models and copied the HE04_Hydrogen_ESH2_GMS_sub_20221101 into
/mechanisms
.Then I run the following code:
cd deepflame-dev/examples/dfHighSpeedFoam/twoD_detonationH2
./Allrun
The process will be terminated. the
log.mpirun
show:whatever I keep the default settings
or modify the
torchModel
This error always happens, and is similar to Issused#175.
However, I have downloaded the DNN, and there is no "inference.py" file in twoD_detonationH2.
Looking forward to your solutions! Thanks a lot!
The text was updated successfully, but these errors were encountered: