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

Lammps should check input file directly when quantities are printed to log file #4

Open
JFRudzinski opened this issue Aug 24, 2022 · 3 comments
Labels
backlog Issue not currently being worked on, and no plans for efforts in the near future enhancement New feature or request

Comments

@JFRudzinski
Copy link
Contributor

The default log file in Lammps appears to not always contain the input parameters of the simulation (still unsure of the exact behavior, need more examples). When we don't find the appropriate key in the log, we should find the '.inp' file in search directly in there.

@JFRudzinski JFRudzinski added the enhancement New feature or request label Aug 24, 2022
@JFRudzinski JFRudzinski self-assigned this Aug 24, 2022
@ladinesa
Copy link
Collaborator

@JFRudzinski any update?

@JFRudzinski
Copy link
Contributor Author

I am not sure what I want to do here. There are a few open issues for the Lammps parser. At the same time I am not interested in investing a lot of time there at the moment (perhaps in the future if we have a larger user base).

What I would say is that let me try to take a look in the next few weeks and reassess the situation, and then we can decide how to move forward for all these Lammps issues.

@ladinesa
Copy link
Collaborator

I suggest you unassign yourself to inidicate it is in the backlog: no one is currently working on it.

@JFRudzinski JFRudzinski removed their assignment Aug 16, 2023
@JFRudzinski JFRudzinski added the backlog Issue not currently being worked on, and no plans for efforts in the near future label Aug 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Issue not currently being worked on, and no plans for efforts in the near future enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants