Closed ricalessandri closed 1 year ago
@ricalessandri I like the idea of the library table very much, but I would add where to find the force-field files as well as the actual name of the polymer because the abbreviation doesn't need to be unique.
yes, agree that the actual name is important. What I don't understand is what you mean by "where to find the force field files"; you mean a link to the papers? Currently I thought I would put the name of the library (actually, I didn't that for "Martini 2" and "Martini 3" --> should be "martini2" and "martini3") and at the same time have the hyperlink to the actual file (if one wants to take a quick peek at the model.
Missing M3 models. Will commit it later today.
I think it's almost done. Two remaining points
(highlights the need for a table with the names :))
Hi Riccardo,
Table looks very good already and indeed I agree we need this.
2016H66/HEA.
Poly(2-hydroxyethyl acrylate)
2016H66/PAM
Polyacrylamide
2016H66/PMAM
poly(methacrylamide)
- Also, in martini3 there's also a lipid-PEO think - should we include that in the table and how?
I think for now not. People doing PEGylated lipids will go to the tutorial hopefully and figure it out there, together with the warning that PEG lipid interactions in M3 are not good.
Done - LIBRARY.md.
yep - go ahead!
found a typo, hold on 1 sec
Ok, fixed. Ready to be merged, @fgrunewald.
I had this idea and wanted to run it with you, @fgrunewald. It might be useful to have this somewhere for users that want to know whether a certain polymer is already in the polyply library (without having to install polyply). It could then be linked in the main README.
Let me know what you think, this is a draft so many things could be improved (including maybe automating the table generation...). But wanted to first check if this is of any interest.