Sorry, I checked the log file and saw that you are running on Windows, and also with the -nb cpu option. I’ll update the issue report with that information.
Yes I tried both -nb option as well as without. Yes we are running it on windows. I think if you could fix this issue it will be useful to a lot of student researchers as windows is used mostly used by students. Is this bug fixable , if it is when do you expect to finish it?
It should definitely be fixable, and as you say, it might affect many people. So, it has a high priority. We hope to have it fixed in 2024.2, which should be released in two months.
Nice sir it will help a lot of people . And maybe can lead to integration of many gui to help assist a lot of people which will lead to lot of citations .
Thanks.
Could you recompile GROMACS with “-DCMAKE_BUILD_TYPE=Debug” and see if the bug still occurs?
What I meant about regular simulation is a molecular dynamics simulation like a small equilibration.
i tried compilin with debug and it didnt work it showed an error at this command “gmx pdb2gmx -f protein.pdb -o protien.gro -water spc -ff charmm36-jul2021”
error which occurred and the tpr file is given below.
i tried compiling with debug and it didn’t work it showed an error at this command “gmx pdb2gmx -f protein.pdb -o protien.gro -water spc -ff charmm36-jul2021” the error was showing debug assertion failed.
Thanks.
You don’t need to redo the whole procedure with the Debug binary, just the minimization (gmx mdrun -v -deffnm em -nb cpu) with the tpr you previously obtained (although the pdb2gmx should not fail like this, I’ll take a look).
i tried compiling with debug and it didn’t work it showed an error at this command “gmx pdb2gmx -f protein.pdb -o protien.gro -water spc -ff charmm36-jul2021” the error was showing debug assertion failed.