Hi Alex,
Sorry that you haven’t gotten any replies. Typically that simply means that nobody has a particularly good answer (probably nobody else ever looked at your system) or your question wasn’t clear enough.
Generally speaking, we can easily help with questions of the type “I want to achieve X, how can I use MDAnalysis to accomplish that” or “I got this error message, what should I do to fix my code”.
Your question seems to be more of a scientific nature: “The output from the analysis is not what I expect for my system.” Arriving at this statement requirements a lot of knowledge and insight into the the physics and chemistry of your system of interest.
You are likely the expert on your system (I have no idea what to expect of cellulose… I suppose it should be stiff?) so at a minimum you need to explain to all of us non-experts WHY your results are puzzling. You then have to show if there are cases where you get the expected results: What did you use for validation? Then you have check if the algorithm used in the MDAnalysis persistence length calculation is appropriate for your case, and you should tell us what you conclude there. then you might want to present other results (eg visualization, back of the enevelope calculations, …) that indicate that the persistence calculation is wrong in some way. We can then start engaging in a discussion related to MDAnalysis.
A good strategy is to describe
1. What you are doing (including code, as you did), and concisely explain the background, i.e., your approach. Include equations, mention if this approach has been used before, etc.
2. What you expected to get (and why you expected this result)
3. What you got instead (and why this is a problem).
4. What other ways you attempted to validate your approach?
5. If you have a hypothesis to explain the problem: What you think might be going wrong?
Finish with a question. The MORE SPECIFIC THE BETTER the question is.
To sum it up: When you don’t get replies then you should try to think about how to make your question more accessible to members of the MDAnalysis community and think about who your audience is — smart people who know simulations, programming, and MDAnalysis but are almost certainly not experts on your system of interest.
The other thing to consider is that most people on this mailing list *may* have 10 minutes a day to spare answering questions. If they can’t quickly see how they can meaningfully contribute to a solution then they use their time for something more productive. We (=scientists, the MDAnalysis community) all love solving problems (otherwise we wouldn’t be doing what we are doing, right?) and we like helping each other being productive with MDAnalysis, so if you make it as easy as possible to help then we will.
Oliver