Ngoc-Cuong Nguyen

> Further updates/cleanups/refactoring can be done later. Totally agree. > Please note, that I am mostly looking at technical issues, consistency, and other formal details. Any scientific assessment and overall...

> @exapde Thanks for submitting this new packages and ML potential. @athomps is better to comment on the potential and fitting command itself. My two comments are about compatibility. @sjplimp...

> I think the two filenames `pod.txt` and ` data.txt` used in `fitpod_command.rst` and in `in.fitpod` are too generic and need a bit more thought. Probably they should both refer...

Hi Axel, Thank you very much for suggesting changes to improve ML-POD. Please share with us your detailed review at your convenience. In the mean time, we will make the...

Dear Axel and Aidan, I sincerely apologize for my slow response on my pull request. Thank you very much for your comments. I will update the ML-POD package to address...

Dear Axel and Aidan, Thank you very much for your help. I greatly appreciate it. I will edit ML-POD to include your comments. I would like to keep you posted...

Dear All, I apologize for my slow response. Recently, I made a number of significant updates for ML-POD relative to the version of the pull request https://github.com/lammps/lammps/pull/3866. The new features...

Exasim does not store the initial solution. I think we may want to have an option flag for users to decide whether they want to get the initial solution.

That's a good suggestion. We'll update the code to store the initial solution.

Temporarily, you can get the mesh structure and call the initu function in the pdeapp script to compute the initial solution. Alternatively, you can visualize the sequence of time-dependent solutions...