Contribution Guideline and File Format Description

[MartinWenge]

We should add a contribution guideline including our programming style, for instance member functions start with lower case letter followed by camel case style for long function names. Suggestions of important points should be collected here in the discussion.

[MartinWenge]

We should also provide a description of the BFM file format in the README

[tonimueller]

Concerning the output of some Features/MonomerExtensions I would suggest to define the standard to only write out the non-trivial behavior. Lets consider the FeatureConnectionSc. The standard is that only a few monomers in the system are reactive, but we write out this property for each monomer. For my opinion it would be sufficient to only write out the reactive ones. The Read-routine for this property sets all monomers which do not appear in the bfm file to the standard value (nonreactive).
Would do you think about this?

[MartinWenge]

That's fine. The FeatureSpringPotentialTwoGroups is already working like this. Does that mean we have to rewrite Feature Attributes again?

[tonimueller]

Yes, if we decide to handle it like I suggest it,it would mean we have to revise FeatureAttributes and FeatureConnectionSc. Other Features are not affected, because they do not add any monomerExtension.

[MartinWenge]

note: typo in README in the section Contribution (programm -> program)

[MartinWenge]

note: the contribution from Vinzenz Sinapius should be added to the Authors.md file

[MartinWenge]

note: add publication
Dendrimers in solution of linear polymers
some more publications made with LeMonADE?

[MartinWenge]

note: add publication
Tendomers – force sensitive bis-rotaxanes with jump-like deformation behavior