Please watch your output very carefully. The MSM kspace style will adjust the coulomb cutoff of the pair style to match the desired accuracy. That step however is not compatible with using a hybrid pair style, so the coulomb cutoff for the first lj/cut/coul/msm instance will be adjusted but not the second.
Overall, your input - as quoted - cannot run, since the used hybrid style setting prevents creating mixed pair_coeff parameters for all entries that would matchpair_coeff 1*5 6
What you are doing makes no sense anyway.
If it runs with an older version of LAMMPS then that is because that older version does not check for all input errors (yet).
I change all the cutoff of coulomb interaction to 16.409433.but it not works.I already set the cutoff to 16.409433,but the warning message will appear again.So is this a drawback of lammps?In some reason, I have to use hybrid pair style.Thanks for your advice!
Actually,all pair coeffs are set one by one in my in script.And this error(All pair coeffs are not set) doesn’t appear in my log file.For simplify,I don’t list all the pair coeffs.A question is ：Using lj/cut/coul/long and pppm method works well with pair hybrid.but why msm not? that’s really confusing.Thanks for your help.
This question is irrelevant unless you can provide a convincing reason to use a hybrid style in the first place. So far you have failed consistently and given the fact that you also do not provide accurate input examples has now exhausted my patience and interest completely.
Successful communication in a forum like this is based on mutual give and take. However you are only taking and not giving.
Sincere sorry for that.the question I mentioned above is just a simple doubt.Pair_style without a hybrid style is suited for my system,too.Thanks for your patient answer. I really learned a lot.
Wish you a happy day!
Your apology is coming too late. The damage is done. While I am not Santa Claus (although sometimes people claim that my appearance would make me a possible candidate), I do have a “nice” and “naughty” list.
There are several things that get you on the “naughty” list:
Not reporting the LAMMPS version you are using (you only provided it after asking)
providing incomplete input examples (you did)
providing inputs that are modified from what you use (you did)
not paying attention to my explanations (I had explained why msm is different with hybrid)
not following the advice been given (I suggested to not use hybrid)
saying that you require a feature when you don’t (you just confirmed that)
not providing an explanation why you need to use something I recommended against (you did)
saying that you have a problem but without saying what it is (you did not)
providing a large and (needlessly) complex input deck that is difficult to read (you did not)
So from that list you qualify for all but the last two. That makes you very naughty™.
Since I also have a long memory about how people behave, you will have to be very nice™ in the future to see me look at any of your questions or requests.